CI Reliability 2022-01-27

Open
#184 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
node.js, shell

Research direction

Start with the Jenkins runs linked in the report and reproduce the recurring failures, then inspect the named tests such as test/parallel/test-fs-rmdir-recursive and test/parallel/test-child-process-pipe-dataflow.js. Compare the failure logs across affected platforms and determine the underlying causes. Done means the reported CI failures are addressed and the relevant test runs are green.

Written by the indexing model from the issue text.

Description

Failures in node-test-pull-request/42079 to node-test-pull-request/42178 that failed more than 2 PRs
(Generated with ncu-ci walk pr --stats=true --markdown /home/runner/work/reliability/reliability/results.md)

UTC Time RUNNING SUCCESS UNSTABLE ABORTED FAILURE Green Rate
2022-01-27 00:07 0 7 15 7 71 7.53%
Jenkins Failure
Git Failure
Build Failure
Reason ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error?
Type BUILD_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/41692/, https://github.com/nodejs/node/pull/41684/)
Appeared test-requireio_ceejbot-debian10-armv7l_pi2-1, test-requireio_davglass-debian10-arm64_pi3-1, test-requireio_joeyvandijk-debian10-armv7l_pi2-2, test-requireio_securogroup-debian10-arm64_pi3-1, test-requireio_svincent-debian10-armv7l_pi2-2, test-requireio_williamkapke-debian10-arm64_pi3-2, test-requireio_rvagg-debian10-armv7l_pi2-1, test-requireio_piccoloaiutante-debian10-arm64_pi3-1, test-requireio_joeyvandijk-debian10-armv7l_pi2-1, test-requireio_securogroup-debian10-arm64_pi3-2, test-requireio_jasnell-debian10-armv7l_pi2-1, test-digitalocean-freebsd12-x64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/42143/
Last CI https://ci.nodejs.org/job/node-test-pull-request/42175/
Example
ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error?
[PostBuildScript] - [INFO] Executing post build scripts.
[node-test-binary-arm] $ /bin/bash -ex /tmp/jenkins473349596480376235.sh
+ '[' -d .git ']'
+ git clean -fdx

