| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
Example failure without these changes: https://ci.nodejs.org/job/node-test-commit-linux/14693/nodes=alpine36-container-x64/consoleFull not ok 148 parallel/test-benchmark-events
---
duration_ms: 5.335
severity: fail
stack: |-
events/ee-add-remove.js
events/ee-add-remove.js n=1: 3,238.5412314876885
events/ee-emit.js
events/ee-emit.js listeners=1 argc=0 n=1: 8,308.684236764266
events/ee-emit.js listeners=5 argc=0 n=1: 7,649.763239827728
events/ee-emit.js listeners=10 argc=0 n=1: 7,807.681196761374
events/ee-emit.js listeners=1 argc=2 n=1: 7,828.52401008314
events/ee-emit.js listeners=5 argc=2 n=1: 16,525.10162937502
events/ee-emit.js listeners=10 argc=2 n=1: 8,180.226755885673
events/ee-emit.js listeners=1 argc=4 n=1: 21,679.276779326643
/home/iojs/build/workspace/node-test-commit-linux/nodes/alpine36-container-x64/benchmark/common.js:202
throw new Error('insufficient clock precision for short benchmark');
^
Error: insufficient clock precision for short benchmark
at Benchmark.end (/home/iojs/build/workspace/node-test-commit-linux/nodes/alpine36-container-x64/benchmark/common.js:202:13)
at main (/home/iojs/build/workspace/node-test-commit-linux/nodes/alpine36-container-x64/benchmark/events/ee-emit.js:35:13)
at Benchmark.process.nextTick (/home/iojs/build/workspace/node-test-commit-linux/nodes/alpine36-container-x64/benchmark/common.js:34:28)
at process._tickCallback (internal/process/next_tick.js:155:11)
at Function.Module.runMain (module.js:703:11)
at startup (bootstrap_node.js:195:16)
at bootstrap_node.js:646:3
assert.js:42
throw new errors.AssertionError({
^
AssertionError [ERR_ASSERTION]: 1 strictEqual 0
at ChildProcess.child.on (/home/iojs/build/workspace/node-test-commit-linux/nodes/alpine36-container-x64/test/common/benchmark.js:25:12)
at ChildProcess.emit (events.js:126:13)
at Process.ChildProcess._handle.onexit (internal/child_process.js:209:12)
... |
Sorry, something went wrong.
Sorry, something went wrong.
|
CI failure is no doubt unrelated build issue but here's a re-run: https://ci.nodejs.org/job/node-test-commit-linux-linked/609/ |
Sorry, something went wrong.
There was a problem hiding this comment.
Typo in commit comment:
'only ones one combination of options'
otherwise LGTM
Sorry, something went wrong.
Make sure each benchmark file only runs one combination of options. Allow for zero iterations for short benchmark.
|
Typo in commit fixed. Thanks, @mhdawson! |
Sorry, something went wrong.
|
(CI is good.) |
Sorry, something went wrong.
|
I think this can land below the 48 hours. |
Sorry, something went wrong.
Make sure each benchmark file only runs one combination of options. Allow for zero iterations for short benchmark. PR-URL: nodejs#17472 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Make sure each benchmark file only runs one combination of options. Allow for zero iterations for short benchmark. PR-URL: #17472 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Make sure each benchmark file only runs one combination of options. Allow for zero iterations for short benchmark. PR-URL: #17472 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Make sure each benchmark file only runs one combination of options. Allow for zero iterations for short benchmark. PR-URL: #17472 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Make sure each benchmark file only runs one combination of options. Allow for zero iterations for short benchmark. PR-URL: #17472 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
| Back | FazBrowse Home | New Git URL |
Make sure each benchmark file only ones one combination of options.
Allow for zero iterations for short benchmark.
Checklist
Affected core subsystem(s)
test benchmark events