Skip to content
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 0 commits into from
Jan 16, 2020

Conversation

Trott
Copy link
Member

@Trott Trott commented Jan 16, 2020

This fixes a benchmark test that was recently broken by a breaking
change on the master branch.

Fixes: #31372

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • commit message follows commit guidelines

@nodejs-github-bot nodejs-github-bot added the benchmark Issues and PRs related to the benchmark subsystem. label Jan 16, 2020
@Trott Trott added the fast-track PRs that do not need to wait for 48 hours to land. label Jan 16, 2020
@Trott
Copy link
Member Author

Trott commented Jan 16, 2020

I'd like to fast-track this to unbreak nightly CI. Please 👍 here to approve (or comment to block).

@Trott
Copy link
Member Author

Trott commented Jan 16, 2020

@Trott
Copy link
Member Author

Trott commented Jan 16, 2020

@mscdex
Copy link
Contributor

mscdex commented Jan 16, 2020

It's probably better to throw instead.

@Trott
Copy link
Member Author

Trott commented Jan 16, 2020

It's probably better to throw instead.

Might be a good enhancement in the future. Before we can do that we'd need to:

  • Change the benchmark tests as described in Investigate flaky test-benchmark-misc  #31372 (comment) so that none of them depend on default options anymore
  • Add this "throw on undefined option" feature to the benchmark test runner (rather than inserting it into each and every benchmark)

@Trott Trott merged commit d2683ed into nodejs:master Jan 16, 2020
@Trott
Copy link
Member Author

Trott commented Jan 16, 2020

Landed in d2683ed

@Trott Trott deleted the fix-getstringwidth branch January 16, 2020 06:00
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 <[email protected]>
Reviewed-By: Sam Roberts <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Richard Lau <[email protected]>
@codebytere codebytere mentioned this pull request Jan 16, 2020
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 <[email protected]>
Reviewed-By: Sam Roberts <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Richard Lau <[email protected]>
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 <[email protected]>
Reviewed-By: Sam Roberts <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Richard Lau <[email protected]>
@codebytere codebytere mentioned this pull request Mar 17, 2020
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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Investigate flaky test-benchmark-misc
7 participants