JSTest Failure
Reason parallel/test-fs-rmdir-recursive
Type JS_TEST_FAILURE
Failed PR 8 (https://github.com/nodejs/node/pull/41667/, https://github.com/nodejs/node/pull/41663/, https://github.com/nodejs/node/pull/41632/, https://github.com/nodejs/node/pull/41682/, https://github.com/nodejs/node/pull/41502/, https://github.com/nodejs/node/pull/41684/, https://github.com/nodejs/node/pull/41681/, https://github.com/nodejs/node/pull/41652/)
Appeared test-azure_msft-win10_vcbt2015-x64-4, test-azure_msft-win10_vs2019-x64-3, test-azure_msft-win10_vcbt2015-x64-3, test-azure_msft-win10_vs2019-x64-1, test-azure_msft-win10_vcbt2015-x64-1, test-requireio_mininodes-debian10-armv7l_pi2-1
First CI https://ci.nodejs.org/job/node-test-pull-request/42104/
Last CI https://ci.nodejs.org/job/node-test-pull-request/42167/
Example
not ok 259 parallel/test-fs-rmdir-recursive
  ---
  duration_ms: 0.759
  severity: fail
  exitcode: 1
  stack: |-
    (node:9100) [DEP0147] DeprecationWarning: In future versions of Node.js, fs.rmdir(path, { recursive: true }) will be removed. Use fs.rm(path, { recursive: true }) instead
    (Use `node --trace-deprecation ...` to show where the warning was created)
    Can't clean tmpdir: C:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.256
    Files blocking: [ 'rmdir-recursive-0', 'rmdir-recursive-4', 'rmdir-recursive-5' ]
    
    node:assert:991
        throw newErr;
        ^
    
    AssertionError [ERR_ASSERTION]: ifError got unwanted exception: ENOTEMPTY: directory not empty, rmdir 'C:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.256\rmdir-recursive-0\d-3-1\d-2-1\d-1-2'
        at C:\workspace\node-test-binary-windows-js-suites\node\test\common\index.js:364:12
        at C:\workspace\node-test-binary-windows-js-suites\node\test\common\index.js:401:15
        at node:fs:188...

Reason sequential/test-cpu-prof-worker-argv
Type JS_TEST_FAILURE
Failed PR 6 (https://github.com/nodejs/node/pull/41600/, https://github.com/nodejs/node/pull/41620/, https://github.com/nodejs/node/pull/41632/, https://github.com/nodejs/node/pull/41642/, https://github.com/nodejs/node/pull/41663/, https://github.com/nodejs/node/pull/41652/)
Appeared test-digitalocean-freebsd12-x64-1, test-digitalocean-freebsd12-x64-2, test-orka-macos11-x64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/42084/
Last CI https://ci.nodejs.org/job/node-test-pull-request/42167/
Example
not ok 3452 sequential/test-cpu-prof-worker-argv
  ---
  duration_ms: 0.755
  severity: fail
  exitcode: 1
  stack: |-
    
    [
      {
        id: 1,
        callFrame: {
          functionName: '(root)',
          scriptId: '0',
          url: '',
          lineNumber: -1,
          columnNumber: -1
        },
        hitCount: 0,
        children: [ 2, 3, 14, 50, 51 ]
      },
      {
        id: 2,
        callFrame: {
          functionName: '(program)',
          scriptId: '0',
          url: '',
          lineNumber: -1,
          columnNumber: -1
        },
        hitCount: 1
      },
      {
        id: 3,
        callFrame: {
          functionName: '',
          scriptId: '10',
          url: 'node:internal/bootstrap/node',
          lineNumber: 0,
          columnNumber: 0
        },
        hitCount: 0,
        children: [ 4, 10, 13 ]
      },
      {
        id: 4,
        callFrame: {
          functionName: 'setupBuffer',
          scriptId: '10',
          url: 'node:internal/bootstrap/nod...

Reason parallel/test-common-expect-warning
Type JS_TEST_FAILURE
Failed PR 5 (https://github.com/nodejs/node/pull/41667/, https://github.com/nodejs/node/pull/41664/, https://github.com/nodejs/node/pull/41502/, https://github.com/nodejs/node/pull/41681/, https://github.com/nodejs/node/pull/41652/)
Appeared test-equinix-ubuntu2004_container-arm64-2, test-equinix-ubuntu1804_sharedlibs_container-arm64-1, test-equinix-centos7_container-arm64-1, test-equinix-centos7_container-arm64-2, test-equinix-ubuntu2004_sharedlibs_container-arm64-6, test-requireio_piccoloaiutante-debian10-arm64_pi3-1
First CI https://ci.nodejs.org/job/node-test-pull-request/42104/
Last CI https://ci.nodejs.org/job/node-test-pull-request/42171/
Example
not ok 325 parallel/test-common-expect-warning
  ---
  duration_ms: 0.456
  severity: fail
  exitcode: 1
  stack: |-
    node:assert:1026
        throw err;
        ^
    
    AssertionError [ERR_ASSERTION]: The input did not match the regular expression /Unexpected extra warning received/. Input:
    
    ''
    
        at ChildProcess.<anonymous> (/home/iojs/build/workspace/node-test-commit-arm/test/parallel/test-common-expect-warning.js:41:14)
        at ChildProcess.<anonymous> (/home/iojs/build/workspace/node-test-commit-arm/test/common/index.js:401:15)
        at ChildProcess.emit (node:events:522:28)
        at Process.ChildProcess._handle.onexit (node:internal/child_process:291:12) {
      generatedMessage: true,
      code: 'ERR_ASSERTION',
      actual: '',
      expected: /Unexpected extra warning received/,
      operator: 'match'
    }
    
    Node.js v18.0.0-pre
  ...


Reason parallel/test-child-process-pipe-dataflow
Type JS_TEST_FAILURE
Failed PR 4 (https://github.com/nodejs/node/pull/41651/, https://github.com/nodejs/node/pull/41682/, https://github.com/nodejs/node/pull/41502/, https://github.com/nodejs/node/pull/41652/)
Appeared test-azure_msft-win10_vs2019-x64-4
First CI https://ci.nodejs.org/job/node-test-pull-request/42119/
Last CI https://ci.nodejs.org/job/node-test-pull-request/42132/
Example
not ok 81 parallel/test-child-process-pipe-dataflow
  ---
  duration_ms: 1.1
  severity: fail
  exitcode: 1
  stack: |-
    assert.js:101
      throw new AssertionError(obj);
      ^
    
    AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:
    
    '0' !== '1048577'
    
        at Socket.<anonymous> (C:\workspace\node-test-binary-windows-js-suites\node\test\parallel\test-child-process-pipe-dataflow.js:66:12)
        at Socket.<anonymous> (C:\workspace\node-test-binary-windows-js-suites\node\test\common\index.js:366:15)
        at Socket.emit (events.js:314:20)
        at addChunk (_stream_readable.js:297:12)
        at readableAddChunk (_stream_readable.js:272:9)
        at Socket.Readable.push (_stream_readable.js:213:10)
        at Pipe.onStreamRead (internal/stream_base_commons.js:188:23) {
      generatedMessage: true,
      code: 'ERR_ASSERTION',
      actual: '0',
      expected: '1048577',
      operator: 'strictEqual'
    }
  ...


Reason parallel/test-crypto-secure-heap
Type JS_TEST_FAILURE
Failed PR 4 (https://github.com/nodejs/node/pull/41667/, https://github.com/nodejs/node/pull/41664/, https://github.com/nodejs/node/pull/41502/, https://github.com/nodejs/node/pull/41692/)
Appeared test-requireio_svincent-debian10-armv7l_pi2-2, test-requireio_davglass-debian10-arm64_pi3-1, test-requireio_ceejbot-debian10-armv7l_pi2-1, test-requireio_williamkapke-debian10-arm64_pi3-2
First CI https://ci.nodejs.org/job/node-test-pull-request/42104/
Last CI https://ci.nodejs.org/job/node-test-pull-request/42143/
Example
not ok 233 parallel/test-crypto-secure-heap
  ---
  duration_ms: 240.89
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...


Reason parallel/test-finalization-group-regular-gc
Type JS_TEST_FAILURE
Failed PR 4 (https://github.com/nodejs/node/pull/41651/, https://github.com/nodejs/node/pull/41682/, https://github.com/nodejs/node/pull/41502/, https://github.com/nodejs/node/pull/41652/)
Appeared test-azure_msft-win10_vs2019-x64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/42119/
Last CI https://ci.nodejs.org/job/node-test-pull-request/42132/
Example
not ok 182 parallel/test-finalization-group-regular-gc
  ---
  duration_ms: 1.511
  severity: fail
  exitcode: 3221226505
  stack: |-
    Assertion failed: !(handle->flags & UV_HANDLE_CLOSING), file c:\workspace\node-compile-windows\node\deps\uv\src\win\async.c, line 76
  ...


Reason parallel/test-fs-rm
Type JS_TEST_FAILURE
Failed PR 4 (https://github.com/nodejs/node/pull/41612/, https://github.com/nodejs/node/pull/41667/, https://github.com/nodejs/node/pull/41652/, https://github.com/nodejs/node/pull/41681/)
Appeared test-azure_msft-win10_vs2019-x64-4, test-azure_msft-win10_vcbt2015-x64-2, test-requireio_jasnell-debian10-armv7l_pi2-1
First CI https://ci.nodejs.org/job/node-test-pull-request/42088/
Last CI https://ci.nodejs.org/job/node-test-pull-request/42174/
Example
not ok 270 parallel/test-fs-rm
  ---
  duration_ms: 2.521
  severity: fail
  exitcode: 1
  stack: |-
    node:internal/process/promises:265
                triggerUncaughtException(err, true /* fromPromise */);
                ^
    
    [Error: ENOTEMPTY: directory not empty, rmdir 'C:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.256\rm-5\d-3-1\d-2-2\d-1-2'] {
      errno: -4051,
      code: 'ENOTEMPTY',
      syscall: 'rmdir',
      path: 'C:\\workspace\\node-test-binary-windows-js-suites\\node\\test\\.tmp.256\\rm-5\\d-3-1\\d-2-2\\d-1-2'
    }
    
    Node.js v18.0.0-pre
  ...


Reason node-api/test_fatal/test_threads
Type JS_TEST_FAILURE
Failed PR 3 (https://github.com/nodejs/node/pull/41663/, https://github.com/nodejs/node/pull/41692/, https://github.com/nodejs/node/pull/41681/)
Appeared test-joyent-smartos20-x64-3
First CI https://ci.nodejs.org/job/node-test-pull-request/42126/
Last CI https://ci.nodejs.org/job/node-test-pull-request/42174/
Example
not ok 3378 node-api/test_fatal/test_threads
  ---
  duration_ms: 120.99
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...


Reason node-api/test_fatal/test_threads_report
Type JS_TEST_FAILURE
Failed PR 3 (https://github.com/nodejs/node/pull/41663/, https://github.com/nodejs/node/pull/41692/, https://github.com/nodejs/node/pull/41681/)
Appeared test-joyent-smartos20-x64-3
First CI https://ci.nodejs.org/job/node-test-pull-request/42126/
Last CI https://ci.nodejs.org/job/node-test-pull-request/42174/
Example
not ok 3379 node-api/test_fatal/test_threads_report
  ---
  duration_ms: 120.315
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...


Reason parallel/test-crypto-dh-constructor
Type JS_TEST_FAILURE
Failed PR 3 (https://github.com/nodejs/node/pull/41662/, https://github.com/nodejs/node/pull/41684/, https://github.com/nodejs/node/pull/41692/)
Appeared test-requireio_joeyvandijk-debian10-armv7l_pi2-2, test-requireio_svincent-debian10-armv7l_pi2-3, test-requireio_svincent-debian10-armv7l_pi2-2
First CI https://ci.nodejs.org/job/node-test-pull-request/42108/
Last CI https://ci.nodejs.org/job/node-test-pull-request/42143/
Example
not ok 189 parallel/test-crypto-dh-constructor
  ---
  duration_ms: 240.129
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...


Reason abort/test-abort-backtrace
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/41612/, https://github.com/nodejs/node/pull/41663/)
Appeared test-joyent-smartos20-x64-3
First CI https://ci.nodejs.org/job/node-test-pull-request/42091/
Last CI https://ci.nodejs.org/job/node-test-pull-request/42125/
Example
not ok 3589 abort/test-abort-backtrace
  ---
  duration_ms: 120.164
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...


Reason abort/test-abort-fatal-error
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/41612/, https://github.com/nodejs/node/pull/41663/)
Appeared test-joyent-smartos20-x64-3
First CI https://ci.nodejs.org/job/node-test-pull-request/42091/
Last CI https://ci.nodejs.org/job/node-test-pull-request/42125/
Example
not ok 3590 abort/test-abort-fatal-error
  ---
  duration_ms: 120.172
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...


Reason async-hooks/test-callback-error
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/41612/, https://github.com/nodejs/node/pull/41663/)
Appeared test-joyent-smartos20-x64-3
First CI https://ci.nodejs.org/job/node-test-pull-request/42090/
Last CI https://ci.nodejs.org/job/node-test-pull-request/42126/
Example
not ok 462 async-hooks/test-callback-error
  ---
  duration_ms: 120.152
  severity: fail
  exitcode: -15
  stack: |-
    timeout
    start case 1
    end case 1: 279.989ms
    start case 2
    end case 2: 329.512ms
    start case 3
  ...


Reason parallel/test-child-process-fork-closed-channel-segfault
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/41681/, https://github.com/nodejs/node/pull/41698/)
Appeared test-requireio_ceejbot-debian10-armv7l_pi2-1, test-requireio_mcollina-debian10-armv7l_pi2-1
First CI https://ci.nodejs.org/job/node-test-pull-request/42169/
Last CI https://ci.nodejs.org/job/node-test-pull-request/42177/
Example
not ok 104 parallel/test-child-process-fork-closed-channel-segfault
  ---
  duration_ms: 4.616
  severity: fail
  exitcode: 1
  stack: |-
    /home/iojs/build/workspace/node-test-binary-arm/test/parallel/test-child-process-fork-closed-channel-segfault.js:83
                throw err;
                ^
    
    Error: write EPIPE
        at ChildProcess.target._send (node:internal/child_process:864:20)
        at ChildProcess.<anonymous> (node:internal/child_process:667:16)
        at ChildProcess.emit (node:events:534:35)
        at emit (node:internal/child_process:936:14)
        at processTicksAndRejections (node:internal/process/task_queues:84:21) {
      errno: -32,
      code: 'EPIPE',
      syscall: 'write'
    }
    
    Node.js v18.0.0-pre
  ...


Reason parallel/test-crypto-classes
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/41612/, https://github.com/nodejs/node/pull/41681/)
Appeared test-requireio_mininodes-debian10-armv7l_pi2-1, test-requireio_svincent-debian10-armv7l_pi2-2
First CI https://ci.nodejs.org/job/node-test-pull-request/42086/
Last CI https://ci.nodejs.org/job/node-test-pull-request/42172/
Example
not ok 208 parallel/test-crypto-classes
  ---
  duration_ms: 240.76
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...


Reason parallel/test-crypto-dh
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/41600/, https://github.com/nodejs/node/pull/41502/)
Appeared test-requireio_mcollina-debian10-armv7l_pi2-1, test-requireio_svincent-debian10-armv7l_pi2-3
First CI https://ci.nodejs.org/job/node-test-pull-request/42084/
Last CI https://ci.nodejs.org/job/node-test-pull-request/42164/
Example
not ok 206 parallel/test-crypto-dh
  ---
  duration_ms: 240.73
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...


Reason parallel/test-crypto-dh-leak
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/41620/, https://github.com/nodejs/node/pull/41502/)
Appeared test-requireio_ceejbot-debian10-armv7l_pi2-1, test-requireio_davglass-debian10-arm64_pi3-1
First CI https://ci.nodejs.org/job/node-test-pull-request/42089/
Last CI https://ci.nodejs.org/job/node-test-pull-request/42168/
Example
not ok 210 parallel/test-crypto-dh-leak
  ---
  duration_ms: 240.87
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...


Reason parallel/test-domain-no-error-handler-abort-on-uncaught-2
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/41612/, https://github.com/nodejs/node/pull/41663/)
Appeared test-joyent-smartos20-x64-3
First CI https://ci.nodejs.org/job/node-test-pull-request/42091/
Last CI https://ci.nodejs.org/job/node-test-pull-request/42125/
Example
not ok 684 parallel/test-domain-no-error-handler-abort-on-uncaught-2
  ---
  duration_ms: 120.174
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...


Reason parallel/test-domain-no-error-handler-abort-on-uncaught-3
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/41612/, https://github.com/nodejs/node/pull/41663/)
Appeared test-joyent-smartos20-x64-3
First CI https://ci.nodejs.org/job/node-test-pull-request/42091/
Last CI https://ci.nodejs.org/job/node-test-pull-request/42125/
Example
not ok 685 parallel/test-domain-no-error-handler-abort-on-uncaught-3
  ---
  duration_ms: 120.166
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...


Reason parallel/test-domain-no-error-handler-abort-on-uncaught-4
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/41612/, https://github.com/nodejs/node/pull/41663/)
Appeared test-joyent-smartos20-x64-3
First CI https://ci.nodejs.org/job/node-test-pull-request/42091/
Last CI https://ci.nodejs.org/job/node-test-pull-request/42113/
Example
not ok 687 parallel/test-domain-no-error-handler-abort-on-uncaught-4
  ---
  duration_ms: 120.116
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...


Reason parallel/test-domain-no-error-handler-abort-on-uncaught-5
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/41612/, https://github.com/nodejs/node/pull/41663/)
Appeared test-joyent-smartos20-x64-3
First CI https://ci.nodejs.org/job/node-test-pull-request/42091/
Last CI https://ci.nodejs.org/job/node-test-pull-request/42105/
Example
not ok 687 parallel/test-domain-no-error-handler-abort-on-uncaught-5
  ---
  duration_ms: 120.140
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...


Reason parallel/test-stdout-to-file
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/41612/, https://github.com/nodejs/node/pull/41681/)
Appeared test-azure_msft-win10_vs2019-x64-4, test-azure_msft-win10_vs2019-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/42088/
Last CI https://ci.nodejs.org/job/node-test-pull-request/42172/
Example
not ok 582 parallel/test-stdout-to-file
  ---
  duration_ms: 1.803
  severity: fail
  exitcode: 1
  stack: |-
    1048576 chars to C:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.571\stdout.txt...
    done!
    C:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.571\stdout.txt has 1048576 bytes
    Done printing with string
    1048576 chars to C:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.571\stdout.txt...
    Can't clean tmpdir: C:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.571
    Files blocking: [ 'stdout.txt' ]
    
    node:assert:991
        throw newErr;
        ^
    
    AssertionError [ERR_ASSERTION]: ifError got unwanted exception: Command failed: "C:\workspace\node-test-binary-windows-js-suites\node\Release\node.exe" "C:\workspace\node-test-binary-windows-js-suites\node\test\fixtures\print-chars-from-buffer.js" 1048576 > "C:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.571\stdout.txt"
    Access is denied.
    
    
      ...

Reason parallel/test-stream-map
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/41664/, https://github.com/nodejs/node/pull/41642/)
Appeared test-requireio_ceejbot-debian10-armv7l_pi2-1, test-requireio_svincent-debian10-armv7l_pi2-3, test-requireio_mininodes-debian10-armv7l_pi2-1
First CI https://ci.nodejs.org/job/node-test-pull-request/42114/
Last CI https://ci.nodejs.org/job/node-test-pull-request/42117/
Example
not ok 578 parallel/test-stream-map
  ---
  duration_ms: 2.362
  severity: fail
  exitcode: 1
  stack: |-
    undefined
    undefined
    node:assert:123
      throw new AssertionError(obj);
      ^
    
    AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:
    
    4 !== 2
    
        at Immediate._onImmediate (/home/iojs/build/workspace/node-test-binary-arm/test/parallel/test-stream-map.js:158:12)
        at processImmediate (node:internal/timers:466:21) {
      generatedMessage: true,
      code: 'ERR_ASSERTION',
      actual: 4,
      expected: 2,
      operator: 'strictEqual'
    }
    
    Node.js v18.0.0-pre
  ...


Reason parallel/test-trace-events-fs-sync
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/41664/, https://github.com/nodejs/node/pull/41681/)
Appeared test-azure_msft-win10_vs2019-x64-1, test-azure_msft-win10_vcbt2015-x64-4
First CI https://ci.nodejs.org/job/node-test-pull-request/42095/
Last CI https://ci.nodejs.org/job/node-test-pull-request/42173/
Example
not ok 689 parallel/test-trace-events-fs-sync
  ---
  duration_ms: 2.276
  severity: fail
  exitcode: 1
  stack: |-
    Can't clean tmpdir: C:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.684
    Files blocking: [ 'fs.txt', 'node_trace.1.log' ]
    
    C:\workspace\node-test-binary-windows-js-suites\node\test\parallel\test-trace-events-fs-sync.js:133
        throw new Error(`${tr}:\n${util.inspect(proc)}`);
        ^
    
    Error: fs.sync.fstat:
    {
      status: 1,
      signal: null,
      output: [
        null,
        '',
        'node:internal/fs/utils:344\r\n' +
          '    throw err;\r\n' +
          '    ^\r\n' +
          '\r\n' +
          "Error: EPERM: operation not permitted, open 'fs.txt'\r\n" +
          '    at Object.openSync (node:fs:585:3)\r\n' +
          '    at Object.writeFileSync (node:fs:2155:35)\r\n' +
          '    at [eval]:1:4\r\n' +
          '    at Script.runInThisContext (node:vm:129:12)\r\n' +
          '    at Object.runInThisContext (node:vm:305:38)...

Reason parallel/test-windows-failed-heap-allocation
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/41652/, https://github.com/nodejs/node/pull/41681/)
Appeared test-azure_msft-win10_vcbt2015-x64-4, test-azure_msft-win10_vs2019-x64-1, test-azure_msft-win10_vcbt2015-x64-2, test-azure_msft-win10_vcbt2015-x64-1, test-azure_msft-win10_vs2019-x64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/42171/
Last CI https://ci.nodejs.org/job/node-test-pull-request/42173/
Example
not ok 754 parallel/test-windows-failed-heap-allocation
  ---
  duration_ms: 1.725
  severity: fail
  exitcode: 1
  stack: |-
    
    
    <--- Last few GCs --->
    
    [8412:0000015ECFDE8D30]       20 ms: Mark-sweep 2.6 (4.9) -> 2.5 (4.9) MB, 2.5 / 0.0 ms  (average mu = 0.652, current mu = 0.652) allocation failure GC in old space requested
    [8412:0000015ECFDE8D30]       26 ms: Mark-sweep 2.8 (5.1) -> 2.8 (5.4) MB, 3.7 / 0.0 ms  (average mu = 0.525, current mu = 0.374) allocation failure GC in old space requested
    
    
    <--- JS stacktrace --->
    
    
    #
    # Fatal javascript OOM in Reached heap limit
    #
    
    
    node:assert:123
      throw new AssertionError(obj);
      ^
    
    AssertionError [ERR_ASSERTION]: Wrong exit code of 2147483651! Expected 134 for abort
        at C:\workspace\node-test-binary-windows-js-suites\node\test\parallel\test-windows-failed-heap-allocation.js:29:10
        at C:\workspace\node-test-binary-windows-js-suites\node\test\common\index.js:401:15
    ...

Reason report/test-report-fatal-error
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/41612/, https://github.com/nodejs/node/pull/41663/)
Appeared test-joyent-smartos20-x64-3
First CI https://ci.nodejs.org/job/node-test-pull-request/42090/
Last CI https://ci.nodejs.org/job/node-test-pull-request/42126/
Example
not ok 403 report/test-report-fatal-error
  ---
  duration_ms: 120.164
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...


Reason sequential/test-debugger-heap-profiler
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/41663/, https://github.com/nodejs/node/pull/41664/)
Appeared test-requireio_svincent-debian10-armv7l_pi2-2, test-requireio_williamkapke-debian10-arm64_pi3-2, test-requireio_mininodes-debian10-armv7l_pi2-1
First CI https://ci.nodejs.org/job/node-test-pull-request/42105/
Last CI https://ci.nodejs.org/job/node-test-pull-request/42106/
Example
not ok 825 sequential/test-debugger-heap-profiler
  ---
  duration_ms: 36.202
  severity: fail
  exitcode: 1
  stack: |-
    /home/iojs/build/workspace/node-test-binary-arm/test/common/debugger.js:84
              reject(new Error([
                     ^
    
    Error: Timeout (10000) while waiting for />\s+$/; found: 
    Heap snapshot: 0/0
    Cannot take heap snapshot because another snapshot is in progress.
    
    
    Heap snapshot: 0/35376
    
    Heap snapshot: 10000/35376
    
    Heap snapshot: 20000/35376
    
    Heap snapshot: 30000/35376
    
    Heap snapshot: 35375/35376
    
    Heap snapshot: 35376/35376
    
    Heap snaphost prepared.
    
    
    Writing snapshot: 102400
    
    Writing snapshot: 204800
    
    Writing snapshot: 307200
    
    Writing snapshot: 409600
    
    Writing snapshot: 512000
    
    Writing snapshot: 614400
    
    Writing snapshot: 716800
    
    Writing snapshot: 819200
    
    Writing snapshot: 921600
    
    Writing snapshot: 1024000
    
    Wr...

Reason sequential/test-debugger-restart-message
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/41667/, https://github.com/nodejs/node/pull/41663/)
Appeared test-requireio_pivotalagency-debian10-arm64_pi3-2, test-requireio_mcollina-debian10-armv7l_pi2-1
First CI https://ci.nodejs.org/job/node-test-pull-request/42104/
Last CI https://ci.nodejs.org/job/node-test-pull-request/42105/
Example
not ok 829 sequential/test-debugger-restart-message
  ---
  duration_ms: 36.359
  severity: fail
  exitcode: 1
  stack: |-
    /home/iojs/build/workspace/node-test-binary-arm/test/common/debugger.js:84
              reject(new Error([
                     ^
    
    Error: Timeout (10000) while waiting for /(?:assert|break|break on start|debugCommand|exception|other|promiseRejection) in/i; found: 
    < Debugger ending on ws://127.0.0.1:9229/9b0ce4c3-02c1-44a5-adb3-e8b72bc5c85b
    < For help, see: https://nodejs.org/en/docs/inspector
    < 
    debug> 
        at Timeout.<anonymous> (/home/iojs/build/workspace/node-test-binary-arm/test/common/debugger.js:84:18)
        at listOnTimeout (node:internal/timers:559:17)
        at processTimers (node:internal/timers:502:7)
    
    Node.js v18.0.0-pre
  ...


Reason sequential/test-debugger-run-after-quit-restart
Type JS_TEST_FAILURE
Failed PR 2 (https://github.com/nodejs/node/pull/41663/, https://github.com/nodejs/node/pull/41664/)
Appeared test-requireio_svincent-debian10-armv7l_pi2-2, test-requireio_williamkapke-debian10-arm64_pi3-2, test-requireio_mininodes-debian10-armv7l_pi2-1
First CI https://ci.nodejs.org/job/node-test-pull-request/42105/
Last CI https://ci.nodejs.org/job/node-test-pull-request/42106/
Example
not ok 828 sequential/test-debugger-run-after-quit-restart
  ---
  duration_ms: 30.509
  severity: fail
  exitcode: 1
  stack: |-
    /home/iojs/build/workspace/node-test-binary-arm/test/common/debugger.js:84
              reject(new Error([
                     ^
    
    Error: Timeout (10000) while waiting for /(?:assert|break|break on start|debugCommand|exception|other|promiseRejection) in/i; found: 
    < Debugger ending on ws://127.0.0.1:9229/ffce4369-4069-4ee7-88c8-71390bfa6e82
    < For help, see: https://nodejs.org/en/docs/inspector
    < 
    debug> 
    
    < Debugger listening on ws://127.0.0.1:9229/3874777e-8ec5-4626-af11-7f12ff16d372
    < For help, see: https://nodejs.org/en/docs/inspector
    < 
    debug> 
    
    connecting to 127.0.0.1:9229 ...
     ok
    
    debug> 
    
    < Debugger attached.
    < 
    debug> 
        at Timeout.<anonymous> (/home/iojs/build/workspace/node-test-binary-arm/test/common/debugger.js:84:18)
        at listOnTimeout (node:internal/timers:559:17)
        ...

Progress
  • ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error? (2)
  • parallel/test-fs-rmdir-recursive (8)
  • sequential/test-cpu-prof-worker-argv (6)
  • parallel/test-common-expect-warning (5)
  • parallel/test-child-process-pipe-dataflow (4)
  • parallel/test-crypto-secure-heap (4)
  • parallel/test-finalization-group-regular-gc (4)
  • parallel/test-fs-rm (4)
  • node-api/test_fatal/test_threads (3)
  • node-api/test_fatal/test_threads_report (3)
  • parallel/test-crypto-dh-constructor (3)
  • abort/test-abort-backtrace (2)
  • abort/test-abort-fatal-error (2)
  • async-hooks/test-callback-error (2)
  • parallel/test-child-process-fork-closed-channel-segfault (2)
  • parallel/test-crypto-classes (2)
  • parallel/test-crypto-dh (2)
  • parallel/test-crypto-dh-leak (2)
  • parallel/test-domain-no-error-handler-abort-on-uncaught-2 (2)
  • parallel/test-domain-no-error-handler-abort-on-uncaught-3 (2)
  • parallel/test-domain-no-error-handler-abort-on-uncaught-4 (2)
  • parallel/test-domain-no-error-handler-abort-on-uncaught-5 (2)
  • parallel/test-stdout-to-file (2)
  • parallel/test-stream-map (2)
  • parallel/test-trace-events-fs-sync (2)
  • parallel/test-windows-failed-heap-allocation (2)
  • report/test-report-fatal-error (2)
  • sequential/test-debugger-heap-profiler (2)
  • sequential/test-debugger-restart-message (2)
  • sequential/test-debugger-run-after-quit-restart (2)
Dominant language
Shell
Stars
57
Forks
20
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from nodejs/reliability

All issues in nodejs/reliability

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.