Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CI Reliability 2023-04-28 #549

Open
29 tasks
github-actions bot opened this issue Apr 28, 2023 · 0 comments
Open
29 tasks

CI Reliability 2023-04-28 #549

github-actions bot opened this issue Apr 28, 2023 · 0 comments

Comments

@github-actions
Copy link

Failures in node-test-pull-request/51420 to node-test-pull-request/51517 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
2023-04-28 00:14 1 4 30 4 61 4.21%

CCTest Failure

Reason ../test/cctest/test_inspector_socket.cc:323: Failure
Type CC_TEST_FAILURE
Failed PR 6 (nodejs/node#47723, nodejs/node#47589, nodejs/node#47728, nodejs/node#47736, nodejs/node#47498, nodejs/node#47737)
Appeared test-rackspace-centos7-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/51480/
Last CI https://ci.nodejs.org/job/node-test-pull-request/51492/
Example
../test/cctest/test_inspector_socket.cc:323: Failure
Value of: (!expectation.read_expected)
  Actual: true
Expected: false
[  FAILED  ] InspectorSocketTest.HostIPv6NonRoutable (5000 ms)

Jenkins Failure

Git Failure

Build Failure

Reason Failed to trigger sub builds
Type BUILD_FAILURE
Failed PR 3 (nodejs/node#47613, nodejs/node#47437, nodejs/node#47160)
Appeared undefined
First CI https://ci.nodejs.org/job/node-test-pull-request/51432/
Last CI https://ci.nodejs.org/job/node-test-pull-request/51473/
Example
Failed to trigger sub builds

undefined

Reason Unknown
Type undefined
Failed PR 2 (nodejs/node#47675, nodejs/node#47641)
Appeared test-equinix-debian10_container-armv7l-2
First CI https://ci.nodejs.org/job/node-test-pull-request/51437/
Last CI https://ci.nodejs.org/job/node-test-pull-request/51481/
Example
Unknown

JSTest Failure

Reason parallel/test-single-executable-application
Type JS_TEST_FAILURE
Failed PR 14 (nodejs/node#47652, nodejs/node#47570, nodejs/node#47567, nodejs/node#47712, nodejs/node#47728, nodejs/node#47736, nodejs/node#47498, nodejs/node#47734, nodejs/node#47737, nodejs/node#47733, nodejs/node#47437, nodejs/node#47588, nodejs/node#47740, nodejs/node#47723)
Appeared test-orka-macos11-x64-1, test-orka-macos11-x64-2, test-nearform-macos10.15-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/51420/
Last CI https://ci.nodejs.org/job/node-test-pull-request/51517/
Example
not ok 2820 parallel/test-single-executable-application
  ---
  duration_ms: 120065.70400
  severity: fail
  exitcode: -15
  stack: |-
    timeout
    Wrote single executable preparation blob to sea-prep.blob
  ...


Reason parallel/test-net-write-fully-async-hex-string
Type JS_TEST_FAILURE
Failed PR 13 (nodejs/node#47679, nodejs/node#47678, nodejs/node#47570, nodejs/node#47675, nodejs/node#47635, nodejs/node#47723, nodejs/node#47589, nodejs/node#47728, nodejs/node#47736, nodejs/node#47498, nodejs/node#47734, nodejs/node#47437, nodejs/node#47588)
Appeared test-ibm-rhel8-s390x-1, test-softlayer-ubi81_container-x64-1, test-digitalocean-ubuntu1804_sharedlibs_container-x64-9, test-digitalocean-ubi81_container-x64-2, test-digitalocean-ubuntu1804_sharedlibs_container-x64-6, test-softlayer-alpine311_container-x64-1, test-digitalocean-ubuntu1804_sharedlibs_container-x64-8, test-softlayer-ubuntu1804_sharedlibs_container-x64-2, test-digitalocean-ubuntu1804_sharedlibs_container-x64-3, test-softlayer-ubuntu1804_sharedlibs_container-x64-4, test-ibm-rhel8-s390x-4
First CI https://ci.nodejs.org/job/node-test-pull-request/51428/
Last CI https://ci.nodejs.org/job/node-test-pull-request/51514/
Example
not ok 2855 parallel/test-net-write-fully-async-hex-string
  ---
  duration_ms: 120090.59800
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...


Reason pummel/test-fs-readfile-tostring-fail
Type JS_TEST_FAILURE
Failed PR 13 (nodejs/node#47652, nodejs/node#47570, nodejs/node#47712, nodejs/node#47635, nodejs/node#47728, nodejs/node#47498, nodejs/node#47737, nodejs/node#47691, nodejs/node#47604, nodejs/node#47734, nodejs/node#47437, nodejs/node#47588, nodejs/node#47723)
Appeared test-nearform-macos10.15-x64-1, test-ibm-ubuntu1804-x64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/51420/
Last CI https://ci.nodejs.org/job/node-test-pull-request/51517/
Example
not ok 3578 pummel/test-fs-readfile-tostring-fail
  ---
  duration_ms: 108.39800
  severity: fail
  exitcode: 7
  stack: |-
    /Users/iojs/build/workspace/node-test-commit-osx/nodes/osx1015/test/pummel/test-fs-readfile-tostring-fail.js:73
      throw err;
      ^
    
    AssertionError [ERR_ASSERTION]: ifError got unwanted exception: ENOSPC: no space left on device, write
        at Object.callback (/Users/iojs/build/workspace/node-test-commit-osx/nodes/osx1015/test/pummel/test-fs-readfile-tostring-fail.js:31:37)
        at callback (node:internal/streams/writable:562:21)
        at onwriteError (node:internal/streams/writable:425:3)
        at onwrite (node:internal/streams/writable:467:7)
        at node:internal/fs/streams:439:14
        at FSReqCallback.wrapper [as oncomplete] (node:fs:958:5) {
      generatedMessage: false,
      code: 'ERR_ASSERTION',
      actual: [Error: ENOSPC: no space left on device, write] {
        errno: -28,
        code: 'ENOSPC',
        syscall: 'write'
      },
      expe...

Reason parallel/test-fs-promises-file-handle-readFile
Type JS_TEST_FAILURE
Failed PR 7 (nodejs/node#47652, nodejs/node#47570, nodejs/node#47712, nodejs/node#47728, nodejs/node#47691, nodejs/node#47604, nodejs/node#47734)
Appeared test-nearform-macos10.15-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/51420/
Last CI https://ci.nodejs.org/job/node-test-pull-request/51506/
Example
not ok 799 parallel/test-fs-promises-file-handle-readFile
  ---
  duration_ms: 118.09900
  severity: fail
  exitcode: 1
  stack: |-
    node:internal/process/promises:289
                triggerUncaughtException(err, true /* fromPromise */);
                ^
    
    [Error: ENOSPC: no space left on device, ftruncate] {
      errno: -28,
      code: 'ENOSPC',
      syscall: 'ftruncate'
    }
    
    Node.js v21.0.0-pre
  ...


Reason parallel/test-fs-readfile
Type JS_TEST_FAILURE
Failed PR 7 (nodejs/node#47652, nodejs/node#47570, nodejs/node#47712, nodejs/node#47728, nodejs/node#47691, nodejs/node#47604, nodejs/node#47734)
Appeared test-nearform-macos10.15-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/51420/
Last CI https://ci.nodejs.org/job/node-test-pull-request/51505/
Example
not ok 848 parallel/test-fs-readfile
  ---
  duration_ms: 125.27300
  severity: fail
  exitcode: 1
  stack: |-
    node:internal/fs/utils:351
        throw err;
        ^
    
    Error: ENOSPC: no space left on device, ftruncate
        at Object.ftruncateSync (node:fs:1143:3)
        at Object.truncateSync (node:fs:1102:14)
        at Object.<anonymous> (/Users/iojs/build/workspace/node-test-commit-osx/nodes/osx1015/test/parallel/test-fs-readfile.js:61:6)
        at Module._compile (node:internal/modules/cjs/loader:1267:14)
        at Module._extensions..js (node:internal/modules/cjs/loader:1321:10)
        at Module.load (node:internal/modules/cjs/loader:1125:32)
        at Module._load (node:internal/modules/cjs/loader:965:12)
        at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:83:12)
        at node:internal/main/run_main_module:23:47 {
      errno: -28,
      syscall: 'ftruncate',
      code: 'ENOSPC'
    }
    
    Node.js v21.0.0-pre
  ...


Reason parallel/test-net-write-fully-async-buffer
Type JS_TEST_FAILURE
Failed PR 7 (nodejs/node#47651, nodejs/node#47679, nodejs/node#47570, nodejs/node#47675, nodejs/node#47712, nodejs/node#47691, nodejs/node#47733)
Appeared test-softlayer-ubi81_container-x64-1, test-softlayer-ubuntu1804_sharedlibs_container-x64-2, test-softlayer-alpine312_container-x64-1, test-ibm-rhel8-s390x-4, test-softlayer-ubuntu1804_sharedlibs_container-x64-5, test-softlayer-alpine311_container-x64-1, test-ibm-rhel8-x64-1, test-digitalocean-alpine311_container-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/51421/
Last CI https://ci.nodejs.org/job/node-test-pull-request/51491/
Example
not ok 2628 parallel/test-net-write-fully-async-buffer
  ---
  duration_ms: 120102.42200
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...


Reason es-module/test-esm-loader-http-imports
Type JS_TEST_FAILURE
Failed PR 4 (nodejs/node#47498, nodejs/node#47723, nodejs/node#47731, nodejs/node#47721)
Appeared test-digitalocean-freebsd12-x64-2, test-equinix-ubuntu2004_sharedlibs_container-arm64-5
First CI https://ci.nodejs.org/job/node-test-pull-request/51455/
Last CI https://ci.nodejs.org/job/node-test-pull-request/51497/
Example
not ok 3544 es-module/test-esm-loader-http-imports
  ---
  duration_ms: 33537.16800
  severity: fail
  exitcode: 1
  stack: |-
    TAP version 13
    # Subtest: ESM: http import via loader
        # Subtest: should load using --import flag
        ok 1 - should load using --import flag
          ---
          duration_ms: 6644.326905
          ...


Reason parallel/test-http-remove-connection-header-persists-connection
Type JS_TEST_FAILURE
Failed PR 4 (nodejs/node#47635, nodejs/node#47567, nodejs/node#47723, nodejs/node#47728)
Appeared test-digitalocean-alpine312_container-x64-2, test-orka-macos11-x64-1, test-equinix-ubuntu2004_sharedlibs_container-arm64-5
First CI https://ci.nodejs.org/job/node-test-pull-request/51458/
Last CI https://ci.nodejs.org/job/node-test-pull-request/51483/
Example
not ok 1414 parallel/test-http-remove-connection-header-persists-connection
  ---
  duration_ms: 171.17500
  severity: fail
  exitcode: 1
  stack: |-
    node:assert:125
      throw new AssertionError(obj);
      ^
    
    AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:
    
    false !== true
    
        at /home/iojs/build/workspace/node-test-commit-linux/test/parallel/test-http-remove-connection-header-persists-connection.js:67:16
        at Timeout._onTimeout (/home/iojs/build/workspace/node-test-commit-linux/test/parallel/test-http-remove-connection-header-persists-connection.js:54:7)
        at listOnTimeout (node:internal/timers:573:17)
        at process.processTimers (node:internal/timers:514:7) {
      generatedMessage: true,
      code: 'ERR_ASSERTION',
      actual: false,
      expected: true,
      operator: 'strictEqual'
    }
    
    Node.js v21.0.0-pre
  ...


Reason parallel/test-worker-nearheaplimit-deadlock
Type JS_TEST_FAILURE
Failed PR 4 (nodejs/node#47679, nodejs/node#47589, nodejs/node#47736, nodejs/node#47498)
Appeared test-digitalocean-rhel8-x64-1, test-ibm-rhel8-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/51429/
Last CI https://ci.nodejs.org/job/node-test-pull-request/51489/
Example
not ok 3570 parallel/test-worker-nearheaplimit-deadlock
  ---
  duration_ms: 120083.94600
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...


Reason sequential/test-http2-large-file
Type JS_TEST_FAILURE
Failed PR 4 (nodejs/node#47648, nodejs/node#47712, nodejs/node#47589, nodejs/node#47498)
Appeared test-softlayer-alpine312_container-x64-1, test-osuosl-aix72-ppc64_be-3, test-ibm-rhel8-s390x-4
First CI https://ci.nodejs.org/job/node-test-pull-request/51430/
Last CI https://ci.nodejs.org/job/node-test-pull-request/51489/
Example
not ok 3904 sequential/test-http2-large-file
  ---
  duration_ms: 120059.34800
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...


Reason parallel/test-child-process-fork-exec-path
Type JS_TEST_FAILURE
Failed PR 3 (nodejs/node#47652, nodejs/node#47570, nodejs/node#47712)
Appeared test-nearform-macos10.15-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/51420/
Last CI https://ci.nodejs.org/job/node-test-pull-request/51459/
Example
not ok 188 parallel/test-child-process-fork-exec-path
  ---
  duration_ms: 3692.52600
  severity: fail
  exitcode: 1
  stack: |-
    node:internal/fs/utils:351
        throw err;
        ^
    
    Error: ENOSPC: no space left on device, copyfile '/Users/iojs/build/workspace/node-test-commit-osx/nodes/osx1015/out/Release/node' -> '/Users/iojs/node-tmp/.tmp.181/node-copy.exe'
        at Object.copyFileSync (node:fs:2951:3)
        at Object.<anonymous> (/Users/iojs/build/workspace/node-test-commit-osx/nodes/osx1015/test/parallel/test-child-process-fork-exec-path.js:51:4)
        at Module._compile (node:internal/modules/cjs/loader:1267:14)
        at Module._extensions..js (node:internal/modules/cjs/loader:1321:10)
        at Module.load (node:internal/modules/cjs/loader:1125:32)
        at Module._load (node:internal/modules/cjs/loader:965:12)
        at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:83:12)
        at node:internal/main/run_main_module:23:47 {
      errno: -28,
  ...

Reason parallel/test-file-write-stream4
Type JS_TEST_FAILURE
Failed PR 3 (nodejs/node#47652, nodejs/node#47570, nodejs/node#47712)
Appeared test-nearform-macos10.15-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/51420/
Last CI https://ci.nodejs.org/job/node-test-pull-request/51459/
Example
not ok 740 parallel/test-file-write-stream4
  ---
  duration_ms: 892.65300
  severity: fail
  exitcode: 1
  stack: |-
    node:events:489
          throw er; // Unhandled 'error' event
          ^
    
    Error: ENOSPC: no space left on device, write
    Emitted 'error' event on WriteStream instance at:
        at WriteStream.onerror (node:internal/streams/readable:793:14)
        at WriteStream.emit (node:events:511:28)
        at emitErrorNT (node:internal/streams/destroy:151:8)
        at emitErrorCloseNT (node:internal/streams/destroy:116:3)
        at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
      errno: -28,
      code: 'ENOSPC',
      syscall: 'write'
    }
    
    Node.js v21.0.0-pre
  ...


Reason parallel/test-macos-app-sandbox
Type JS_TEST_FAILURE
Failed PR 3 (nodejs/node#47652, nodejs/node#47570, nodejs/node#47712)
Appeared test-nearform-macos10.15-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/51420/
Last CI https://ci.nodejs.org/job/node-test-pull-request/51459/
Example
not ok 1758 parallel/test-macos-app-sandbox
  ---
  duration_ms: 3250.12600
  severity: fail
  exitcode: 1
  stack: |-
    node:internal/fs/utils:351
        throw err;
        ^
    
    Error: ENOSPC: no space left on device, copyfile '/Users/iojs/build/workspace/node-test-commit-osx/nodes/osx1015/out/Release/node' -> '/Users/iojs/node-tmp/.tmp.1752/node_sandboxed.app/Contents/MacOS/node'
        at Object.copyFileSync (node:fs:2951:3)
        at Object.<anonymous> (/Users/iojs/build/workspace/node-test-commit-osx/nodes/osx1015/test/parallel/test-macos-app-sandbox.js:37:4)
        at Module._compile (node:internal/modules/cjs/loader:1267:14)
        at Module._extensions..js (node:internal/modules/cjs/loader:1321:10)
        at Module.load (node:internal/modules/cjs/loader:1125:32)
        at Module._load (node:internal/modules/cjs/loader:965:12)
        at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:83:12)
        at node:internal/main/run_main_module:23:47 {
      errno: -2...

Reason parallel/test-module-loading-globalpaths
Type JS_TEST_FAILURE
Failed PR 3 (nodejs/node#47652, nodejs/node#47570, nodejs/node#47712)
Appeared test-nearform-macos10.15-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/51420/
Last CI https://ci.nodejs.org/job/node-test-pull-request/51459/
Example
not ok 1782 parallel/test-module-loading-globalpaths
  ---
  duration_ms: 3448.11000
  severity: fail
  exitcode: 1
  stack: |-
    node:internal/fs/utils:351
        throw err;
        ^
    
    Error: ENOSPC: no space left on device, copyfile '/Users/iojs/build/workspace/node-test-commit-osx/nodes/osx1015/out/Release/node' -> '/Users/iojs/node-tmp/.tmp.1776/install/bin/node'
        at Object.copyFileSync (node:fs:2951:3)
        at Object.<anonymous> (/Users/iojs/build/workspace/node-test-commit-osx/nodes/osx1015/test/parallel/test-module-loading-globalpaths.js:32:6)
        at Module._compile (node:internal/modules/cjs/loader:1267:14)
        at Module._extensions..js (node:internal/modules/cjs/loader:1321:10)
        at Module.load (node:internal/modules/cjs/loader:1125:32)
        at Module._load (node:internal/modules/cjs/loader:965:12)
        at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:83:12)
        at node:internal/main/run_main_module:23:47 {
      errno: -28,
 ...

Reason parallel/test-runner-watch-mode
Type JS_TEST_FAILURE
Failed PR 3 (nodejs/node#47675, nodejs/node#47706, nodejs/node#47498)
Appeared test-digitalocean-ubuntu1804_sharedlibs_container-x64-3, test-osuosl-ubuntu2004_container-armv7l-1, test-orka-macos11-x64-2, test-digitalocean-alpine312_container-x64-2, test-osuosl-rhel8-ppc64_le-2, test-equinix-ubuntu1804_sharedlibs_container-arm64-1, test-nearform-macos11.0-arm64-1, test-ibm-rhel8-s390x-4, test-softlayer-ubuntu1804_sharedlibs_container-x64-3, test-digitalocean-ubuntu1804_sharedlibs_container-x64-6, test-digitalocean-ubuntu1804_sharedlibs_container-x64-4, test-softlayer-ubuntu1804_sharedlibs_container-x64-4, test-azure_msft-win10_vs2019-x64-4
First CI https://ci.nodejs.org/job/node-test-pull-request/51437/
Last CI https://ci.nodejs.org/job/node-test-pull-request/51489/
Example
not ok 2593 parallel/test-runner-watch-mode
  ---
  duration_ms: 120119.36900
  severity: fail
  exitcode: -15
  stack: |-
    timeout
    TAP version 13
  ...


Reason pummel/test-crypto-timing-safe-equal-benchmarks
Type JS_TEST_FAILURE
Failed PR 3 (nodejs/node#47687, nodejs/node#47588, nodejs/node#47723)
Appeared test-ibm-aix72-ppc64_be-2
First CI https://ci.nodejs.org/job/node-test-pull-request/51434/
Last CI https://ci.nodejs.org/job/node-test-pull-request/51517/
Example
not ok 3573 pummel/test-crypto-timing-safe-equal-benchmarks
  ---
  duration_ms: 3484.05800
  severity: fail
  exitcode: 1
  stack: |-
    node:assert:399
        throw err;
        ^
    
    AssertionError [ERR_ASSERTION]: timingSafeEqual should not leak information from its execution time (t=-4.344695520447655)
        at Object.<anonymous> (/home/iojs/build/workspace/node-test-commit-aix/nodes/aix72-ppc64/test/pummel/test-crypto-timing-safe-equal-benchmarks.js:109:1)
        at Module._compile (node:internal/modules/cjs/loader:1267:14)
        at Module._extensions..js (node:internal/modules/cjs/loader:1321:10)
        at Module.load (node:internal/modules/cjs/loader:1125:32)
        at Module._load (node:internal/modules/cjs/loader:965:12)
        at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:83:12)
        at node:internal/main/run_main_module:23:47 {
      generatedMessage: false,
      code: 'ERR_ASSERTION',
      actual: false,
      expected: true,
      operator: '=...

Reason pummel/test-net-throttle
Type JS_TEST_FAILURE
Failed PR 3 (nodejs/node#47712, nodejs/node#47721, nodejs/node#47735)
Appeared test-digitalocean-freebsd12-x64-2, test-digitalocean-freebsd12-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/51468/
Last CI https://ci.nodejs.org/job/node-test-pull-request/51510/
Example
not ok 3606 pummel/test-net-throttle
  ---
  duration_ms: 596.19700
  severity: fail
  exitcode: 1
  stack: |-
    node:assert:125
      throw new AssertionError(obj);
      ^
    
    AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:
    
    false !== true
    
        at process.<anonymous> (/usr/home/iojs/build/workspace/node-test-commit-freebsd/nodes/freebsd12-x64/test/pummel/test-net-throttle.js:87:10)
        at process.emit (node:events:523:35) {
      generatedMessage: true,
      code: 'ERR_ASSERTION',
      actual: false,
      expected: true,
      operator: 'strictEqual'
    }
    
    Node.js v21.0.0-pre
  ...


Reason sequential/test-worker-prof
Type JS_TEST_FAILURE
Failed PR 3 (nodejs/node#47675, nodejs/node#47678, nodejs/node#47731)
Appeared test-equinix-ubuntu2004_sharedlibs_container-arm64-5, test-rackspace-win2012r2_vs2019-x64-1, test-rackspace-win2012r2_vs2019-x64-3
First CI https://ci.nodejs.org/job/node-test-pull-request/51437/
Last CI https://ci.nodejs.org/job/node-test-pull-request/51485/
Example
not ok 3954 sequential/test-worker-prof
  ---
  duration_ms: 1414.36600
  severity: fail
  exitcode: 1
  stack: |-
    node:assert:125
      throw new AssertionError(obj);
      ^
    
    AssertionError [ERR_ASSERTION]: child exited with an error:                      {
      status: null,
      signal: 'SIGABRT',
      output: [
        null,
        '',
        "/home/iojs/build/workspace/node-test-commit-arm-debug/out/Debug/node[1080666]: ../src/env-inl.h:846:void node::Environment::set_filehandlereadwrap_template(v8::Local<v8::ObjectTemplate>): Assertion `isolate_data()->filehandlereadwrap_template().IsEmpty()' failed.\n" +
          ' 1: 0xaaaae6a08a70 node::DumpBacktrace(_IO_FILE*) [/home/iojs/build/workspace/node-test-commit-arm-debug/out/Debug/node]\n' +
          ' 2: 0xaaaae6b14590 node::Abort() [/home/iojs/build/workspace/node-test-commit-arm-debug/out/Debug/node]\n' +
          ' 3: 0xaaaae6b14664  [/home/iojs/build/workspace/node-test-commit-arm-debug/out/Debug/node]\n' +
          ' 4: 0xaaaae6...

Reason parallel/test-http2-misbehaving-multiplex
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#47728, nodejs/node#47588)
Appeared test-orka-macos11-x64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/51483/
Last CI https://ci.nodejs.org/job/node-test-pull-request/51509/
Example
not ok 1479 parallel/test-http2-misbehaving-multiplex
  ---
  duration_ms: 346.92000
  severity: fail
  exitcode: 1
  stack: |-
    node:assert:125
      throw new AssertionError(obj);
      ^
    
    AssertionError [ERR_ASSERTION]: Expected "actual" to be strictly unequal to: 5
        at Http2Server.<anonymous> (/Users/iojs/build/workspace/node-test-commit-osx/nodes/osx11-x64/test/parallel/test-http2-misbehaving-multiplex.js:45:10)
        at Http2Server.<anonymous> (/Users/iojs/build/workspace/node-test-commit-osx/nodes/osx11-x64/test/common/index.js:465:15)
        at Http2Server.emit (node:events:511:28)
        at ServerHttp2Session.sessionOnStream (node:internal/http2/core:3003:19)
        at ServerHttp2Session.emit (node:events:511:28)
        at emit (node:internal/http2/core:331:3)
        at process.processTicksAndRejections (node:internal/process/task_queues:85:22) {
      generatedMessage: true,
      code: 'ERR_ASSERTION',
      actual: 5,
      expected: 5,
      operator: 'notStrictEqual'
   ...

Reason parallel/test-inspector-exception
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#47648, nodejs/node#47570)
Appeared test-ibm-rhel8-s390x-4
First CI https://ci.nodejs.org/job/node-test-pull-request/51430/
Last CI https://ci.nodejs.org/job/node-test-pull-request/51436/
Example
not ok 2096 parallel/test-inspector-exception
  ---
  duration_ms: 15304.18400
  severity: fail
  exitcode: 1
  stack: |-
    [test] Connecting to a child Node process
    [test] Testing /json/list
    [err] Debugger listening on ws://127.0.0.1:42899/e95320fe-242e-4a2a-95b0-1211d0d8a0fe
    [err] For help, see: https://nodejs.org/en/docs/inspector
    [err] 
    [test] Verifying debugger stops on start (--inspect-brk option)
    [err] Debugger attached.
    [err] 
    Timed out waiting for matching notification (break on file:///home/iojs/build/workspace/node-test-commit-linuxone/test/fixtures/throws_error.js:21)
    1
  ...


Reason parallel/test-tls-ticket-cluster
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#47728, nodejs/node#47498)
Appeared test-azure_msft-win10_vs2019-x64-4, test-rackspace-win2012r2_vs2017-x64-4
First CI https://ci.nodejs.org/job/node-test-pull-request/51483/
Last CI https://ci.nodejs.org/job/node-test-pull-request/51489/
Example
not ok 754 parallel/test-tls-ticket-cluster
  ---
  duration_ms: 650.04200
  severity: fail
  exitcode: 1
  stack: |-
    [primary] got "listening"
    [primary] connecting 56143 session? false
    [primary] got "listening"
    [primary] got "listening"
    [primary] connecting 56143 session? false
    [worker] connection reused? false
    [primary] got "not-reused"
    [primary] connecting 56143 session? true
    [worker] connection reused? true
    [primary] got "reused"
    [primary] connecting 56143 session? true
    [worker] connection reused? true
    [primary] got "reused"
    [primary] connecting 56143 session? true
    [worker] connection reused? true
    [primary] got "reused"
    [primary] connecting 56143 session? true
    [worker] connection reused? true
    [primary] got "reused"
    [primary] connecting 56143 session? true
    [worker] connection reused? true
    [primary] got "reused"
    [primary] connecting 56143 session? true
    [worker] connection reused? true
    [primary] got "reused"
 ...

Reason pummel/test-net-bytes-per-incoming-chunk-overhead
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#47567, nodejs/node#47691)
Appeared test-orka-macos11-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/51464/
Last CI https://ci.nodejs.org/job/node-test-pull-request/51496/
Example
not ok 3629 pummel/test-net-bytes-per-incoming-chunk-overhead
  ---
  duration_ms: 36582.18800
  severity: crashed
  exitcode: -6
  stack: |-
    Assertion failed: (timeout != -1), function uv__io_poll, file kqueue.c, line 257.
  ...


Reason wpt/test-encoding
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#47731, nodejs/node#47734)
Appeared test-azure_msft-win10_vs2019-x64-2, test-equinix-ubuntu2004_sharedlibs_container-arm64-5
First CI https://ci.nodejs.org/job/node-test-pull-request/51485/
Last CI https://ci.nodejs.org/job/node-test-pull-request/51505/
Example
not ok 891 wpt/test-encoding
  ---
  duration_ms: 1800.00700
  severity: crashed
  exitcode: 3221225477
  stack: |-
    [SKIPPED] idlharness.any.js: No implementation of TextDecoderStream and TextEncoderStream
    [SKIPPED] iso-2022-jp-decoder.any.js: iso-2022-jp decoder state handling bug: https://encoding.spec.whatwg.org/#iso-2022-jp-decoder
    [SKIPPED] legacy-mb-schinese\gb18030\gb18030-decoder.any.js: The gb18030 encoding is not supported
    [SKIPPED] legacy-mb-schinese\gbk\gbk-decoder.any.js: The gbk encoding is not supported
    [SKIPPED] replacement-encodings.any.js: decoding-helpers.js needs XMLHttpRequest
    [SKIPPED] single-byte-decoder.window.js?XMLHttpRequest: document is not defined
    [SKIPPED] single-byte-decoder.window.js?TextDecoder: document is not defined
    [SKIPPED] single-byte-decoder.window.js?document: document is not defined
    [SKIPPED] streams\invalid-realm.window.js: document is not defined
    [SKIPPED] streams\realms.window.js: window is not defined
    [SKIPPED] textdecod...

Reason wpt/test-timers
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#47731, nodejs/node#47736)
Appeared test-softlayer-alpine311_container-x64-1, test-equinix-ubuntu2004_sharedlibs_container-arm64-5
First CI https://ci.nodejs.org/job/node-test-pull-request/51485/
Last CI https://ci.nodejs.org/job/node-test-pull-request/51488/
Example
not ok 100 wpt/test-timers
  ---
  duration_ms: 4523.32900
  severity: fail
  exitcode: 1
  stack: |-
    [SKIPPED] negative-settimeout.any.js: unreliable in Node.js; Refs: https://github.com/nodejs/node/issues/37672
    [PASS] Calling setInterval with no interval should be the same as if called with 0 interval
    [PASS] Calling setInterval with undefined interval should be the same as if called with 0 interval
    [PASS] type-long-setinterval
    [UNEXPECTED_FAILURE][UNCAUGHT] evaluation in WPTRunner.runJsTests()
    assert_unreached: Reached unreachable code
    {
      message: 'assert_unreached: Reached unreachable code',
      stack: '    at listOnTimeout (node:internal/timers:573:17)\n' +
        '    at process.processTimers (node:internal/timers:514:7)'
    }
    Command: /home/iojs/build/workspace/node-test-commit-linux/out/Release/node  /home/iojs/build/workspace/node-test-commit-linux/test/wpt/test-timers.js 'type-long-setinterval.any.js'
    
    [PASS] negative-setinterval
    [PASS] type-long-s...

Reason wpt/test-wasm-webapi
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#47731, nodejs/node#47498)
Appeared test-digitalocean-ubuntu1804_sharedlibs_container-x64-3, test-equinix-ubuntu2004_sharedlibs_container-arm64-5
First CI https://ci.nodejs.org/job/node-test-pull-request/51485/
Last CI https://ci.nodejs.org/job/node-test-pull-request/51489/
Example
not ok 2537 wpt/test-wasm-webapi
  ---
  duration_ms: 1440049.39000
  severity: fail
  exitcode: -15
  stack: |-
    timeout
    [SKIPPED] abort.any.js: WPTRunner does not support fetch()
    [SKIPPED] contenttype.any.js: WPTRunner does not support fetch()
    [SKIPPED] historical.any.js: indexedDB is not defined
    [SKIPPED] idlharness.any.js: not configured
    [SKIPPED] instantiateStreaming-bad-imports.any.js: Flaky on ARM with V8 >= 11.2
    [SKIPPED] origin.sub.any.js: CORS not implemented
    [SKIPPED] status.any.js: WPTRunner does not support fetch()
    [PASS] compileStreaming
    [PASS] instantiateStreaming
    [PASS] compileStreaming after consumption
    [PASS] compileStreaming before consumption
    [PASS] instantiateStreaming after consumption
    [PASS] instantiateStreaming before consumption
    [PASS] compileStreaming: undefined
    [PASS] compileStreaming: undefined in a promise
    [PASS] compileStreaming: no body
    [PASS] Empty module without imports argument
    [PASS] compileStreaming:...

Reason wpt/test-webcrypto
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#47731, nodejs/node#47737)
Appeared test-equinix_mnx-smartos20-x64-3, test-equinix-ubuntu2004_sharedlibs_container-arm64-5
First CI https://ci.nodejs.org/job/node-test-pull-request/51485/
Last CI https://ci.nodejs.org/job/node-test-pull-request/51492/
Example
not ok 330 wpt/test-webcrypto
  ---
  duration_ms: 18025.72700
  severity: fail
  exitcode: 1
  stack: |-
    [SKIPPED] algorithm-discards-context.https.window.js: Not relevant in Node.js context
    [SKIPPED] historical.any.js: Not relevant in Node.js context
    [PASS] setup - define tests
    [PASS] P-521 good parameters
    [PASS] P-521 mixed case parameters
    [PASS] P-521 with null length
    [PASS] P-521 short result
    [PASS] P-521 non-multiple of 8 bits
    [PASS] P-521 missing public curve
    [PASS] P-521 public property of algorithm is not a CryptoKey
    [PASS] P-521 mismatched curves
    [PASS] P-521 public property of algorithm is not an ECDSA public key
    [PASS] P-521 no deriveBits usage for base key
    [PASS] P-521 base key is not a private key
    [PASS] P-521 public property value is a private key
    [PASS] P-521 public property value is a secret key
    [PASS] P-521 asking for too many bits
    [PASS] P-256 good parameters
    [PASS] P-256 mixed case parameters
    [PASS] P-256 with ...

Progress

  • ../test/cctest/test_inspector_socket.cc:323: Failure (6)
  • Failed to trigger sub builds (3)
  • Unknown (2)
  • parallel/test-single-executable-application (14)
  • parallel/test-net-write-fully-async-hex-string (13)
  • pummel/test-fs-readfile-tostring-fail (13)
  • parallel/test-fs-promises-file-handle-readFile (7)
  • parallel/test-fs-readfile (7)
  • parallel/test-net-write-fully-async-buffer (7)
  • es-module/test-esm-loader-http-imports (4)
  • parallel/test-http-remove-connection-header-persists-connection (4)
  • parallel/test-worker-nearheaplimit-deadlock (4)
  • sequential/test-http2-large-file (4)
  • parallel/test-child-process-fork-exec-path (3)
  • parallel/test-file-write-stream4 (3)
  • parallel/test-macos-app-sandbox (3)
  • parallel/test-module-loading-globalpaths (3)
  • parallel/test-runner-watch-mode (3)
  • pummel/test-crypto-timing-safe-equal-benchmarks (3)
  • pummel/test-net-throttle (3)
  • sequential/test-worker-prof (3)
  • parallel/test-http2-misbehaving-multiplex (2)
  • parallel/test-inspector-exception (2)
  • parallel/test-tls-ticket-cluster (2)
  • pummel/test-net-bytes-per-incoming-chunk-overhead (2)
  • wpt/test-encoding (2)
  • wpt/test-timers (2)
  • wpt/test-wasm-webapi (2)
  • wpt/test-webcrypto (2)
tniessen added a commit to tniessen/node that referenced this issue Apr 28, 2023
In general, we assume that the tmpdir will provide sufficient space for
most tests. Some tests, however, require hundreds of megabytes or even
gigabytes of space, which often causes them to fail, especially on our
macOS infrastructure. The most recent reliability report contains more
than 20 related CI failures.

This change adds a new function hasTooLittleSpace() to the tmpdir module
that uses statfsSync() to guess whether allocating a certain amount of
space within the temporary directory will fail.

This change also updates the most frequently failing tests to use the
new function, in which case the relevant parts of the tests are skipped.

Refs: nodejs/reliability#549
tniessen added a commit to tniessen/node that referenced this issue Apr 29, 2023
In general, we assume that the tmpdir will provide sufficient space for
most tests. Some tests, however, require hundreds of megabytes or even
gigabytes of space, which often causes them to fail, especially on our
macOS infrastructure. The most recent reliability report contains more
than 20 related CI failures.

This change adds a new function hasTooLittleSpace() to the tmpdir module
that uses statfsSync() to guess whether allocating a certain amount of
space within the temporary directory will fail.

This change also updates the most frequently failing tests to use the
new function, in which case the relevant parts of the tests are skipped.

Refs: nodejs/reliability#549
tniessen added a commit to tniessen/node that referenced this issue Apr 30, 2023
In general, we assume that the tmpdir will provide sufficient space for
most tests. Some tests, however, require hundreds of megabytes or even
gigabytes of space, which often causes them to fail, especially on our
macOS infrastructure. The most recent reliability report contains more
than 20 related CI failures.

This change adds a new function hasEnoughSpace() to the tmpdir module
that uses statfsSync() to guess whether allocating a certain amount of
space within the temporary directory will succeed.

This change also updates the most frequently failing tests to use the
new function such that the relevant parts of the tests are skipped if
tmpdir has insufficient space.

Refs: nodejs/reliability#549
nodejs-github-bot pushed a commit to nodejs/node that referenced this issue May 1, 2023
In general, we assume that the tmpdir will provide sufficient space for
most tests. Some tests, however, require hundreds of megabytes or even
gigabytes of space, which often causes them to fail, especially on our
macOS infrastructure. The most recent reliability report contains more
than 20 related CI failures.

This change adds a new function hasEnoughSpace() to the tmpdir module
that uses statfsSync() to guess whether allocating a certain amount of
space within the temporary directory will succeed.

This change also updates the most frequently failing tests to use the
new function such that the relevant parts of the tests are skipped if
tmpdir has insufficient space.

Refs: nodejs/reliability#549
PR-URL: #47767
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com>
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
Reviewed-By: Richard Lau <rlau@redhat.com>
targos pushed a commit to nodejs/node that referenced this issue May 2, 2023
In general, we assume that the tmpdir will provide sufficient space for
most tests. Some tests, however, require hundreds of megabytes or even
gigabytes of space, which often causes them to fail, especially on our
macOS infrastructure. The most recent reliability report contains more
than 20 related CI failures.

This change adds a new function hasEnoughSpace() to the tmpdir module
that uses statfsSync() to guess whether allocating a certain amount of
space within the temporary directory will succeed.

This change also updates the most frequently failing tests to use the
new function such that the relevant parts of the tests are skipped if
tmpdir has insufficient space.

Refs: nodejs/reliability#549
PR-URL: #47767
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com>
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
Reviewed-By: Richard Lau <rlau@redhat.com>
targos pushed a commit to nodejs/node that referenced this issue May 3, 2023
In general, we assume that the tmpdir will provide sufficient space for
most tests. Some tests, however, require hundreds of megabytes or even
gigabytes of space, which often causes them to fail, especially on our
macOS infrastructure. The most recent reliability report contains more
than 20 related CI failures.

This change adds a new function hasEnoughSpace() to the tmpdir module
that uses statfsSync() to guess whether allocating a certain amount of
space within the temporary directory will succeed.

This change also updates the most frequently failing tests to use the
new function such that the relevant parts of the tests are skipped if
tmpdir has insufficient space.

Refs: nodejs/reliability#549
PR-URL: #47767
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com>
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
Reviewed-By: Richard Lau <rlau@redhat.com>
danielleadams pushed a commit to nodejs/node that referenced this issue Jul 6, 2023
In general, we assume that the tmpdir will provide sufficient space for
most tests. Some tests, however, require hundreds of megabytes or even
gigabytes of space, which often causes them to fail, especially on our
macOS infrastructure. The most recent reliability report contains more
than 20 related CI failures.

This change adds a new function hasEnoughSpace() to the tmpdir module
that uses statfsSync() to guess whether allocating a certain amount of
space within the temporary directory will succeed.

This change also updates the most frequently failing tests to use the
new function such that the relevant parts of the tests are skipped if
tmpdir has insufficient space.

Refs: nodejs/reliability#549
PR-URL: #47767
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com>
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
Reviewed-By: Richard Lau <rlau@redhat.com>
MoLow pushed a commit to MoLow/node that referenced this issue Jul 6, 2023
In general, we assume that the tmpdir will provide sufficient space for
most tests. Some tests, however, require hundreds of megabytes or even
gigabytes of space, which often causes them to fail, especially on our
macOS infrastructure. The most recent reliability report contains more
than 20 related CI failures.

This change adds a new function hasEnoughSpace() to the tmpdir module
that uses statfsSync() to guess whether allocating a certain amount of
space within the temporary directory will succeed.

This change also updates the most frequently failing tests to use the
new function such that the relevant parts of the tests are skipped if
tmpdir has insufficient space.

Refs: nodejs/reliability#549
PR-URL: nodejs#47767
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com>
Reviewed-By: Moshe Atlow <moshe@atlow.co.il>
Reviewed-By: Richard Lau <rlau@redhat.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

0 participants