You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
assert.js:86
throw new AssertionError(obj);
^
AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:
1 !== 7
at Agent.<anonymous> (/home/iojs/build/workspace/node-stress-single-test/nodes/aix61-ppc64/test/parallel/test-https-agent-additional-options.js:73:16)
at Agent.<anonymous> (/home/iojs/build/workspace/node-stress-single-test/nodes/aix61-ppc64/test/common/index.js:346:15)
at Object.onceWrapper (events.js:277:13)
at Agent.emit (events.js:194:15)
at TLSSocket.onFree (_http_agent.js:258:11)
at TLSSocket.emit (events.js:189:13)
at emitFreeNT (_http_client.js:628:10)
at process.internalTickCallback (internal/process/next_tick.js:72:19)
not recreate-able any more - ran enough time to arrive at that. And didn't see this as reported any time in the recent past. Probably we should close; and re-open if we see again?
assert.js:84
throw new AssertionError(obj);
^
AssertionError [ERR_ASSERTION]: Input A expected to strictly equal input B:
+ expected - actual
- 6
+ 7
at Agent.<anonymous> (/home/iojs/build/workspace/node-test-binary-arm/test/parallel/test-https-agent-additional-options.js:72:16)
at Agent.<anonymous> (/home/iojs/build/workspace/node-test-binary-arm/test/common/index.js:379:15)
at Object.onceWrapper (events.js:286:20)
at Agent.emit (events.js:203:15)
at TLSSocket.onFree (_http_agent.js:258:11)
at TLSSocket.emit (events.js:198:13)
at emitFreeNT (_http_client.js:622:10)
at process._tickCallback (internal/process/next_tick.js:63:19)
On my way out the door to drop my kid at school and then get to work, but really fast: I suppose it's possible that it's only on 10.x and has been fixed on master. I might try to run a stress test later on master vs. v10.x-staging. If anyone does that before I get to it later, even better. :-D
Looks like the socket will sometimes close before the test completes, causing it to be removed from the pool Then it is missing from the pool when it is checked at the end of the test. Working up a fix (unless my conclusion here is wrong, in which case I'm working on a non-fix).
Looks like the socket will sometimes close before the test completes, causing it to be removed from the pool Then it is missing from the pool when it is checked at the end of the test. Working up a fix (unless my conclusion here is wrong, in which case I'm working on a non-fix).
Activity
richardlau commentedon Nov 17, 2018
Copy/paste error? (platform and test do not match the CI links/output).
refack commentedon Nov 17, 2018
Yeah. I mangled #24397 instead 🤦♂️
Trott commentedon Nov 24, 2018
Stress test: https://ci.nodejs.org/job/node-stress-single-test/2109/
RUN_TESTS:
-J --repeat 10 parallel/test-https-agent-additional-optionsRUN_TIMES:
100RUN_LABEL:
aix61-ppc64refack commentedon Nov 24, 2018
1 out of 100 repeats failed
https://ci.nodejs.org/job/node-stress-single-test/2109/nodes=aix61-ppc64/testReport/junit/(root)/
With:
gireeshpunathil commentedon Jan 29, 2019
not recreate-able any more - ran enough time to arrive at that. And didn't see this as reported any time in the recent past. Probably we should close; and re-open if we see again?
Trott commentedon Jan 29, 2019
Did
ncu-ci walk commitand there were no failures of this test. So that would be consistent with "This doesn't seem to be failing anymore."gireeshpunathil commentedon Jan 30, 2019
closing as non-reproducible, re-open if found again.
MylesBorins commentedon May 16, 2019
Just showed up on 10.x arm
https://ci.nodejs.org/job/node-test-binary-arm/7686/RUN_SUBSET=3,label=pi1-docker/testReport/junit/(root)/test/parallel_test_https_agent_additional_options/
Trott commentedon May 21, 2019
On my way out the door to drop my kid at school and then get to work, but really fast: I suppose it's possible that it's only on 10.x and has been fixed on master. I might try to run a stress test later on master vs. v10.x-staging. If anyone does that before I get to it later, even better. :-D
Trott commentedon May 21, 2019
Actually, no need for a stress test on CI as I can replicate this locally (on macOS Mojave):
Details
Trott commentedon May 22, 2019
Flaky on master: https://ci.nodejs.org/job/node-stress-single-test/2211/nodes=debian9-64/console
Trott commentedon May 22, 2019
Looks like the socket will sometimes close before the test completes, causing it to be removed from the pool Then it is missing from the pool when it is checked at the end of the test. Working up a fix (unless my conclusion here is wrong, in which case I'm working on a non-fix).
Trott commentedon May 22, 2019
#27830
test: fix test-https-agent-additional-options
test: fix test-https-agent-additional-options
test: fix test-https-agent-additional-options