-
Notifications
You must be signed in to change notification settings - Fork 30k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
benchmark: add default type in getstringwidth.js #31377
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nodejs-github-bot
added
the
benchmark
Issues and PRs related to the benchmark subsystem.
label
Jan 16, 2020
I'd like to fast-track this to unbreak nightly CI. Please 👍 here to approve (or comment to block). |
BridgeAR
approved these changes
Jan 16, 2020
Benchmark tests CI: https://ci.nodejs.org/job/node-test-commit-custom-suites-freestyle/11595/ |
sam-github
approved these changes
Jan 16, 2020
cjihrig
approved these changes
Jan 16, 2020
It's probably better to throw instead. |
richardlau
approved these changes
Jan 16, 2020
Might be a good enhancement in the future. Before we can do that we'd need to:
|
Trott
force-pushed
the
fix-getstringwidth
branch
from
January 16, 2020 06:00
3c7c340
to
d2683ed
Compare
Landed in d2683ed |
MylesBorins
pushed a commit
that referenced
this pull request
Jan 16, 2020
This fixes a benchmark test that was recently broken by a breaking change on the master branch. Fixes: #31372 PR-URL: #31377 Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> Reviewed-By: Sam Roberts <vieuxtech@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Richard Lau <riclau@uk.ibm.com>
Merged
codebytere
pushed a commit
that referenced
this pull request
Mar 14, 2020
This fixes a benchmark test that was recently broken by a breaking change on the master branch. Fixes: #31372 PR-URL: #31377 Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> Reviewed-By: Sam Roberts <vieuxtech@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Richard Lau <riclau@uk.ibm.com>
codebytere
pushed a commit
that referenced
this pull request
Mar 17, 2020
This fixes a benchmark test that was recently broken by a breaking change on the master branch. Fixes: #31372 PR-URL: #31377 Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> Reviewed-By: Sam Roberts <vieuxtech@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Richard Lau <riclau@uk.ibm.com>
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
benchmark
Issues and PRs related to the benchmark subsystem.
fast-track
PRs that do not need to wait for 48 hours to land.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This fixes a benchmark test that was recently broken by a breaking
change on the master branch.
Fixes: #31372
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passes