https://ci.nodejs.org/job/node-test-binary-windows/20671/COMPILED_BY=vs2017,RUNNER=win2016,RUN_SUBSET=1/console ```console 11:33:39 not ok 551 addons-napi/test_threadsafe_function/test 11:33:39 --- 11:33:39 duration_ms: 5.819 11:33:39 severity: fail 11:33:39 exitcode: 134 11:33:39 stack: |- 11:33:39 FATAL ERROR: data_source_thread queue was never full 11:33:39 1: 00007FF66985BCE5 11:33:39 2: 00007FF669834F56 11:33:39 3: 00007FF669835940 11:33:39 4: 00007FF669835959 11:33:39 5: 00007FF66982843D 11:33:39 6: 00007FFC92A711EE 11:33:39 7: 00007FF669894884 11:33:39 8: 00007FF66A33D660 11:33:39 9: 00007FFC983B8364 11:33:39 10: 00007FFC9894E851 11:33:39 ... ```
Activity
addaleax commentedon Oct 12, 2018
@gabrielschulhof
Trott commentedon Oct 26, 2018
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
Trott commentedon Oct 26, 2018
@nodejs/n-api
Trott commentedon Nov 1, 2018
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
Trott commentedon Nov 1, 2018
@nodejs/platform-windows
Trott commentedon Nov 2, 2018
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
Trott commentedon Nov 2, 2018
@nodejs/build This seems to perhaps be Azure-only failure?
Trott commentedon Nov 28, 2018
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:
Trott commentedon Nov 28, 2018
@nodejs/n-api
test: mark test_threadsafe_function/test as flaky
test: mark test_threadsafe_function/test as flaky
2 remaining items
test: mark test_threadsafe_function/test as flaky
test: mark test_threadsafe_function/test as flaky
test: mark test_threadsafe_function/test as flaky
test: mark test_threadsafe_function/test as flaky
Trott commentedon Mar 2, 2019
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?
test: remove flaky designation for test_threadsafe_function
test: remove flaky designation for test_threadsafe_function
test: remove flaky designation for test_threadsafe_function
test: remove flaky designation for test_threadsafe_function
gireeshpunathil commentedon Nov 25, 2019
seen again today:
ref: https://ci.nodejs.org/job/node-test-binary-windows-2/COMPILED_BY=vs2017-x86,RUNNER=win2012r2,RUN_SUBSET=addons/4470/consoleFull
bzoz commentedon Mar 26, 2020
I can't reproduce this on Win10 nor on Win2012. Does this happen anymore?
Trott commentedon Mar 30, 2020
I can't find any recent occurrences with
ncu-ci walkso I think we can close this.