CI Reliability 2022-03-31

java.io.IOException: Backing channel 'JNLP4-connect connection from 139.178.85.13/139.178.85.13:47766' 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 timed out (after 60 minutes). Marking the build as failed.

ERROR: No acceptable C compiler found!

       Please make sure you have a C compiler installed on your system and/or
       consider adjusting the CC environment variable if you installed
       it in a non-standard prefix.
make: *** [build-ci] Error 1

Failed to trigger node-test-commit

Unknown

not ok 1015 parallel/test-http-header-overflow
  ---
  duration_ms: 0.431
  severity: crashed
  exitcode: -6
  stack: |-
    Found bad BaseObject during clean exit: ConnectionsList
     1: 0xaaaad17311e8 node::DumpBacktrace(_IO_FILE*) [out/Debug/node]
     2: 0xaaaad181d748 node::Abort() [out/Debug/node]
     3: 0xaaaad1754004  [out/Debug/node]
     4: 0xaaaad1761058  [out/Debug/node]
     5: 0xaaaad175409c node::Environment::VerifyNoStrongBaseObjects() [out/Debug/node]
     6: 0xaaaad16c5194 node::SpinEventLoop(node::Environment*) [out/Debug/node]
     7: 0xaaaad188faf0 node::NodeMainInstance::Run(int*, node::Environment*) [out/Debug/node]
     8: 0xaaaad188fa34 node::NodeMainInstance::Run() [out/Debug/node]
     9: 0xaaaad17bf870 node::Start(int, char**) [out/Debug/node]
    10: 0xaaaad2d3a214 main [out/Debug/node]
    11: 0xffffa0eae720 __libc_start_main [/lib/aarch64-linux-gnu/libc.so.6]
    12: 0xaaaad16bf8b0  [out/Debug/node]
  ...

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
  ...

not ok 1637 parallel/test-crypto-keygen
  ---
  duration_ms: 120.75
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...

not ok 249 parallel/test-crypto-secure-heap
  ---
  duration_ms: 360.87
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...

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)...

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)
      ...