Skip to content

CI Reliability 2022-04-06 #243

New issue
New issue
Open
Open
CI Reliability 2022-04-06#243
@github-actions

Description

@github-actions
github-actions
bot
opened on Apr 6, 2022

Failures in node-test-pull-request/43245 to node-test-pull-request/43344 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-06 00:13 0 17 15 23 45 22.08%

Jenkins Failure

Reason Backing channel 'JNLP4-connect connection from ... is disconnected.
Type JENKINS_FAILURE
Failed PR 4 (nodejs/node#42567, nodejs/node#42573, nodejs/node#41513, nodejs/node#42409)
Appeared test-requireio_mcollina-debian10-armv7l_pi2-1, test-requireio_securogroup-debian10-arm64_pi3-1, test-digitalocean-freebsd12-x64-2, test-equinix-debian10_container-armv7l-2, test-equinix-ubuntu2004_container-armv7l-2, test-requireio_jasnell-debian10-armv7l_pi2-1, test-equinix-ubuntu2004_container-armv7l-1
First CI https://ci.nodejs.org/job/node-test-pull-request/43261/
Last CI https://ci.nodejs.org/job/node-test-pull-request/43327/
Example 
java.io.IOException: Backing channel 'JNLP4-connect connection from 203.217.18.114/203.217.18.114:53872' 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)

Build Failure

Reason ERROR: Build step failed with exception
Type BUILD_FAILURE
Failed PR 3 (nodejs/node#42584, nodejs/node#42459, nodejs/node#42409)
Appeared test-requireio_svincent-debian10-armv7l_pi2-1, test-requireio_kahwee-debian10-arm64_pi3-1, test-requireio_louiscntr-debian10-armv7l_pi2-1, test-requireio_davglass-debian10-arm64_pi3-1, test-requireio_ceejbot-debian10-armv7l_pi2-1, test-requireio_notthetup_sayanee-debian10-arm64_pi3-1, test-requireio_williamkapke-debian10-arm64_pi3-1, test-requireio_svincent-debian10-armv7l_pi2-2
First CI https://ci.nodejs.org/job/node-test-pull-request/43292/
Last CI https://ci.nodejs.org/job/node-test-pull-request/43343/
Example 
ERROR: Build step failed with exception
java.lang.NullPointerException: no workspace from node hudson.slaves.DumbSlave[test-requireio_svincent-debian10-armv7l_pi2-1] which is computer hudson.slaves.SlaveComputer@5831cbab and has channel null
	at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:113)
	at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:91)
	at org.jenkinsci.plugins.postbuildscript.processor.Processor.processBuildSteps(Processor.java:180)
	at org.jenkinsci.plugins.postbuildscript.processor.Processor.processScripts(Processor.java:91)
Reason ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for ...
Type BUILD_FAILURE
Failed PR 2 (nodejs/node#42387, nodejs/node#41513)
Appeared test-digitalocean-freebsd12-x64-2, test-nearform-macos11.0-arm64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/43267/
Last CI https://ci.nodejs.org/job/node-test-pull-request/43289/
Example 
ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for node-test-commit-freebsd/nodes=freebsd12-x64 #43476
Collecting metadata...
Metadata collection done.
Notifying upstream projects of job completion
Finished: FAILURE
Reason fatal: sent error to the client: git upload-archive: archiver died with error
Type BUILD_FAILURE
Failed PR 2 (nodejs/node#42278, nodejs/node#42338)
Appeared undefined
First CI https://ci.nodejs.org/job/node-test-pull-request/43270/
Last CI https://ci.nodejs.org/job/node-test-pull-request/43320/
Example 
fatal: sent error to the client: git upload-archive: archiver died with error
fatal: no such ref: jenkins-node-test-commit-windows-fanned-484663b89768cd3b99a255cf9463ff101c82214f

Git Failure

undefined

Reason Unknown
Type undefined
Failed PR 6 (nodejs/node#42559, nodejs/node#42584, nodejs/node#42278, nodejs/node#42577, nodejs/node#39841, nodejs/node#42573)
Appeared test-nearform_arm-win10_vs2019-arm64-1
First CI https://ci.nodejs.org/job/node-test-pull-request/43259/
Last CI https://ci.nodejs.org/job/node-test-pull-request/43312/
Example 
Unknown

JSTest Failure

Reason parallel/test-child-process-fork-closed-channel-segfault
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#42531, nodejs/node#42589)
Appeared test-requireio_williamkapke-debian10-arm64_pi3-2, test-requireio_joeyvandijk-debian10-armv7l_pi2-2
First CI https://ci.nodejs.org/job/node-test-pull-request/43300/
Last CI https://ci.nodejs.org/job/node-test-pull-request/43328/
Example 
not ok 106 parallel/test-child-process-fork-closed-channel-segfault
  ---
  duration_ms: 3.186
  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-child-process-set-blocking
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#42573, nodejs/node#42338)
Appeared test-equinix-debian10_container-armv7l-1
First CI https://ci.nodejs.org/job/node-test-pull-request/43312/
Last CI https://ci.nodejs.org/job/node-test-pull-request/43323/
Example 
not ok 189 parallel/test-child-process-set-blocking
  ---
  duration_ms: 0.173
  severity: fail
  exitcode: 1
  stack: |-
    node:events:505
          throw er; // Unhandled 'error' event
          ^
    
    Error: spawn python ENOENT
        at Process.ChildProcess._handle.onexit (node:internal/child_process:283:19)
        at onErrorNT (node:internal/child_process:476:16)
        at processTicksAndRejections (node:internal/process/task_queues:82:21)
    Emitted 'error' event on ChildProcess instance at:
        at Process.ChildProcess._handle.onexit (node:internal/child_process:289:12)
        at onErrorNT (node:internal/child_process:476:16)
        at processTicksAndRejections (node:internal/process/task_queues:82:21) {
      errno: -2,
      code: 'ENOENT',
      syscall: 'spawn python',
      path: 'python',
      spawnargs: [ '-c', 'print(100000 * "C")' ]
    }
    
    Node.js v18.0.0-pre
  ...
Reason parallel/test-fetch
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#42583, nodejs/node#41263)
Appeared test-equinix-ubuntu1804_sharedlibs_container-arm64-1, test-requireio_rvagg-debian10-armv7l_pi2-1
First CI https://ci.nodejs.org/job/node-test-pull-request/43283/
Last CI https://ci.nodejs.org/job/node-test-pull-request/43322/
Example 
not ok 730 parallel/test-fetch
  ---
  duration_ms: 2.545
  severity: crashed
  exitcode: -6
  stack: |-
    (node:4011889) ExperimentalWarning: The Fetch API is an experimental feature. This feature could change at any time
    (Use `node --trace-warnings ...` to show where the warning was created)
    Found bad BaseObject during clean exit: ConnectionsList
     1: 0xaaaaafc3a1e8 node::DumpBacktrace(_IO_FILE*) [out/Debug/node]
     2: 0xaaaaafd29bfc node::Abort() [out/Debug/node]
     3: 0xaaaaafc5d004  [out/Debug/node]
     4: 0xaaaaafc6a058  [out/Debug/node]
     5: 0xaaaaafc5d09c node::Environment::VerifyNoStrongBaseObjects() [out/Debug/node]
     6: 0xaaaaafbce194 node::SpinEventLoop(node::Environment*) [out/Debug/node]
     7: 0xaaaaafd99fac node::NodeMainInstance::Run(int*, node::Environment*) [out/Debug/node]
     8: 0xaaaaafd99ef0 node::NodeMainInstance::Run() [out/Debug/node]
     9: 0xaaaaafcc88e4 node::Start(int, char**) [out/Debug/node]
    10: 0xaaaab1235214 main [out/Debug/node]
    11: 0xffffb...
Reason parallel/test-net-connect-memleak
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#42584, nodejs/node#39841)
Appeared test-rackspace-win2012r2_vs2017-x64-4
First CI https://ci.nodejs.org/job/node-test-pull-request/43274/
Last CI https://ci.nodejs.org/job/node-test-pull-request/43311/
Example 
not ok 467 parallel/test-net-connect-memleak
  ---
  duration_ms: 0.257
  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:369: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 (node:internal/modules/cjs/loader:1106:14)
        at Object.Module._extensions..js (node:internal/modules/cjs/loader:1160:10)
        at Module.load (node:internal/modules/cjs/loader:982:32)
        at Function.Module._load (node:internal/modules/cjs/loader:829:12)
        at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12)
        at node:internal/main/run_main_module:17:47
  ...
Reason pummel/test-child-process-spawn-loop
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#42573, nodejs/node#42338)
Appeared test-equinix-debian10_container-armv7l-1
First CI https://ci.nodejs.org/job/node-test-pull-request/43312/
Last CI https://ci.nodejs.org/job/node-test-pull-request/43323/
Example 
not ok 3218 pummel/test-child-process-spawn-loop
  ---
  duration_ms: 0.333
  severity: fail
  exitcode: 1
  stack: |-
    node:events:505
          throw er; // Unhandled 'error' event
          ^
    
    Error: spawn python ENOENT
        at Process.ChildProcess._handle.onexit (node:internal/child_process:283:19)
        at onErrorNT (node:internal/child_process:476:16)
        at processTicksAndRejections (node:internal/process/task_queues:82:21)
    Emitted 'error' event on ChildProcess instance at:
        at Process.ChildProcess._handle.onexit (node:internal/child_process:289:12)
        at onErrorNT (node:internal/child_process:476:16)
        at processTicksAndRejections (node:internal/process/task_queues:82:21) {
      errno: -2,
      code: 'ENOENT',
      syscall: 'spawn python',
      path: 'python',
      spawnargs: [ '-c', 'print(1024000 * "C")' ]
    }
    
    Node.js v18.0.0-pre
  ...
Reason sequential/test-worker-prof
Type JS_TEST_FAILURE
Failed PR 2 (nodejs/node#42278, nodejs/node#39841)
Appeared 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/43277/
Last CI https://ci.nodejs.org/job/node-test-pull-request/43303/
Example 
not ok 854 sequential/test-worker-prof
  ---
  duration_ms: 4.35
  severity: fail
  exitcode: 1
  stack: |-
    node:assert:123
      throw new AssertionError(obj);
      ^
    
    AssertionError [ERR_ASSERTION]: child exited with non-zero status:                      {
      status: 3221226505,
      signal: null,
      output: [ null, '', '' ],
      pid: 11992,
      stdout: '',
      stderr: ''
    }
        at Object.<anonymous> (C:\workspace\node-test-binary-windows-js-suites\node\test\sequential\test-worker-prof.js:61:10)
        at Module._compile (node:internal/modules/cjs/loader:1106:14)
        at Object.Module._extensions..js (node:internal/modules/cjs/loader:1160:10)
        at Module.load (node:internal/modules/cjs/loader:982:32)
        at Function.Module._load (node:internal/modules/cjs/loader:829:12)
        at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12)
        at node:internal/main/run_main_module:17:47 {
      generatedMessage: false,
      code: 'ER...

Progress

  • Backing channel 'JNLP4-connect connection from ... is disconnected. (4)
  • ERROR: Build step failed with exception (3)
  • ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for ... (2)
  • fatal: sent error to the client: git upload-archive: archiver died with error (2)
  • Unknown (6)
  • parallel/test-child-process-fork-closed-channel-segfault (2)
  • parallel/test-child-process-set-blocking (2)
  • parallel/test-fetch (2)
  • parallel/test-net-connect-memleak (2)
  • pummel/test-child-process-spawn-loop (2)
  • sequential/test-worker-prof (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