-
Notifications
You must be signed in to change notification settings - Fork 29.9k
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 addons-napi/test_threadsafe_function/test #23621
Comments
https://ci.nodejs.org/job/node-test-binary-windows/21052/COMPILED_BY=vs2017,RUNNER=win2016,RUN_SUBSET=1/console on test-azure_msft-win2016-x64-2 00:57:07 not ok 555 addons-napi/test_threadsafe_function/test
00:57:07 ---
00:57:07 duration_ms: 6.378
00:57:07 severity: fail
00:57:07 exitcode: 134
00:57:07 stack: |-
00:57:07 FATAL ERROR: data_source_thread queue was never full
00:57:07 1: 00007FF749A6F6D5
00:57:07 2: 00007FF749A47816
00:57:07 3: 00007FF749A48200
00:57:07 4: 00007FF749A48219
00:57:07 5: 00007FF749A3ADCD
00:57:07 6: 00007FFDA11F11EE
00:57:07 7: 00007FF749AA8B54
00:57:07 8: 00007FF74A566A70
00:57:07 9: 00007FFDA8B58364
00:57:07 10: 00007FFDAB57E851
00:57:07 ... |
@nodejs/n-api |
https://ci.nodejs.org/job/node-test-binary-windows/21174/COMPILED_BY=vs2017-x86,RUNNER=win2012r2,RUN_SUBSET=1/console on test-azure_msft-win2012r2-x64-2 00:56:39 not ok 556 addons-napi/test_threadsafe_function/test
00:56:39 ---
00:56:39 duration_ms: 2.845
00:56:39 severity: fail
00:56:39 exitcode: 134
00:56:39 stack: |-
00:56:39 FATAL ERROR: data_source_thread queue was never full
00:56:39 1: 009C0B2E node::MakeCallback+3822
00:56:39 2: 7347141C data_source_thread+396 [c:\workspace\node-test-binary-windows\test\addons-napi\test_threadsafe_function\binding.c]:L104 |
@nodejs/platform-windows |
https://ci.nodejs.org/job/node-test-binary-windows/21193/COMPILED_BY=vs2017-x86,RUNNER=win2012r2,RUN_SUBSET=1/console on test-azure_msft-win2012r2-x64-2 15:38:11 not ok 556 addons-napi/test_threadsafe_function/test
15:38:11 ---
15:38:11 duration_ms: 2.898
15:38:11 severity: fail
15:38:11 exitcode: 134
15:38:11 stack: |-
15:38:11 FATAL ERROR: data_source_thread queue was never full
15:38:11 1: 00A30B2E node::MakeCallback+3822
15:38:11 2: 7347141C data_source_thread+396 [c:\workspace\node-test-binary-windows\test\addons-napi\test_threadsafe_function\binding.c]:L104
15:38:11 ... |
@nodejs/build This seems to perhaps be Azure-only failure? |
https://ci.nodejs.org/job/node-test-binary-windows/21995/COMPILED_BY=vs2017-x86,RUNNER=win2012r2,RUN_SUBSET=1/console on test-azure_msft-win2012r2-x64-2: 19:55:05 not ok 555 addons-napi/test_threadsafe_function/test
19:55:05 ---
19:55:05 duration_ms: 2.927
19:55:05 severity: fail
19:55:05 exitcode: 134
19:55:05 stack: |-
19:55:05 FATAL ERROR: data_source_thread queue was never full
19:55:05 1: 00A873FE v8::internal::OptimizedCompilationInfo::bailout_reason+62590
19:55:05 2: 74CE141C data_source_thread+396 [c:\workspace\node-test-binary-windows\test\addons-napi\test_threadsafe_function\binding.c]:L104
19:55:05 ... |
@nodejs/n-api |
The test fails consistently on windows-fanned with vs2017. mark it as flaky while the issue is being progressed, and to keep CI green / amber. Ref: nodejs#23621 PR-URL: nodejs#24714 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Rich Trott <[email protected]>
The test fails consistently on windows-fanned with vs2017. mark it as flaky while the issue is being progressed, and to keep CI green / amber. Ref: #23621 PR-URL: #24714 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Rich Trott <[email protected]>
The test fails consistently on windows-fanned with vs2017. mark it as flaky while the issue is being progressed, and to keep CI green / amber. Ref: nodejs#23621 PR-URL: nodejs#24714 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Rich Trott <[email protected]>
The test fails consistently on windows-fanned with vs2017. mark it as flaky while the issue is being progressed, and to keep CI green / amber. Ref: nodejs#23621 PR-URL: nodejs#24714 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Rich Trott <[email protected]>
The test fails consistently on windows-fanned with vs2017. mark it as flaky while the issue is being progressed, and to keep CI green / amber. Ref: #23621 Backport-PR-URL: #25002 PR-URL: #24714 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Rich Trott <[email protected]>
The test fails consistently on windows-fanned with vs2017. mark it as flaky while the issue is being progressed, and to keep CI green / amber. Ref: #23621 PR-URL: #24714 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Rich Trott <[email protected]>
The test fails consistently on windows-fanned with vs2017. mark it as flaky while the issue is being progressed, and to keep CI green / amber. Ref: #23621 PR-URL: #24714 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Rich Trott <[email protected]>
The test fails consistently on windows-fanned with vs2017. mark it as flaky while the issue is being progressed, and to keep CI green / amber. Ref: #23621 Backport-PR-URL: #25002 PR-URL: #24714 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Rich Trott <[email protected]>
This doesn't seem to come up anymore. Is it possible some of the thread cleanup that happened fixed it as a positive side-effect? |
The test_threadsafe_function doesn't seem to be flaky anymore on Windows. Optimistically removing the flaky designation in the relevant status file. Refs: nodejs#23621 (comment)
The test_threadsafe_function doesn't seem to be flaky anymore on Windows. Optimistically removing the flaky designation in the relevant status file. Refs: nodejs#23621 (comment) PR-URL: nodejs#26403 Reviewed-By: Benjamin Gruenbaum <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]>
The test_threadsafe_function doesn't seem to be flaky anymore on Windows. Optimistically removing the flaky designation in the relevant status file. Refs: nodejs#23621 (comment) PR-URL: nodejs#26403 Reviewed-By: Benjamin Gruenbaum <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]>
The test_threadsafe_function doesn't seem to be flaky anymore on Windows. Optimistically removing the flaky designation in the relevant status file. Refs: #23621 (comment) PR-URL: #26403 Reviewed-By: Benjamin Gruenbaum <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]>
seen again today:
|
I can't reproduce this on Win10 nor on Win2012. Does this happen anymore? |
I can't find any recent occurrences with |
https://ci.nodejs.org/job/node-test-binary-windows/20671/COMPILED_BY=vs2017,RUNNER=win2016,RUN_SUBSET=1/console
The text was updated successfully, but these errors were encountered: