CI Reliability 2022-06-24

java.io.IOException: Backing channel 'JNLP4-connect connection from 145.40.99.31/145.40.99.31:60588' 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)

ERROR: Build step failed with exception
java.lang.NullPointerException: no workspace from node hudson.slaves.DumbSlave[test-equinix-ubuntu2004_container-armv7l-2] which is computer hudson.slaves.SlaveComputer@2ad6001 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)

ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?
[PostBuildScript] - [INFO] Executing post build scripts.
[node-test-binary-armv7l] $ /bin/bash -ex /tmp/jenkins6706608375315491508.sh
+ '[' -d .git ']'
+ git clean -fdx

Unknown

not ok 1171 parallel/test-http-server-request-timeouts-mixed
  ---
  duration_ms: 3.471
  severity: fail
  exitcode: 1
  stack: |-
    node:assert:399
        throw err;
        ^
    
    AssertionError [ERR_ASSERTION]: The expression evaluated to a falsy value:
    
      assert(request2.completed)
    
        at Timeout._onTimeout (/Users/iojs/build/workspace/node-test-commit-osx/nodes/osx1015/test/parallel/test-http-server-request-timeouts-mixed.js:106:5)
        at listOnTimeout (node:internal/timers:564:17)
        at process.processTimers (node:internal/timers:507:7) {
      generatedMessage: true,
      code: 'ERR_ASSERTION',
      actual: false,
      expected: true,
      operator: '=='
    }
    
    Node.js v19.0.0-pre
  ...

not ok 3044 parallel/test-worker-fshandles-error-on-termination
  ---
  duration_ms: 120.89
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...

not ok 715 parallel/test-domain-no-error-handler-abort-on-uncaught-8
  ---
  duration_ms: 120.599
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...

not ok 3046 parallel/test-worker-fshandles-open-close-on-termination
  ---
  duration_ms: 120.104
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...

not ok 734 parallel/test-domain-no-error-handler-abort-on-uncaught-9
  ---
  duration_ms: 120.119
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...

not ok 973 parallel/test-domain-throw-error-then-throw-from-uncaught-exception-handler
  ---
  duration_ms: 120.203
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...

not ok 714 parallel/test-domain-no-error-handler-abort-on-uncaught-7
  ---
  duration_ms: 120.597
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...

not ok 989 parallel/test-domain-with-abort-on-uncaught-exception
  ---
  duration_ms: 120.186
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...

not ok 710 parallel/test-domain-no-error-handler-abort-on-uncaught-6
  ---
  duration_ms: 120.215
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...

not ok 2202 parallel/test-net-connect-reset-until-connected
  ---
  duration_ms: 120.16
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...

not ok 708 parallel/test-domain-no-error-handler-abort-on-uncaught-4
  ---
  duration_ms: 120.155
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...

not ok 709 parallel/test-domain-no-error-handler-abort-on-uncaught-5
  ---
  duration_ms: 120.231
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...

not ok 3062 parallel/test-worker-http2-stream-terminate
  ---
  duration_ms: 120.145
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...

not ok 3469 node-api/test_fatal/test_threads_report
  ---
  duration_ms: 120.89
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...

not ok 704 parallel/test-trace-events-fs-sync
  ---
  duration_ms: 1.964
  severity: fail
  exitcode: 1
  stack: |-
    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:347\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:599:3)\r\n' +
          '    at Object.writeFileSync (node:fs:2221:35)\r\n' +
          '    at [eval]:1:4\r\n' +
          '    at Script.runInThisContext (node:vm:130:12)\r\n' +
          '    at Object.runInThisContext (node:vm:306:38)\r\n' +
          '    at node:internal/process/execution:76:19\r\n' +
          '    at [eval]-wrapper:6:22\r\n' +
          '    at evalScript (nod...

not ok 3294 pummel/test-heapsnapshot-near-heap-limit
  ---
  duration_ms: 720.133
  severity: fail
  exitcode: -15
  stack: |-
    timeout
    
    Testing limit = 0
    [28589:681b010]       66 ms: Scavenge 5.4 (5.7) -> 4.9 (6.7) MB, 1.1 / 0.0 ms  (average mu = 1.000, current mu = 1.000) task; 
    [28589:681b010]       73 ms: Scavenge 5.5 (6.7) -> 5.1 (7.2) MB, 1.2 / 0.0 ms  (average mu = 1.000, current mu = 1.000) allocation failure; 
    [28589:681b010]       83 ms: Scavenge 5.9 (7.2) -> 5.3 (7.2) MB, 0.8 / 0.0 ms  (average mu = 1.000, current mu = 1.000) allocation failure; 
    [28589:681b010]       91 ms: Scavenge 6.0 (7.2) -> 5.5 (9.4) MB, 1.1 / 0.0 ms  (average mu = 1.000, current mu = 1.000) allocation failure; 
    [28589:681b010]      103 ms: Scavenge 7.2 (9.4) -> 6.0 (9.7) MB, 0.6 / 0.0 ms  (average mu = 1.000, current mu = 1.000) allocation failure; 
    [28589:681b010]      112 ms: Scavenge 7.1 (9.7) -> 6.3 (10.4) MB, 1.3 / 0.0 ms  (average mu = 1.000, current mu = 1.000) task; 
    [28589:681b...

not ok 707 parallel/test-domain-no-error-handler-abort-on-uncaught-3
  ---
  duration_ms: 120.152
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...

not ok 2932 parallel/test-vm-timeout-escape-promise-2
  ---
  duration_ms: 0.256
  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)
      ...

not ok 3059 parallel/test-worker-heap-snapshot
  ---
  duration_ms: 0.916
  severity: crashed
  exitcode: -6
  stack: |-
    FATAL ERROR: HandleScope::HandleScope Entering the V8 API without proper locking in place
     1: 0xafbae0 node::Abort() [out/Release/node]
     2: 0xa0c1b5 node::FatalError(char const*, char const*) [out/Release/node]
     3: 0xcec4aa v8::Utils::ReportApiFailure(char const*, char const*) [out/Release/node]
     4: 0xceda0c v8::HandleScope::HandleScope(v8::Isolate*) [out/Release/node]
     5: 0xa4f077 node::BaseObject::~BaseObject() [out/Release/node]
     6: 0xa4df6e node::AsyncWrap::~AsyncWrap() [out/Release/node]
     7: 0xbcb0e8 node::worker::WorkerHeapSnapshotTaker::~WorkerHeapSnapshotTaker() [out/Release/node]
     8: 0xbc3bff  [out/Release/node]
     9: 0xa7a7ba node::Environment::RunAndClearInterrupts() [out/Release/node]
    10: 0xa7a867  [out/Release/node]
    11: 0xe43dfc v8::internal::Isolate::InvokeApiInterruptCallbacks() [out/Release/node]
    12: 0xe5cf01 v8::internal::St...

not ok 3286 report/test-report-fatal-error
  ---
  duration_ms: 120.145
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...

not ok 3661 abort/test-signal-handler
  ---
  duration_ms: 120.104
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...

not ok 3662 abort/test-worker-abort-uncaught-exception
  ---
  duration_ms: 120.186
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...

not ok 3664 abort/test-zlib-invalid-internals-usage
  ---
  duration_ms: 120.183
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...

not ok 3468 node-api/test_fatal/test_threads
  ---
  duration_ms: 120.66
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...

not ok 705 parallel/test-domain-no-error-handler-abort-on-uncaught-1
  ---
  duration_ms: 120.118
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...

not ok 706 parallel/test-domain-no-error-handler-abort-on-uncaught-2
  ---
  duration_ms: 120.198
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...

not ok 873 parallel/test-gc-http-client-timeout
  ---
  duration_ms: 0.674
  severity: fail
  exitcode: 1
  stack: |-
    node:events:515
          throw er; // Unhandled 'error' event
          ^
    
    Error: connect ECONNRESET 127.0.0.1:42450 - Local (127.0.0.1:42647)
        at internalConnect (node:net:999:16)
        at defaultTriggerAsyncIdScope (node:internal/async_hooks:464:18)
        at GetAddrInfoReqWrap.emitLookup [as callback] (node:net:1145:9)
        at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:113:8)
    Emitted 'error' event on ClientRequest instance at:
        at Socket.socketErrorListener (node:_http_client:465:9)
        at Socket.emit (node:events:537: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: -54,
      code: 'ECONNRESET',
      syscall: 'connect',
      address: '127.0.0.1',
      por...

not ok 3670 sequential/test-vm-timeout-escape-promise-module-2
  ---
  duration_ms: 0.211
  severity: fail
  exitcode: 1
  stack: |-
    (node:303461) 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)
    /home/iojs/build/workspace/node-test-commit-linuxone/test/sequential/test-vm-timeout-escape-promise-module-2.js:22
          throw new Error(
                ^
    
    Error: escaped timeout at 100 milliseconds!
        at loop (/home/iojs/build/workspace/node-test-commit-linuxone/test/sequential/test-vm-timeout-escape-promise-module-2.js:22:13)
        at vm:module(0):1:30
        at SourceTextModule.evaluate (node:internal/vm/module:226:23)
        at assert.rejects.code (/home/iojs/build/workspace/node-test-commit-linuxone/test/sequential/test-vm-timeout-escape-promise-module-2.js:38:16)
        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    
    N...