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
not ok 259 parallel/test-fs-rmdir-recursive
---
duration_ms: 0.759
severity: fail
exitcode: 1
stack: |-
(node:9100) [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\d-2-1\d-1-2'
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...
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 462 async-hooks/test-callback-error
---
duration_ms: 120.152
severity: fail
exitcode: -15
stack: |-
timeout
start case 1
end case 1: 279.989ms
start case 2
end case 2: 329.512ms
start case 3
...
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
...
Failures in node-test-pull-request/42079 to node-test-pull-request/42178 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
JSTest Failure
parallel/test-fs-rmdir-recursiveExample
sequential/test-cpu-prof-worker-argvExample
parallel/test-common-expect-warningExample
parallel/test-child-process-pipe-dataflowExample
parallel/test-crypto-secure-heapExample
parallel/test-finalization-group-regular-gcExample
parallel/test-fs-rmExample
node-api/test_fatal/test_threadsExample
node-api/test_fatal/test_threads_reportExample
parallel/test-crypto-dh-constructorExample
abort/test-abort-backtraceExample
abort/test-abort-fatal-errorExample
async-hooks/test-callback-errorExample
parallel/test-child-process-fork-closed-channel-segfaultExample
parallel/test-crypto-classesExample
parallel/test-crypto-dhExample
parallel/test-crypto-dh-leakExample
parallel/test-domain-no-error-handler-abort-on-uncaught-2Example
parallel/test-domain-no-error-handler-abort-on-uncaught-3Example
parallel/test-domain-no-error-handler-abort-on-uncaught-4Example
parallel/test-domain-no-error-handler-abort-on-uncaught-5Example
parallel/test-stdout-to-fileExample
parallel/test-stream-mapExample
parallel/test-trace-events-fs-syncExample
parallel/test-windows-failed-heap-allocationExample
report/test-report-fatal-errorExample
sequential/test-debugger-heap-profilerExample
sequential/test-debugger-restart-messageExample
sequential/test-debugger-run-after-quit-restartExample
Progress
ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error?(2)parallel/test-fs-rmdir-recursive(8)sequential/test-cpu-prof-worker-argv(6)parallel/test-common-expect-warning(5)parallel/test-child-process-pipe-dataflow(4)parallel/test-crypto-secure-heap(4)parallel/test-finalization-group-regular-gc(4)parallel/test-fs-rm(4)node-api/test_fatal/test_threads(3)node-api/test_fatal/test_threads_report(3)parallel/test-crypto-dh-constructor(3)abort/test-abort-backtrace(2)abort/test-abort-fatal-error(2)async-hooks/test-callback-error(2)parallel/test-child-process-fork-closed-channel-segfault(2)parallel/test-crypto-classes(2)parallel/test-crypto-dh(2)parallel/test-crypto-dh-leak(2)parallel/test-domain-no-error-handler-abort-on-uncaught-2(2)parallel/test-domain-no-error-handler-abort-on-uncaught-3(2)parallel/test-domain-no-error-handler-abort-on-uncaught-4(2)parallel/test-domain-no-error-handler-abort-on-uncaught-5(2)parallel/test-stdout-to-file(2)parallel/test-stream-map(2)parallel/test-trace-events-fs-sync(2)parallel/test-windows-failed-heap-allocation(2)report/test-report-fatal-error(2)sequential/test-debugger-heap-profiler(2)sequential/test-debugger-restart-message(2)sequential/test-debugger-run-after-quit-restart(2)The text was updated successfully, but these errors were encountered: