-
Notifications
You must be signed in to change notification settings - Fork 29.7k
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
test: fix flaky test-http-client-timeout-event #10293
Conversation
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) |
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-event Result: === 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. |
@nodejs/testing |
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. |
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 |
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>
Landed in 348e69c |
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>
Checklist
make -j4 test
(UNIX), orvcbuild test nosign
(Windows) passesAffected core subsystem(s)
test http
Description of change
Race condition caused occasional failure on CI. Chained callbacks used
to remove race condition.