not ok 259 parallel/test-fs-rmdir-recursive
  ---
  duration_ms: 0.597
  severity: fail
  exitcode: 1
  stack: |-
    (node:16496) [DEP0147] DeprecationWarning: In future versions of Node.js, fs.rmdir(path, { recursive: true }) will be removed. Use fs.rm(path, { recursive: true }) instead
    (Use `node --trace-deprecation ...` to show where the warning was created)
    Can't clean tmpdir: C:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.256
    Files blocking: [ 'rmdir-recursive-0', 'rmdir-recursive-4', 'rmdir-recursive-5' ]
    
    node:assert:991
        throw newErr;
        ^
    
    AssertionError [ERR_ASSERTION]: ifError got unwanted exception: ENOTEMPTY: directory not empty, rmdir 'C:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.256\rmdir-recursive-0\d-3-1'
        at C:\workspace\node-test-binary-windows-js-suites\node\test\common\index.js:364:12
        at C:\workspace\node-test-binary-windows-js-suites\node\test\common\index.js:401:15
        at node:fs:188:23
       ...

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

not ok 3455 sequential/test-cpu-prof-worker-argv
  ---
  duration_ms: 0.651
  severity: fail
  exitcode: 1
  stack: |-
    
    [
      {
        id: 1,
        callFrame: {
          functionName: '(root)',
          scriptId: '0',
          url: '',
          lineNumber: -1,
          columnNumber: -1
        },
        hitCount: 0,
        children: [ 2, 3, 31, 38 ]
      },
      {
        id: 2,
        callFrame: {
          functionName: '(program)',
          scriptId: '0',
          url: '',
          lineNumber: -1,
          columnNumber: -1
        },
        hitCount: 1
      },
      {
        id: 3,
        callFrame: {
          functionName: '',
          scriptId: '10',
          url: 'node:internal/bootstrap/node',
          lineNumber: 0,
          columnNumber: 0
        },
        hitCount: 0,
        children: [ 4 ]
      },
      {
        id: 4,
        callFrame: {
          functionName: 'nativeModuleRequire',
          scriptId: '9',
          url: 'node:internal/bootstrap/loaders'...

not ok 639 parallel/test-common-expect-warning
  ---
  duration_ms: 0.217
  severity: fail
  exitcode: 1
  stack: |-
    node:assert:1026
        throw err;
        ^
    
    AssertionError [ERR_ASSERTION]: The input did not match the regular expression /Unexpected extra warning received/. Input:
    
    '(node:58593) [fhqwhgads] fhqwhgads: fhqwhgads\n' +
      '(Use `node --trace-warnings ...` to show where the warning was created)\n'
    
        at ChildProcess.<anonymous> (/home/iojs/build/workspace/node-test-commit-linux-containered/test/parallel/test-common-expect-warning.js:41:14)
        at ChildProcess.<anonymous> (/home/iojs/build/workspace/node-test-commit-linux-containered/test/common/index.js:401:15)
        at ChildProcess.emit (node:events:522:28)
        at Process.ChildProcess._handle.onexit (node:internal/child_process:291:12) {
      generatedMessage: true,
      code: 'ERR_ASSERTION',
      actual: '(node:58593) [fhqwhgads] fhqwhgads: fhqwhgads\n' +
        '(Use `node --trace-warnings ....

not ok 286 parallel/test-fs-rm
  ---
  duration_ms: 251.362
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...

not ok 228 parallel/test-crypto-dh
  ---
  duration_ms: 240.120
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...

not ok 169 parallel/test-crypto-dh-leak
  ---
  duration_ms: 240.120
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...

not ok 238 parallel/test-crypto-dh-odd-key
  ---
  duration_ms: 240.151
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...

not ok 724 parallel/test-trace-events-fs-sync
  ---
  duration_ms: 240.131
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...

not ok 703 parallel/test-vm-timeout-escape-promise-2
  ---
  duration_ms: 0.250
  severity: fail
  exitcode: 1
  stack: |-
    C:\workspace\node-test-binary-windows-js-suites\node\test\parallel\test-vm-timeout-escape-promise-2.js:20
          throw new Error(
                ^
    
    Error: escaped timeout at 100 milliseconds!
        at loop (C:\workspace\node-test-binary-windows-js-suites\node\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 (C:\workspace\node-test-binary-windows-js-suites\node\test\parallel\test-vm-timeout-escape-promise-2.js:27:6)
        at getActual (node:assert:757:5)
        at Function.throws (node:assert:903:24)
        at Object.<anonymous> (C:\workspace\node-test-binary-windows-js-suites\node\test\parallel\test-vm-timeout-escape-promise-2.js:26:8)
       ...

not ok 3380 node-api/test_fatal/test_threads_report
  ---
  duration_ms: 0.311
  severity: fail
  exitcode: 1
  stack: |-
  ...

not ok 104 parallel/test-child-process-fork-closed-channel-segfault
  ---
  duration_ms: 4.616
  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:534:35)
        at emit (node:internal/child_process:936:14)
        at processTicksAndRejections (node:internal/process/task_queues:84:21) {
      errno: -32,
      code: 'EPIPE',
      syscall: 'write'
    }
    
    Node.js v18.0.0-pre
  ...

not ok 158 parallel/test-crypto-classes
  ---
  duration_ms: 240.82
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...

not ok 1565 parallel/test-inspector-multisession-ws
  ---
  duration_ms: 15.484
  severity: fail
  exitcode: 1
  stack: |-
    [test] Connecting to a child Node process
    [test] Testing /json/list
    [test] Connecting to a child Node process
    [test] Testing /json/list
    [err] Debugger listening on ws://127.0.0.1:57202/0ebf63ca-44c3-4eab-a923-e8cf9d6ec742
    [err] For help, see: https://nodejs.org/en/docs/inspector
    [err] 
    [err] Debugger attached.
    [err] Debugger attached.
    [err] 
    [test] Breaking in code and verifying events are fired
    Timed out waiting for matching notification (Initial pause)
    1
  ...

not ok 588 parallel/test-stdout-to-file
  ---
  duration_ms: 1.640
  severity: fail
  exitcode: 1
  stack: |-
    1048576 chars to C:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.571\stdout.txt...
    done!
    C:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.571\stdout.txt has 1048576 bytes
    Done printing with string
    1048576 chars to C:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.571\stdout.txt...
    done!
    C:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.571\stdout.txt has 1048576 bytes
    Done printing with buffer
    Can't clean tmpdir: C:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.571
    Files blocking: [ 'stdout.txt' ]
    
    C:\workspace\node-test-binary-windows-js-suites\node\test\common\tmpdir.js:54
        throw e;
        ^
    
    Error: EPERM: operation not permitted, lstat '\\?\C:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.571\stdout.txt'
        at lstatSync (node:fs:1516:3)
        at r...

not ok 2616 parallel/test-tls-ticket-cluster
  ---
  duration_ms: 1.438
  severity: fail
  exitcode: 1
  stack: |-
    [primary] got "listening"
    [primary] connecting 27245 session? false
    [worker] connection reused? false
    [primary] got "not-reused"
    [primary] connecting 27245 session? true
    [worker] connection reused? true
    [primary] got "reused"
    [primary] connecting 27245 session? true
    [worker] connection reused? true
    [primary] got "reused"
    [primary] connecting 27245 session? true
    [worker] connection reused? true
    [primary] got "reused"
    [primary] connecting 27245 session? true
    [worker] connection reused? true
    [primary] got "reused"
    [primary] connecting 27245 session? true
    [worker] connection reused? true
    [primary] got "reused"
    [primary] connecting 27245 session? true
    [worker] connection reused? true
    [primary] got "reused"
    [primary] connecting 27245 session? true
    [worker] connection reused? true
    [primary] got "reused"
 ...

not ok 754 parallel/test-windows-failed-heap-allocation
  ---
  duration_ms: 1.725
  severity: fail
  exitcode: 1
  stack: |-
    
    
    <--- Last few GCs --->
    
    [8412:0000015ECFDE8D30]       20 ms: Mark-sweep 2.6 (4.9) -> 2.5 (4.9) MB, 2.5 / 0.0 ms  (average mu = 0.652, current mu = 0.652) allocation failure GC in old space requested
    [8412:0000015ECFDE8D30]       26 ms: Mark-sweep 2.8 (5.1) -> 2.8 (5.4) MB, 3.7 / 0.0 ms  (average mu = 0.525, current mu = 0.374) allocation failure GC in old space requested
    
    
    <--- JS stacktrace --->
    
    
    #
    # Fatal javascript OOM in Reached heap limit
    #
    
    
    node:assert:123
      throw new AssertionError(obj);
      ^
    
    AssertionError [ERR_ASSERTION]: Wrong exit code of 2147483651! Expected 134 for abort
        at C:\workspace\node-test-binary-windows-js-suites\node\test\parallel\test-windows-failed-heap-allocation.js:29:10
        at C:\workspace\node-test-binary-windows-js-suites\node\test\common\index.js:401:15
    ...

not ok 3197 pummel/test-fs-watch-non-recursive
  ---
  duration_ms: 0.121
  severity: fail
  exitcode: 1
  stack: |-
    node:internal/fs/watchers:252
        throw error;
        ^
    
    Error: EMFILE: too many open files, watch '/home/iojs/node-tmp/.tmp.3196'
        at FSWatcher.<computed> (node:internal/fs/watchers:244:19)
        at Object.watch (node:fs:2249:34)
        at Object.<anonymous> (/home/iojs/build/workspace/node-test-commit-arm/test/pummel/test-fs-watch-non-recursive.js:41:20)
        at Module._compile (node:internal/modules/cjs/loader:1097:14)
        at Object.Module._extensions..js (node:internal/modules/cjs/loader:1149:10)
        at Module.load (node:internal/modules/cjs/loader:975:32)
        at Function.Module._load (node:internal/modules/cjs/loader:822:12)
        at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12)
        at node:internal/main/run_main_module:17:47 {
      errno: -24,
      syscall: 'watch',
      code: 'EMFILE',
      path: '/h...

not ok 3155 pummel/test-heapsnapshot-near-heap-limit
  ---
  duration_ms: 720.94
  severity: fail
  exitcode: -15
  stack: |-
    timeout
    
    Testing limit = 0
    [61200:5ea0010]       50 ms: Scavenge 4.4 (4.9) -> 3.9 (5.9) MB, 1.0 / 0.0 ms  (average mu = 1.000, current mu = 1.000) task 
    [61200:5ea0010]       56 ms: Scavenge 4.6 (5.9) -> 4.1 (6.4) MB, 1.0 / 0.0 ms  (average mu = 1.000, current mu = 1.000) allocation failure 
    [61200:5ea0010]       67 ms: Scavenge 4.9 (6.4) -> 4.3 (6.4) MB, 0.5 / 0.0 ms  (average mu = 1.000, current mu = 1.000) allocation failure 
    [61200:5ea0010]       72 ms: Scavenge 5.0 (6.4) -> 4.5 (8.6) MB, 0.8 / 0.0 ms  (average mu = 1.000, current mu = 1.000) allocation failure 
    [61200:5ea0010]       84 ms: Scavenge 6.2 (8.6) -> 4.9 (8.9) MB, 0.6 / 0.0 ms  (average mu = 1.000, current mu = 1.000) allocation failure 
    [61200:5ea0010]       94 ms: Scavenge 6.4 (8.9) -> 5.3 (9.4) MB, 1.0 / 0.0 ms  (average mu = 1.000, current mu = 1.000) allocation failure 
    [6120...

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

not ok 831 sequential/test-debugger-scripts
  ---
  duration_ms: 54.967
  severity: fail
  exitcode: 1
  stack: |-
    /home/iojs/build/workspace/node-test-binary-arm/test/common/debugger.js:84
              reject(new Error([
                     ^
    
    Error: Timeout (10000) while waiting for /break (?:on start )?in/i; found: 
        at Timeout.<anonymous> (/home/iojs/build/workspace/node-test-binary-arm/test/common/debugger.js:84:18)
        at listOnTimeout (node:internal/timers:559:17)
        at processTimers (node:internal/timers:502:7)
    
    Node.js v18.0.0-pre
  ...

not ok 842 sequential/test-inspector-enabled
  ---
  duration_ms: 2.383
  severity: fail
  exitcode: 1
  stack: |-
    Starting inspector on 127.0.0.1:9229 failed: address already in use
    node:assert:399
        throw err;
        ^
    
    AssertionError [ERR_ASSERTION]: inspector.isEnabled() should be true when run with --inspect
        at [eval]:5:1
        at Script.runInThisContext (node:vm:129:12)
        at Object.runInThisContext (node:vm:305:38)
        at node:internal/process/execution:76:19
        at [eval]-wrapper:6:22
        at evalScript (node:internal/process/execution:75:60)
        at node:internal/main/eval_string:27:3 {
      generatedMessage: false,
      code: 'ERR_ASSERTION',
      actual: false,
      expected: true,
      operator: '=='
    }
    
    Node.js v18.0.0-pre
  ...

not ok 3531 sequential/test-net-connect-econnrefused
  ---
  duration_ms: 120.88
  severity: fail
  exitcode: -15
  stack: |-
    timeout
    pending 50 rounds 1
    pending 49 rounds 1
    pending 48 rounds 1
    pending 47 rounds 1
    pending 46 rounds 1
    pending 45 rounds 1
    pending 44 rounds 1
    pending 43 rounds 1
    pending 42 rounds 1
    pending 41 rounds 1
    pending 40 rounds 1
    pending 39 rounds 1
    pending 38 rounds 1
    pending 37 rounds 1
    pending 36 rounds 1
    pending 35 rounds 1
    pending 34 rounds 1
    pending 33 rounds 1
    pending 32 rounds 1
    pending 31 rounds 1
    pending 30 rounds 1
    pending 29 rounds 1
    pending 28 rounds 1
    pending 27 rounds 1
    pending 26 rounds 1
    pending 25 rounds 1
    pending 24 rounds 1
    pending 23 rounds 1
    pending 22 rounds 1
    pending 21 rounds 1
    pending 20 rounds 1
    pending 19 rounds 1
    pending 18 rounds 1
    pending 17 rounds 1
    pending 16 rounds 1
    pending 15 rounds 1
    pending 14 rounds ...

java.io.IOException: Backing channel 'JNLP4-connect connection from p8-aix2-nodejs03.osuosl.org/140.211.9.131:48561' is disconnected.
	at hudson.remoting.RemoteInvocationHandler.channelOrFail(RemoteInvocationHandler.java:216)
	at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:286)
	at com.sun.proxy.$Proxy82.isAlive(Unknown Source)
	at hudson.Launcher$RemoteLauncher$ProcImpl.isAlive(Launcher.java:1213)
	at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:1205)

java.io.IOException: Cannot retrieve the node's workspace for hudson.matrix.MatrixProject@521ad347[node-test-commit-arm]. Most probably the node is offline
	at hudson.matrix.MatrixRun$MatrixRunExecution.getParentWorkspaceLease(MatrixRun.java:173)
	at hudson.matrix.MatrixRun$MatrixRunExecution.decideWorkspace(MatrixRun.java:187)
	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499)
	at hudson.model.Run.execute(Run.java:1888)
	at hudson.matrix.MatrixRun.run(MatrixRun.java:153)

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-arm] $ /bin/bash -ex /tmp/jenkins7728694897015984951.sh
+ '[' -d .git ']'
+ git clean -fdx

ERROR: Step ?Publish JUnit test result report? failed: no workspace for node-test-commit-aix/nodes=aix72-ppc64 #39748
Sending e-mails to: michael_dawson@ca.ibm.com vieuxtech@gmail.com ashley.cripps@ibm.com
Collecting metadata...
Metadata collection done.
Notifying upstream projects of job completion
Finished: FAILURE

Failed to trigger node-test-commit