Skip to content

CI Reliability 2022-11-02 #418

New issue
New issue
Open
Open
CI Reliability 2022-11-02#418
@github-actions

Description

@github-actions
github-actions
bot
opened on Nov 2, 2022

Failures in node-test-pull-request/47528 to node-test-pull-request/47625 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-11-02 00:16 3 8 30 3 56 8.51%

JSTest Failure

Reason parallel/test-vm-timeout-escape-promise-module
Type JS_TEST_FAILURE
Failed PR 4 (nodejs/node#45231, nodejs/node#45243, nodejs/node#45156, nodejs/node#44989)
Appeared test-azure_msft-win2016_vs2017-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/47554/
Last CI https://ci.nodejs.org/job/node-test-pull-request/47594/
Example 
not ok 675 parallel/test-vm-timeout-escape-promise-module
  ---
  duration_ms: 0.792
  severity: fail
  exitcode: 1
  stack: |-
    (node:4220) ExperimentalWarning: VM Modules is an experimental feature. This feature could change at any time
    (Use `node --trace-warnings ...` to show where the warning was created)
    C:\workspace\node-test-binary-windows-js-suites\node\test\common\index.js:638
    const crashOnUnhandledRejection = (err) => { throw err; };
                                                 ^
    
    Error: escaped timeout at 100 milliseconds!
        at loop (C:\workspace\node-test-binary-windows-js-suites\node\test\parallel\test-vm-timeout-escape-promise-module.js:22:13)
        at vm:module(0):1:39
        at SourceTextModule.evaluate (internal/vm/module.js:230:23)
        at assert.rejects.code (C:\workspace\node-test-binary-windows-js-suites\node\test\parallel\test-vm-timeout-escape-promise-module.js:38:16)
        at processTicksAndRejections (internal/process/task_queues.js:95:5)
     ...
Reason sequential/test-worker-prof
Type JS_TEST_FAILURE
Failed PR 4 (nodejs/node#42384, nodejs/node#45243, nodejs/node#45156, nodejs/node#44436)
Appeared test-rackspace-win2012r2_vs2019-x64-4, test-rackspace-win2012r2_vs2019-x64-1, test-azure_msft-win10_vs2019-x64-3, test-azure_msft-win10_vs2019-x64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/47550/
Last CI https://ci.nodejs.org/job/node-test-pull-request/47610/
Example 
not ok 904 sequential/test-worker-prof
  ---
  duration_ms: 30.296
  severity: fail
  exitcode: 1
  stack: |-
    node:assert:124
      throw new AssertionError(obj);
      ^
    
    AssertionError [ERR_ASSERTION]: child exited with signal: {
      error: Error: spawnSync C:\workspace\node-test-binary-windows-js-suites\node\Release\node.exe ETIMEDOUT
          at Object.spawnSync (node:internal/child_process:1117:20)
          at spawnSync (node:child_process:871:24)
          at Object.<anonymous> (C:\workspace\node-test-binary-windows-js-suites\node\test\sequential\test-worker-prof.js:53:23)
          at Module._compile (node:internal/modules/cjs/loader:1205:14)
          at Module._extensions..js (node:internal/modules/cjs/loader:1259:10)
          at Module.load (node:internal/modules/cjs/loader:1068:32)
          at Module._load (node:internal/modules/cjs/loader:909:12)
          at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:82:12)
          at node:internal/main/run_mai...
Reason pummel/test-fs-largefile
Type JS_TEST_FAILURE
Failed PR 3 (nodejs/node#44226, nodejs/node#45269, nodejs/node#44412)
Appeared test-nearform-macos10.15-x64-2, test-rackspace-win2012r2_vs2019-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/47613/
Last CI https://ci.nodejs.org/job/node-test-pull-request/47625/
Example 
not ok 3420 pummel/test-fs-largefile
  ---
  duration_ms: 0.73
  severity: fail
  exitcode: 1
  stack: |-
    node:internal/fs/utils:347
        throw err;
        ^
    
    Error: ENOSPC: no space left on device, ftruncate
        at Object.ftruncateSync (node:fs:1130:3)
        at Object.<anonymous> (/Users/iojs/build/workspace/node-test-commit-osx/nodes/osx1015/test/pummel/test-fs-largefile.js:37:4)
        at Module._compile (node:internal/modules/cjs/loader:1205:14)
        at Module._extensions..js (node:internal/modules/cjs/loader:1259:10)
        at Module.load (node:internal/modules/cjs/loader:1068:32)
        at Module._load (node:internal/modules/cjs/loader:909:12)
        at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:82:12)
        at node:internal/main/run_main_module:23:47 {
      errno: -28,
      syscall: 'ftruncate',
      code: 'ENOSPC'
    }
    
    Node.js v20.0.0-pre
  ...
Reason node-api/test_fatal/test2
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#44458, nodejs/node#45156)
Appeared test-joyent-smartos20-x64-3
First CI https://ci.nodejs.org/job/node-test-pull-request/47601/
Last CI https://ci.nodejs.org/job/node-test-pull-request/47602/
Example 
not ok 3612 node-api/test_fatal/test2
  ---
  duration_ms: 300.172
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...
Reason parallel/test-corepack-yarn-install
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#45176, nodejs/node#44989)
Appeared test-digitalocean-ubuntu1804_sharedlibs_container-x64-4
First CI https://ci.nodejs.org/job/node-test-pull-request/47552/
Last CI https://ci.nodejs.org/job/node-test-pull-request/47595/
Example 
not ok 592 parallel/test-corepack-yarn-install
  ---
  duration_ms: 2.724
  severity: fail
  exitcode: 1
  stack: |-
    (node:12501) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
    (Use `node --trace-deprecation ...` to show where the warning was created)
    Segmentation fault (core dumped)
    assert.js:118
      throw new AssertionError(obj);
      ^
    
    AssertionError [ERR_ASSERTION]: yarn install got error code 139
        at handleExit (/home/iojs/build/workspace/node-test-commit-linux-containered/test/parallel/test-corepack-yarn-install.js:60:10)
        at handleExit (/home/iojs/build/workspace/node-test-commit-linux-containered/test/common/index.js:380:15)
        at ChildProcess.exithandler (child_process.js:390:5)
        at ChildProcess.emit (events.js:400:28)
        at maybeClose (internal/child_process.js:1088:16)
        at Socket.<anonymous> (internal/chi...
Reason parallel/test-heapsnapshot-near-heap-limit-by-api-in-worker
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#44989, nodejs/node#45255)
Appeared test-ibm-rhel8-s390x-4, test-equinix-ubuntu2004_container-arm64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/47595/
Last CI https://ci.nodejs.org/job/node-test-pull-request/47620/
Example 
not ok 989 parallel/test-heapsnapshot-near-heap-limit-by-api-in-worker
  ---
  duration_ms: 3.395
  severity: fail
  exitcode: 1
  stack: |-
    
    Invoked NearHeapLimitCallback, processing=false, current_limit=52428800, initial_limit=52428800
    max_young_gen_size=50331648, young_gen_size=0, old_gen_size=49537016, total_size=49537016
    Estimated available memory=9223372036727861248, estimated overhead=50331648
    Start generating Heap.20221101.132003.2475175.1.001.heapsnapshot...
    Invoked NearHeapLimitCallback, processing=true, current_limit=52428800, initial_limit=52428800
    max_young_gen_size=50331648, young_gen_size=0, old_gen_size=49537016, total_size=49537016
    Estimated available memory=9223372036727861248, estimated overhead=50331648
    Not generating snapshots in nested callback. new_limit=102760448
    1/1 snapshots taken.
    Removing the near heap limit callbackWrote snapshot to /home/iojs/node-tmp/.tmp.978/Heap.20221101.132003.2475175.1.001.heapsnapshot
    
    <--- Last few GCs --...
Reason parallel/test-inspector-esm
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#44432, nodejs/node#45156)
Appeared test-nearform-macos10.15-x64-1, test-ibm-rhel8-s390x-3
First CI https://ci.nodejs.org/job/node-test-pull-request/47542/
Last CI https://ci.nodejs.org/job/node-test-pull-request/47586/
Example 
not ok 1648 parallel/test-inspector-esm
  ---
  duration_ms: 15.354
  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:65168/9a0d04e0-827c-4441-9687-029bb7fc9337
    [err] For help, see: https://nodejs.org/en/docs/inspector
    [err] 
    [err] Debugger attached.
    [err] 
    [test] Verifying debugger stops on start (--inspect-brk option)
    Timed out waiting for matching notification (break on file:///Users/iojs/build/workspace/node-test-commit-osx/nodes/osx1015/test/fixtures/es-modules/message.mjs:0)
    1
  ...
Reason parallel/test-net-connect-memleak
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#44412, nodejs/node#42384)
Appeared test-azure_msft-win2016_vs2017-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/47538/
Last CI https://ci.nodejs.org/job/node-test-pull-request/47550/
Example 
not ok 439 parallel/test-net-connect-memleak
  ---
  duration_ms: 1.109
  severity: fail
  exitcode: 1
  stack: |-
    Mismatched noop function calls. Expected exactly 1, actual 0.
        at Proxy.mustCall (C:\workspace\node-test-binary-windows-js-suites\node\test\common\index.js:338:10)
        at Object.<anonymous> (C:\workspace\node-test-binary-windows-js-suites\node\test\parallel\test-net-connect-memleak.js:33:40)
        at Module._compile (internal/modules/cjs/loader.js:1085:14)
        at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)
        at Module.load (internal/modules/cjs/loader.js:950:32)
        at Function.Module._load (internal/modules/cjs/loader.js:790:12)
        at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:75:12)
        at internal/main/run_main_module.js:17:47
  ...
Reason parallel/test-tls-ticket-cluster
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#42856, nodejs/node#45225)
Appeared test-digitalocean-freebsd12-x64-2, test-nearform-macos10.15-x64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/47551/
Last CI https://ci.nodejs.org/job/node-test-pull-request/47567/
Example 
not ok 2870 parallel/test-tls-ticket-cluster
  ---
  duration_ms: 0.751
  severity: fail
  exitcode: 1
  stack: |-
    [primary] got "listening"
    [primary] connecting 41476 session? false
    [worker] connection reused? false
    [primary] got "not-reused"
    [primary] connecting 41476 session? true
    [worker] connection reused? true
    [primary] got "reused"
    [primary] connecting 41476 session? true
    [worker] connection reused? true
    [primary] got "reused"
    [primary] connecting 41476 session? true
    [worker] connection reused? true
    [primary] got "reused"
    [primary] connecting 41476 session? true
    [worker] connection reused? true
    [primary] got "reused"
    [primary] connecting 41476 session? true
    [worker] connection reused? true
    [primary] got "reused"
    [primary] connecting 41476 session? true
    [worker] connection reused? true
    [primary] got "reused"
    [primary] connecting 41476 session? true
    [worker] connection reused? true
    [primary] got "reused"
 ...

Jenkins Failure

Reason Backing channel 'JNLP4-connect connection from ... is disconnected.
Type JENKINS_FAILURE
Failed PR 4 (nodejs/node#45225, nodejs/node#45236, nodejs/node#45235, nodejs/node#45139)
Appeared test-digitalocean-freebsd12-x64-2, test-digitalocean-freebsd12-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/47553/
Last CI https://ci.nodejs.org/job/node-test-pull-request/47607/
Example 
java.io.IOException: Backing channel 'JNLP4-connect connection from 107.170.28.213/107.170.28.213:18291' is disconnected.
	at hudson.remoting.RemoteInvocationHandler.channelOrFail(RemoteInvocationHandler.java:215)
	at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:285)
	at jdk.proxy2/jdk.proxy2.$Proxy87.isAlive(Unknown Source)
	at hudson.Launcher$RemoteLauncher$ProcImpl.isAlive(Launcher.java:1215)
	at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:1207)
Reason Build timed out (after 60 minutes). Marking the build as failed.
Type JENKINS_FAILURE
Failed PR 3 (nodejs/node#44412, nodejs/node#45176, nodejs/node#45237)
Appeared test-softlayer-ubi81_container-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/47538/
Last CI https://ci.nodejs.org/job/node-test-pull-request/47575/
Example 
Build timed out (after 60 minutes). Marking the build as failed.
Reason Build timed out (after 120 minutes). Marking the build as failed.
Type JENKINS_FAILURE
Failed PR 2 (nodejs/node#45237, nodejs/node#45007)
Appeared test-digitalocean-fedora32-x64-1, test-softlayer-alpine311_container-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/47579/
Last CI https://ci.nodejs.org/job/node-test-pull-request/47592/
Example 
Build timed out (after 120 minutes). Marking the build as failed.

Build Failure

Reason error: remote GitHub already exists.
Type BUILD_FAILURE
Failed PR 11 (nodejs/node#45209, nodejs/node#45148, nodejs/node#45221, nodejs/node#43525, nodejs/node#45230, nodejs/node#42856, nodejs/node#45222, nodejs/node#45236, nodejs/node#45229, nodejs/node#44989, nodejs/node#45143)
Appeared test-rackspace-win2012r2_vs2019-x64-4, test-rackspace-win2012r2_vs2019-x64-5, test-rackspace-win2012r2_vs2017-x64-1, test-rackspace-win2012r2_vs2019-x64-6
First CI https://ci.nodejs.org/job/node-test-pull-request/47529/
Last CI https://ci.nodejs.org/job/node-test-pull-request/47598/
Example 
error: remote GitHub already exists.

> git fetch --prune --no-tags GitHub 
From https://github.com/nodejs/node
 - [deleted]               (none)     -> GitHub/actions/authors-update
 - [deleted]               (none)     -> GitHub/actions/tools-update-corepack
Reason ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?
Type BUILD_FAILURE
Failed PR 2 (nodejs/node#44937, nodejs/node#44989)
Appeared test-joyent-smartos20-x64-4, test-equinix-rhel8_container-arm64-2, test-equinix-ubuntu1804_sharedlibs_container-arm64-4, test-equinix-ubuntu2004_sharedlibs_container-arm64-6, test-equinix-ubuntu2004_container-armv7l-2, test-equinix-ubuntu1804_sharedlibs_container-arm64-2, test-osuosl-aix72-ppc64_be-3, test-joyent-smartos20-x64-3
First CI https://ci.nodejs.org/job/node-test-pull-request/47573/
Last CI https://ci.nodejs.org/job/node-test-pull-request/47594/
Example 
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?
Collecting metadata...
Metadata collection done.
Notifying upstream projects of job completion
Finished: FAILURE
Reason ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for ...
Type BUILD_FAILURE
Failed PR 2 (nodejs/node#45235, nodejs/node#45219)
Appeared test-digitalocean-freebsd12-x64-2, test-digitalocean-freebsd12-x64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/47570/
Last CI https://ci.nodejs.org/job/node-test-pull-request/47583/
Example 
ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for node-test-commit-freebsd/nodes=freebsd12-x64 #46631
Collecting metadata...
Metadata collection done.
Notifying upstream projects of job completion
Finished: FAILURE

Progress

  • parallel/test-vm-timeout-escape-promise-module (4)
  • sequential/test-worker-prof (4)
  • pummel/test-fs-largefile (3)
  • node-api/test_fatal/test2 (2)
  • parallel/test-corepack-yarn-install (2)
  • parallel/test-heapsnapshot-near-heap-limit-by-api-in-worker (2)
  • parallel/test-inspector-esm (2)
  • parallel/test-net-connect-memleak (2)
  • parallel/test-tls-ticket-cluster (2)
  • Backing channel 'JNLP4-connect connection from ... is disconnected. (4)
  • Build timed out (after 60 minutes). Marking the build as failed. (3)
  • Build timed out (after 120 minutes). Marking the build as failed. (2)
  • error: remote GitHub already exists. (11)
  • ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error? (2)
  • ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for ... (2)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions