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
00:34:22 not ok 365 parallel/test-worker-prof00:34:22 ---00:34:22 duration_ms: 19.97700:34:22 severity: fail00:34:22 exitcode: 100:34:22 stack: |-00:34:22 assert.js:8500:34:22 throw new AssertionError(obj);00:34:22 ^00:34:22 00:34:22 AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:00:34:22 00:34:22 1 !== 200:34:22 00:34:22 at Object.<anonymous> (/home/iojs/build/workspace/node-test-binary-arm/test/parallel/test-worker-prof.js:29:8)00:34:22 at Module._compile (internal/modules/cjs/loader.js:807:30)00:34:22 at Object.Module._extensions..js (internal/modules/cjs/loader.js:818:10)00:34:22 at Module.load (internal/modules/cjs/loader.js:674:32)00:34:22 at tryModuleLoad (internal/modules/cjs/loader.js:606:12)00:34:22 at Function.Module._load (internal/modules/cjs/loader.js:598:3)00:34:22 at Function.Module.runMain (internal/modules/cjs/loader.js:870:12)00:34:22 at internal/main/run_main_module.js:21:1100:34:22 ...
the assertion failure indicates that either the parent or the child - one those did not produce a trace output! (something beyond what we thought could potentially cause flake in this test - i.e., the process timings and the number of ticks etc.)
assert.js:340
throw err;
^
AssertionError [ERR_ASSERTION]: 10 >= 15
at Object.<anonymous> (/home/iojs/build/workspace/node-test-commit-linux-containered/test/parallel/test-worker-prof.js:39:3)
at Module._compile (internal/modules/cjs/loader.js:813:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:824:10)
at Module.load (internal/modules/cjs/loader.js:680:32)
at tryModuleLoad (internal/modules/cjs/loader.js:612:12)
at Function.Module._load (internal/modules/cjs/loader.js:604:3)
at Function.Module.runMain (internal/modules/cjs/loader.js:876:12)
at internal/main/run_main_module.js:21:11
Activity
refack commentedon Mar 10, 2019
https://ci.nodejs.org/job/node-test-binary-arm/6731/RUN_SUBSET=2,label=pi1-docker/testReport/junit/(root)/test/parallel_test_worker_prof/
Worker: https://ci.nodejs.org/computer/test-requireio_davglass-debian9-armv6l_pi1p-1/
mark-as-flaky PR: #26557
gireeshpunathil commentedon Mar 10, 2019
the assertion failure indicates that either the parent or the child - one those did not produce a trace output! (something beyond what we thought could potentially cause flake in this test - i.e., the process timings and the number of ticks etc.)
test: mark `test-worker-prof` as Flaky on ARM
refack commentedon Mar 10, 2019
Now it's flaking on Windows
Worker: https://ci.nodejs.org/computer/test-azure_msft-win10-x64-1/
targos commentedon Mar 11, 2019
Also on Linux without intl:
https://ci.nodejs.org/job/node-test-commit-linux-containered/11274/nodes=ubuntu1604_sharedlibs_withoutintl_x64/testReport/junit/(root)/test/parallel_test_worker_prof/
test: mark test-worker-prof as flake on all platforms
test: mark `test-worker-prof` as Flaky on ARM
test: mark `test-worker-prof` as Flaky on ARM
test: mark test-worker-prof as flake on all platforms
test: mark `test-worker-prof` as Flaky on ARM
test: mark test-worker-prof as flake on all platforms
131 remaining items
test: fix flaky test-worker-prof
joyeecheung commentedon Aug 21, 2023
Still flaky: nodejs/reliability#640
joyeecheung commentedon Aug 21, 2023
I start to wonder if we actually need 15 ticks in the tests. Maybe it's already good enough to run some tests and check the code-creation events...
test: make test-worker-prof more robust
test: make test-worker-prof more robust
shnooshnoo commentedon Dec 12, 2023
I believe this issue can be closed now #37673 (comment)
test: unmark test-worker-prof as flaky