Skip to content

Investigate flaky test-worker-prof #26401

Description

@Trott

https://ci.nodejs.org/job/node-test-binary-arm/6472/RUN_SUBSET=0,label=pi1-docker/console

test-requireio_ceejbot-debian9-armv6l_pi1p-1

00:34:22 not ok 365 parallel/test-worker-prof
00:34:22   ---
00:34:22   duration_ms: 19.977
00:34:22   severity: fail
00:34:22   exitcode: 1
00:34:22   stack: |-
00:34:22     assert.js:85
00: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 !== 2
00: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:11
00:34:22   ...

Activity

  1. added
    flaky-testIssues and PRs involving tests that fail intermittently in CI.
    workerIssues and PRs related to the worker_threads module and Worker API.
    on Mar 2, 2019
  2. gireeshpunathil commented on Mar 10, 2019

    @gireeshpunathil
    Member

    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.)

  3. refack commented on Mar 10, 2019

    @refack
    Contributor

    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
  4. added
    windowsIssues and PRs related to the Windows platform.
    armIssues and PRs related to the ARM architecture.
    on Mar 10, 2019
  5. targos commented on Mar 11, 2019

    @targos
    Member

    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/

    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
    
  6. 131 remaining items

  7. added a commit that references this issue on Feb 28, 2021
  8. joyeecheung commented on Aug 21, 2023

    @joyeecheung
    Member
  9. joyeecheung commented on Aug 21, 2023

    @joyeecheung
    Member

    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...

  10. shnooshnoo commented on Dec 12, 2023

    @shnooshnoo

    I believe this issue can be closed now #37673 (comment)

  11. added a commit that references this issue on Jul 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    flaky-testIssues and PRs involving tests that fail intermittently in CI.workerIssues and PRs related to the worker_threads module and Worker API.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions