Skip to content

CI Reliability 2022-04-03 #240

Open
Open
@github-actions

Description

Failures in node-test-pull-request/43175 to node-test-pull-request/43271 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-04-03 00:12 2 5 29 16 48 6.10%

Jenkins Failure

Reason Backing channel 'JNLP4-connect connection from ... is disconnected.
Type JENKINS_FAILURE
Failed PR 5 (nodejs/node#42443, nodejs/node#42420, nodejs/node#42409, nodejs/node#42115, nodejs/node#42567)
Appeared test-equinix-ubuntu2004_container-armv7l-1, test-equinix-centos7_container-arm64-2, test-equinix-ubuntu1804_container-arm64-2, test-equinix-ubuntu2004_container-arm64-2, test-requireio_mcollina-debian10-armv7l_pi2-1, test-digitalocean-fedora34-x64-2, test-equinix-ubuntu1804_sharedlibs_container-arm64-5, test-equinix-ubuntu2004_sharedlibs_container-arm64-6, test-requireio_joeyvandijk-debian10-armv7l_pi2-1, test-requireio_jasnell-debian10-armv7l_pi2-1, test-requireio_svincent-debian10-armv7l_pi2-3
First CI https://ci.nodejs.org/job/node-test-pull-request/43185/
Last CI https://ci.nodejs.org/job/node-test-pull-request/43261/
Example
java.io.IOException: Backing channel 'JNLP4-connect connection from 145.40.81.219/145.40.81.219:55704' is disconnected.
	at hudson.remoting.RemoteInvocationHandler.channelOrFail(RemoteInvocationHandler.java:216)
	at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:286)
	at com.sun.proxy.$Proxy79.isAlive(Unknown Source)
	at hudson.Launcher$RemoteLauncher$ProcImpl.isAlive(Launcher.java:1213)
	at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:1205)

Reason Build timed out (after 60 minutes). Marking the build as failed.
Type JENKINS_FAILURE
Failed PR 3 (nodejs/node#42466, nodejs/node#42410, nodejs/node#42420)
Appeared test-softlayer-ubi81_container-x64-1, test-rackspace-win2012r2_vs2019-x64-4
First CI https://ci.nodejs.org/job/node-test-pull-request/43183/
Last CI https://ci.nodejs.org/job/node-test-pull-request/43271/
Example
Build timed out (after 60 minutes). Marking the build as failed.

Git Failure

Build Failure

Reason ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for ...
Type BUILD_FAILURE
Failed PR 2 (nodejs/node#38545, nodejs/node#42387)
Appeared test-nearform-macos11.0-arm64-1, test-orka-macos10.15-x64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/43222/
Last CI https://ci.nodejs.org/job/node-test-pull-request/43267/
Example
ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for node-test-commit-osx-arm/nodes=osx11 #5049
Collecting metadata...
Metadata collection done.
Notifying upstream projects of job completion
Finished: FAILURE

Reason Failed to trigger node-test-commit
Type BUILD_FAILURE
Failed PR 2 (nodejs/node#42399, nodejs/node#43206)
Appeared test-packetnet-ubuntu1804-x64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/43184/
Last CI https://ci.nodejs.org/job/node-test-pull-request/43208/
Example
Failed to trigger node-test-commit

undefined

Reason Unknown
Type undefined
Failed PR 6 (nodejs/node#42278, nodejs/node#42471, nodejs/node#42409, nodejs/node#42466, nodejs/node#42512, nodejs/node#42559)
Appeared test-nearform_arm-win10_vs2019-arm64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/43179/
Last CI https://ci.nodejs.org/job/node-test-pull-request/43259/
Example
Unknown

JSTest Failure

Reason parallel/test-child-process-fork-closed-channel-segfault
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#42442, nodejs/node#42486)
Appeared test-requireio_securogroup-debian10-arm64_pi3-2, test-requireio_jasnell-debian10-armv7l_pi2-1
First CI https://ci.nodejs.org/job/node-test-pull-request/43175/
Last CI https://ci.nodejs.org/job/node-test-pull-request/43198/
Example
not ok 106 parallel/test-child-process-fork-closed-channel-segfault
  ---
  duration_ms: 3.784
  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:539:35)
        at emit (node:internal/child_process:936:14)
        at processTicksAndRejections (node:internal/process/task_queues:83:21) {
      errno: -32,
      code: 'EPIPE',
      syscall: 'write'
    }
    
    Node.js v18.0.0-pre
  ...


Reason parallel/test-trace-events-fs-sync
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#42471, nodejs/node#42466)
Appeared test-azure_msft-win10_vs2019-x64-2
First CI https://ci.nodejs.org/job/node-test-pull-request/43193/
Last CI https://ci.nodejs.org/job/node-test-pull-request/43218/
Example
not ok 695 parallel/test-trace-events-fs-sync
  ---
  duration_ms: 1.993
  severity: fail
  exitcode: 1
  stack: |-
    Can't clean tmpdir: C:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.691
    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:345\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:584:3)\r\n' +
          '    at Object.writeFileSync (node:fs:2169: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-vm-timeout-escape-promise-2
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#42115, nodejs/node#42466)
Appeared test-ibm-rhel8-s390x-1
First CI https://ci.nodejs.org/job/node-test-pull-request/43234/
Last CI https://ci.nodejs.org/job/node-test-pull-request/43237/
Example
not ok 2704 parallel/test-vm-timeout-escape-promise-2
  ---
  duration_ms: 0.239
  severity: fail
  exitcode: 1
  stack: |-
    /home/iojs/build/workspace/node-test-commit-linuxone/test/parallel/test-vm-timeout-escape-promise-2.js:20
          throw new Error(
                ^
    
    Error: escaped timeout at 100 milliseconds!
        at loop (/home/iojs/build/workspace/node-test-commit-linuxone/test/parallel/test-vm-timeout-escape-promise-2.js:20:13)
        at evalmachine.<anonymous>:1:30
        at Script.runInContext (node:vm:139:12)
        at Script.runInNewContext (node:vm:144:17)
        at Object.runInNewContext (node:vm:298:38)
        at assert.throws.code (/home/iojs/build/workspace/node-test-commit-linuxone/test/parallel/test-vm-timeout-escape-promise-2.js:27:6)
        at getActual (node:assert:756:5)
        at Function.throws (node:assert:902:24)
        at Object.<anonymous> (/home/iojs/build/workspace/node-test-commit-linuxone/test/parallel/test-vm-timeout-escape-promise-2.js:26:8)
      ...

Progress

  • Backing channel 'JNLP4-connect connection from ... is disconnected. (5)
  • Build timed out (after 60 minutes). Marking the build as failed. (3)
  • ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for ... (2)
  • Failed to trigger node-test-commit (2)
  • Unknown (6)
  • parallel/test-child-process-fork-closed-channel-segfault (2)
  • parallel/test-trace-events-fs-sync (2)
  • parallel/test-vm-timeout-escape-promise-2 (2)

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

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