| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
/cc @nodejs/testing |
Sorry, something went wrong.
|
Stress test so-far showing (and hopefully will continue to show) that this version of the test is robust: https://ci.nodejs.org/job/node-stress-single-test/768/nodes=smartos14-64/console Stress test showing the version on master branch is flaky: https://ci.nodejs.org/job/node-stress-single-test/767/nodes=smartos14-64/console |
Sorry, something went wrong.
Sorry, something went wrong.
|
Stress test failed but now at a later part of the test, I think... |
Sorry, something went wrong.
Sometimes, a SmartOS bug results in ECONNREFUSED when trying to connect to the TLS server that the test starts. Retry in that situation. Fixes: nodejs#5111 Refs: https://smartos.org/bugview/OS-2767
|
Rebased, force pushed, changed test to decrement a counter on failure, and trying stress test again: |
Sorry, something went wrong.
|
That wasn't quite the right fix. Let's try again: https://ci.nodejs.org/job/node-stress-single-test/775/nodes=smartos14-64/console |
Sorry, something went wrong.
|
Hooray, that seems to have fixed it. PTAL @nodejs/testing |
Sorry, something went wrong.
|
LGTM. One (maybe evident) question though: how is that the process.exit is emitted twice? |
Sorry, something went wrong.
|
@santigimeno exit is being emitted on process only once, but there are two listeners. The process.on('exit', ...) gets run twice because it's inside doTest() which is called twice. So, the listener gets added twice. It's behavior depends on testOptions which is scoped to doTest() so it will have different values (and therefore the listeners will behave differently) even though they are both being triggered by the same event. |
Sorry, something went wrong.
|
Oh. It was pretty obvious in hindsight. Thanks for the explanation @Trott |
Sorry, something went wrong.
Sorry, something went wrong.
|
One build issue on CI but no issues with this test. |
Sorry, something went wrong.
Sometimes, a SmartOS bug results in ECONNREFUSED when trying to connect to the TLS server that the test starts. Retry in that situation. Fixes: nodejs#5111 Refs: https://smartos.org/bugview/OS-2767 PR-URL: nodejs#7505 Reviewed-By: Santiago Gimeno <santiago.gimeno@gmail.com>
Sometimes, a SmartOS bug results in ECONNREFUSED when trying to connect to the TLS server that the test starts. Retry in that situation. Fixes: #5111 Refs: https://smartos.org/bugview/OS-2767 PR-URL: #7505 Reviewed-By: Santiago Gimeno <santiago.gimeno@gmail.com>
|
@thealphanerd Yes if it lands cleanly. |
Sorry, something went wrong.
|
does not land cleanly 😢 |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Checklist
Affected core subsystem(s)
test tls
Description of change
Sometimes, a SmartOS bug results in ECONNREFUSED when trying to connect
to the TLS server that the test starts. Retry in that situation.
Fixes: #5111
Refs: https://smartos.org/bugview/OS-2767