-
Notifications
You must be signed in to change notification settings - Fork 166
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
Benchmarks in CI produce erroneous results #1793
Comments
This issue is stale because it has been open many days with no activity. It will be closed soon unless the stale label is removed or a comment is made. |
This issue is stale because it has been open many days with no activity. It will be closed soon unless the stale label is removed or a comment is made. |
Checking to see if timers benchmark is still affected: https://ci.nodejs.org/view/Node.js%20benchmark/job/benchmark-node-micro-benchmarks/977/ (That's a PR doing a timers benchmark comparison using a PR that only changes a single |
I've also queued a dns benchmark for the same purpose: https://ci.nodejs.org/view/Node.js%20benchmark/job/benchmark-node-micro-benchmarks/978/ |
Seems like this is no longer an issue, but two last CI runs just to make sure. dns: https://ci.nodejs.org/view/Node.js%20benchmark/job/benchmark-node-micro-benchmarks/984/ events: https://ci.nodejs.org/view/Node.js%20benchmark/job/benchmark-node-micro-benchmarks/985/ |
Looks good. Closing. |
Running benchmark CI jobs using PRs that only change the README file, I've found at least two that consistently report significant differences. I am not able to reproduce these erroneous results locally. Something is wrong with the benchmark CI setup, but I have no idea what.
Ref: nodejs/node#27380 (comment) and nodejs/node#27380 (comment)
Ref: nodejs/node#27081 (comment)
The text was updated successfully, but these errors were encountered: