| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Race condition caused occasional failure on CI. Chained callbacks used to remove race condition.
|
Sample CI failure: https://ci.nodejs.org/job/node-test-commit-freebsd/5892/nodes=freebsd10-64/console not ok 464 parallel/test-http-client-timeout-event
---
duration_ms: 1.240
severity: fail
stack: |-
assert.js:85
throw new assert.AssertionError({
^
AssertionError: 0 === 1
at Timeout._onTimeout (/usr/home/iojs/build/workspace/node-test-commit-freebsd/nodes/freebsd10-64/test/parallel/test-http-client-timeout-event.js:28:12)
at ontimeout (timers.js:365:14)
at tryOnTimeout (timers.js:237:5)
at Timer.listOnTimeout (timers.js:207:5) |
Sorry, something went wrong.
|
I am able to replicate that failure locally by running the test in parallel with itself: tools/test.py -j 32 parallel/test-http-client-timeout-event parallel/test-http-client-timeout-event parallel/test-http-client-timeout-event parallel/test-http-client-timeout-event parallel/test-http-client-timeout-event parallel/test-http-client-timeout-event parallel/test-http-client-timeout-event parallel/test-http-client-timeout-event parallel/test-http-client-timeout-event parallel/test-http-client-timeout-event parallel/test-http-client-timeout-event parallel/test-http-client-timeout-event parallel/test-http-client-timeout-event parallel/test-http-client-timeout-event parallel/test-http-client-timeout-event parallel/test-http-client-timeout-event parallel/test-http-client-timeout-event parallel/test-http-client-timeout-event parallel/test-http-client-timeout-event parallel/test-http-client-timeout-event parallel/test-http-client-timeout-event parallel/test-http-client-timeout-event parallel/test-http-client-timeout-event parallel/test-http-client-timeout-event parallel/test-http-client-timeout-event parallel/test-http-client-timeout-event parallel/test-http-client-timeout-event parallel/test-http-client-timeout-event parallel/test-http-client-timeout-event parallel/test-http-client-timeout-event parallel/test-http-client-timeout-event parallel/test-http-client-timeout-eventResult: === release test-http-client-timeout-event ===
Path: parallel/test-http-client-timeout-event
assert.js:85
throw new assert.AssertionError({
^
AssertionError: 0 === 1
at Timeout._onTimeout (/Users/trott/io.js/test/parallel/test-http-client-timeout-event.js:28:12)
at ontimeout (timers.js:365:14)
at tryOnTimeout (timers.js:237:5)
at Timer.listOnTimeout (timers.js:207:5)
Command: out/Release/node /Users/trott/io.js/test/parallel/test-http-client-timeout-event.js
=== release test-http-client-timeout-event ===
Path: parallel/test-http-client-timeout-event
assert.js:85
throw new assert.AssertionError({
^
AssertionError: 0 === 1
at Timeout._onTimeout (/Users/trott/io.js/test/parallel/test-http-client-timeout-event.js:28:12)
at ontimeout (timers.js:365:14)
at tryOnTimeout (timers.js:237:5)
at Timer.listOnTimeout (timers.js:207:5)
Command: out/Release/node /Users/trott/io.js/test/parallel/test-http-client-timeout-event.js
[00:01|% 100|+ 30|- 2]: Done Running the same command with the changes in this PR results in success. |
Sorry, something went wrong.
Sorry, something went wrong.
|
@nodejs/testing |
Sorry, something went wrong.
|
The widget keeps reporting arm as failing on various pull requests even when it's successful (like here). Not sure what's up with that, but I guess /cc @jbergstroem as an FYI. |
Sorry, something went wrong.
|
CI stress test showing current master failing: https://ci.nodejs.org/job/node-stress-single-test/1074/nodes=freebsd10-64/console CI stress test showing this branch passing: https://ci.nodejs.org/job/node-stress-single-test/1075/nodes=freebsd10-64/console |
Sorry, something went wrong.
Race condition caused occasional failure on CI. Chained callbacks used to remove race condition. PR-URL: nodejs#10293 Reviewed-By: Santiago Gimeno <santiago.gimeno@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Race condition caused occasional failure on CI. Chained callbacks used to remove race condition. PR-URL: nodejs#10293 Reviewed-By: Santiago Gimeno <santiago.gimeno@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Race condition caused occasional failure on CI. Chained callbacks used to remove race condition. PR-URL: #10293 Reviewed-By: Santiago Gimeno <santiago.gimeno@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Race condition caused occasional failure on CI. Chained callbacks used to remove race condition. PR-URL: #10293 Reviewed-By: Santiago Gimeno <santiago.gimeno@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Race condition caused occasional failure on CI. Chained callbacks used to remove race condition. PR-URL: #10293 Reviewed-By: Santiago Gimeno <santiago.gimeno@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Race condition caused occasional failure on CI. Chained callbacks used to remove race condition. PR-URL: #10293 Reviewed-By: Santiago Gimeno <santiago.gimeno@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
| Back | FazBrowse Home | New Git URL |
Checklist
Affected core subsystem(s)
test http
Description of change
Race condition caused occasional failure on CI. Chained callbacks used
to remove race condition.