You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?
Collecting metadata...
Metadata collection done.
Notifying upstream projects of job completion
Finished: FAILURE
Reason
ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error?
not ok 259 parallel/test-fs-rmdir-recursive
---
duration_ms: 0.597
severity: fail
exitcode: 1
stack: |-
(node:3104) [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-1', '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-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
at CB ...
not ok 325 parallel/test-common-expect-warning
---
duration_ms: 0.456
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:
''
at ChildProcess.<anonymous> (/home/iojs/build/workspace/node-test-commit-arm/test/parallel/test-common-expect-warning.js:41:14)
at ChildProcess.<anonymous> (/home/iojs/build/workspace/node-test-commit-arm/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: '',
expected: /Unexpected extra warning received/,
operator: 'match'
}
Node.js v18.0.0-pre
...
not ok 2780 parallel/test-vm-timeout-escape-promise-2
---
duration_ms: 0.442
severity: fail
exitcode: 1
stack: |-
/usr/home/iojs/build/workspace/node-test-commit-freebsd/nodes/freebsd12-x64/test/parallel/test-vm-timeout-escape-promise-2.js:20
throw new Error(
^
Error: escaped timeout at 100 milliseconds!
at loop (/usr/home/iojs/build/workspace/node-test-commit-freebsd/nodes/freebsd12-x64/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 (/usr/home/iojs/build/workspace/node-test-commit-freebsd/nodes/freebsd12-x64/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> (/usr/home/iojs/build/workspace/node-test-commi...
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 844 sequential/test-worker-prof
---
duration_ms: 30.293
severity: fail
exitcode: 1
stack: |-
node:assert:123
throw new AssertionError(obj);
^
AssertionError [ERR_ASSERTION]: child exited with signal: {
error: Error: spawnSync C:\workspace\node-test-binary-windows-js-suites\node\Release\node.exe ETIMEDOUT
at Object.spawnSync (node:internal/child_process:1109:20)
at spawnSync (node:child_process:803:24)
at Object.<anonymous> (C:\workspace\node-test-binary-windows-js-suites\node\test\sequential\test-worker-prof.js:53:23)
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:intern...
Progress
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error? (2)
ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error? (2)
Failures in node-test-pull-request/42105 to node-test-pull-request/42203 that failed more than 2 PRs
(Generated with
ncu-ci walk pr --stats=true --markdown /home/runner/work/reliability/reliability/results.md)Jenkins Failure
Git Failure
Build Failure
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?Example
ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error?Example
JSTest Failure
parallel/test-fs-rmdir-recursiveExample
parallel/test-crypto-secure-heapExample
parallel/test-child-process-pipe-dataflowExample
parallel/test-common-expect-warningExample
parallel/test-finalization-group-regular-gcExample
sequential/test-cpu-prof-worker-argvExample
node-api/test_fatal/test_threadsExample
node-api/test_fatal/test_threads_reportExample
parallel/test-crypto-dh-constructorExample
parallel/test-child-process-fork-closed-channel-segfaultExample
parallel/test-crypto-dhExample
parallel/test-crypto-dh-leakExample
parallel/test-fs-rmExample
parallel/test-stream-mapExample
parallel/test-vm-timeout-escape-promise-2Example
parallel/test-windows-failed-heap-allocationExample
sequential/test-debugger-heap-profilerExample
sequential/test-debugger-run-after-quit-restartExample
sequential/test-net-connect-econnrefusedExample
sequential/test-worker-profExample
Progress
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?(2)ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error?(2)parallel/test-fs-rmdir-recursive(10)parallel/test-crypto-secure-heap(5)parallel/test-child-process-pipe-dataflow(4)parallel/test-common-expect-warning(4)parallel/test-finalization-group-regular-gc(4)sequential/test-cpu-prof-worker-argv(4)node-api/test_fatal/test_threads(3)node-api/test_fatal/test_threads_report(3)parallel/test-crypto-dh-constructor(3)parallel/test-child-process-fork-closed-channel-segfault(2)parallel/test-crypto-dh(2)parallel/test-crypto-dh-leak(2)parallel/test-fs-rm(2)parallel/test-stream-map(2)parallel/test-vm-timeout-escape-promise-2(2)parallel/test-windows-failed-heap-allocation(2)sequential/test-debugger-heap-profiler(2)sequential/test-debugger-run-after-quit-restart(2)sequential/test-net-connect-econnrefused(2)sequential/test-worker-prof(2)The text was updated successfully, but these errors were encountered: