-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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
investigate flaky known_issues/test-vm-timeout-escape-nexttick #24120
Comments
Fails reliably, it seems on Raspberry Pi devices. https://ci.nodejs.org/job/node-test-binary-arm/3931/RUN_SUBSET=0,label=pi1-docker/console 01:56:21 not ok 313 known_issues/test-vm-timeout-escape-nexttick # TODO : Fix flaky test
01:56:21 ---
01:56:21 duration_ms: 2.609
01:56:21 severity: flaky
01:56:21 stack: |-
01:56:21 ... https://ci.nodejs.org/job/node-test-binary-arm/3931/RUN_SUBSET=0,label=pi2-docker/console 00:12:31 not ok 313 known_issues/test-vm-timeout-escape-nexttick # TODO : Fix flaky test
00:12:31 ---
00:12:31 duration_ms: 1.235
00:12:31 severity: flaky
00:12:31 stack: |-
00:12:31 ... https://ci.nodejs.org/job/node-test-binary-arm/3931/RUN_SUBSET=0,label=pi3-docker/console 00:09:09 not ok 313 known_issues/test-vm-timeout-escape-nexttick # TODO : Fix flaky test
00:09:09 ---
00:09:09 duration_ms: 0.927
00:09:09 severity: flaky
00:09:09 stack: |-
00:09:09 ... |
@nodejs/vm |
Increase the timeouts based on platform. This required adjusting common.platformTimeout() to deal with bigint. Fixes: nodejs#24120
Still there testing https://github.com/nodejs/node/commits/8920d5d896b3f9b5df47b02e779ab49136cca085 which includes d8e06b2:
https://ci.nodejs.org/job/node-test-commit-arm-fanned/4141/ |
At least it's flaky now and not reliably failing. Will take a look. Solution might be to make the timeout bigger, which will make the test slower once we get it out of |
Increase the VM timeout. If it is too small, the VM does not exit before the code has a chance to create the problematic condition that causes the timeout to be ignored. Fixes: nodejs#24120
Increase the VM timeout. If it is too small, the VM does not exit before the code has a chance to create the problematic condition that causes the timeout to be ignored. Fixes: nodejs#24120 PR-URL: nodejs#24251 Reviewed-By: Refael Ackermann <refack@gmail.com> Reviewed-By: Richard Lau <riclau@uk.ibm.com> Reviewed-By: Michaël Zasso <targos@protonmail.com>
Fixed in a4a2e9f |
Increase the VM timeout. If it is too small, the VM does not exit before the code has a chance to create the problematic condition that causes the timeout to be ignored. Fixes: #24120 PR-URL: #24251 Reviewed-By: Refael Ackermann <refack@gmail.com> Reviewed-By: Richard Lau <riclau@uk.ibm.com> Reviewed-By: Michaël Zasso <targos@protonmail.com>
Increase the timeouts based on platform. This required adjusting common.platformTimeout() to deal with bigint. Fixes: nodejs#24120 PR-URL: nodejs#24238 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Richard Lau <riclau@uk.ibm.com>
Increase the VM timeout. If it is too small, the VM does not exit before the code has a chance to create the problematic condition that causes the timeout to be ignored. Fixes: nodejs#24120 PR-URL: nodejs#24251 Reviewed-By: Refael Ackermann <refack@gmail.com> Reviewed-By: Richard Lau <riclau@uk.ibm.com> Reviewed-By: Michaël Zasso <targos@protonmail.com>
looks like still failing - https://ci.nodejs.org/job/node-test-binary-arm/4403/RUN_SUBSET=0,label=pi1-docker/console |
Real solution is probably to fix the problem that this is a |
This is a known failure so mark it such, so that CI is green / amber while the issue is being progressed. PR-URL: nodejs#24712 Refs: nodejs#24620 Refs: nodejs#24120 Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Richard Lau <riclau@uk.ibm.com>
Increase the VM timeout. If it is too small, the VM does not exit before the code has a chance to create the problematic condition that causes the timeout to be ignored. Fixes: #24120 PR-URL: #24251 Reviewed-By: Refael Ackermann <refack@gmail.com> Reviewed-By: Richard Lau <riclau@uk.ibm.com> Reviewed-By: Michaël Zasso <targos@protonmail.com>
This is a known failure so mark it such, so that CI is green / amber while the issue is being progressed. PR-URL: nodejs#24712 Refs: nodejs#24620 Refs: nodejs#24120 Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Richard Lau <riclau@uk.ibm.com>
https://ci.nodejs.org/job/node-test-binary-arm/6218/RUN_SUBSET=3,label=pi2-docker/console test-requireio_joeyvandijk-debian9-armv7l_pi2-2 00:09:38 not ok 376 known_issues/test-vm-timeout-escape-nexttick # TODO : Fix flaky test
00:09:38 ---
00:09:38 duration_ms: 1.543
00:09:38 severity: flaky
00:09:38 stack: |-
00:09:38 ... |
test-digitalocean-ubuntu1604_sharedlibs_container-x64-7 00:15:31 not ok 2270 known_issues/test-vm-timeout-escape-nexttick
00:15:31 ---
00:15:31 duration_ms: 1.62
00:15:31 severity: fail
00:15:31 stack: |-
00:15:31 ... |
test-digitalocean-ubuntu1604_sharedlibs_container-x64-1 00:19:50 not ok 2579 known_issues/test-vm-timeout-escape-nexttick
00:19:50 ---
00:19:50 duration_ms: 0.247
00:19:50 severity: fail
00:19:50 stack: |-
00:19:50 ... |
https://ci.nodejs.org/job/node-test-commit-smartos/21423/nodes=smartos16-64/console
@jasnell
The text was updated successfully, but these errors were encountered: