Repository navigation
Investigate flaky test-worker-prof #26401
Copy link
Copy link
Closed
Labels
flaky-testIssues and PRs involving tests that fail intermittently in CI.Issues and PRs involving tests that fail intermittently in CI.workerIssues and PRs related to the worker_threads module and Worker API.Issues and PRs related to the worker_threads module and Worker API.
Description
Activity
- addedflaky-testIssues and PRs involving tests that fail intermittently in CI.Issues and PRs involving tests that fail intermittently in CI.workerIssues and PRs related to the worker_threads module and Worker API.Issues and PRs related to the worker_threads module and Worker API.
on Mar 2, 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.)
- added a commit that references this issue
on Mar 10, 2019 Now it's flaking on Windows
Worker: https://ci.nodejs.org/computer/test-azure_msft-win10-x64-1/assert.js:340 throw err; ^ AssertionError [ERR_ASSERTION]: 3 >= 15 at Object.<anonymous> (c:\workspace\node-test-binary-windows\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
- addedwindowsIssues and PRs related to the Windows platform.Issues and PRs related to the Windows platform.armIssues and PRs related to the ARM architecture.Issues and PRs related to the ARM architecture.
on Mar 10, 2019 Also on Linux without intl:
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- added a commit that references this issue
on Mar 12, 2019 - added 5 commits that reference this issue
on Mar 13, 2019 131 remaining items
- added a commit that references this issue
on Feb 28, 2021 Still flaky: nodejs/reliability#640
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...
- added a commit that references this issue
on Sep 4, 2023 - added a commit that references this issue
on Sep 28, 2023 I believe this issue can be closed now #37673 (comment)
- added a commit that references this issue
on Jul 27, 2026
Metadata
Metadata
Assignees
Labels
flaky-testIssues and PRs involving tests that fail intermittently in CI.Issues and PRs involving tests that fail intermittently in CI.workerIssues and PRs related to the worker_threads module and Worker API.Issues and PRs related to the worker_threads module and Worker API.
https://ci.nodejs.org/job/node-test-binary-arm/6472/RUN_SUBSET=0,label=pi1-docker/console
test-requireio_ceejbot-debian9-armv6l_pi1p-1