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: check for time precision in common.js #12934

Closed
wants to merge 1 commit into from

Conversation

Trott
Copy link
Member

@Trott Trott commented May 9, 2017

Some benchmark tests are failing intermittently, possibly due to
hrtime() imprecision on particular hosts. This change will confirm or
refute that as the root cause the next time the test fails on CI. Either
way, it's a valid check.

Refs: #12497
Refs: #12433

/cc @addaleax @joyeecheung

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

benchmark test

Some benchmark tests are failing intermittently, possibly due to
hrtime() imprecision on particular hosts. This change will confirm or
refute that as the root cause the next time the test fails on CI. Either
way, it's a valid check.

Refs: nodejs#12497
Refs: nodejs#12433
@Trott Trott added benchmark Issues and PRs related to the benchmark subsystem. test Issues and PRs related to the tests. labels May 9, 2017
@nodejs-github-bot nodejs-github-bot added the benchmark Issues and PRs related to the benchmark subsystem. label May 9, 2017
@jasnell
Copy link
Member

jasnell commented May 9, 2017

Hmmm... do we want to fail or skip on those?

@Trott
Copy link
Member Author

Trott commented May 9, 2017

Hmmm... do we want to fail or skip on those?

If it is confirmed as the source of the error, we'll probably add something to the start of the test to check the hrtime() precision and skip if it is not sufficiently precise. But first I want to confirm that this is actually the source of the problem.

@Trott
Copy link
Member Author

Trott commented May 11, 2017

Trott added a commit to Trott/io.js that referenced this pull request May 11, 2017
Some benchmark tests are failing intermittently, possibly due to
hrtime() imprecision on particular hosts. This change will confirm or
refute that as the root cause the next time the test fails on CI. Either
way, it's a valid check.

PR-URL: nodejs#12934
Ref: nodejs#12497
Ref: nodejs#12433
Reviewed-By: Anna Henningsen <[email protected]>
Reviewed-By: Joyee Cheung <[email protected]>
Reviewed-By: James M Snell <[email protected]>
@Trott
Copy link
Member Author

Trott commented May 11, 2017

Landed in a82e0e6

@Trott Trott closed this May 11, 2017
anchnk pushed a commit to anchnk/node that referenced this pull request May 19, 2017
Some benchmark tests are failing intermittently, possibly due to
hrtime() imprecision on particular hosts. This change will confirm or
refute that as the root cause the next time the test fails on CI. Either
way, it's a valid check.

PR-URL: nodejs#12934
Ref: nodejs#12497
Ref: nodejs#12433
Reviewed-By: Anna Henningsen <[email protected]>
Reviewed-By: Joyee Cheung <[email protected]>
Reviewed-By: James M Snell <[email protected]>
@jasnell jasnell mentioned this pull request May 28, 2017
@gibfahn gibfahn mentioned this pull request Jun 15, 2017
3 tasks
@Trott Trott deleted the precision branch January 13, 2022 22:45
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. test Issues and PRs related to the tests.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants