Open
Description
Failures in node-test-pull-request/45710 to node-test-pull-request/45808 that failed more than 2 PRs
(Generated with ncu-ci walk pr --stats=true --markdown /home/runner/work/reliability/reliability/results.md
)
UTC Time | RUNNING | SUCCESS | UNSTABLE | ABORTED | FAILURE | Green Rate |
---|---|---|---|---|---|---|
2022-08-03 00:17 | 0 | 5 | 39 | 1 | 55 | 5.05% |
Jenkins Failure
Reason | Backing channel 'JNLP4-connect connection from ... is disconnected. |
---|---|
Type | JENKINS_FAILURE |
Failed PR | 7 (nodejs/node#44013, nodejs/node#43942, nodejs/node#44064, nodejs/node#44075, nodejs/node#44081, nodejs/node#44080, nodejs/node#38905) |
Appeared | test-nearform-macos10.15-x64-3, test-digitalocean-freebsd12-x64-2, test-nearform-macos11.0-arm64-1, test-digitalocean-freebsd12-x64-1, test-equinix-ubuntu2004_container-armv7l-2 |
First CI | https://ci.nodejs.org/job/node-test-pull-request/45710/ |
Last CI | https://ci.nodejs.org/job/node-test-pull-request/45797/ |
Example
java.io.IOException: Backing channel 'JNLP4-connect connection from ip-83-147-191-72.broadband.digiweb.ie/83.147.191.72:62316' 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)
Git Failure
Build Failure
Reason | ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error? |
---|---|
Type | BUILD_FAILURE |
Failed PR | 2 (nodejs/node#44032, nodejs/node#44080) |
Appeared | test-equinix-ubuntu2004_container-armv7l-1, test-equinix-rhel8_container-arm64-1, test-equinix-ubuntu1804_container-arm64-2, test-equinix-ubuntu2004_container-arm64-2, test-equinix-ubuntu1804_sharedlibs_container-arm64-3 |
First CI | https://ci.nodejs.org/job/node-test-pull-request/45723/ |
Last CI | https://ci.nodejs.org/job/node-test-pull-request/45805/ |
Example
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/jenkins6422209372664579818.sh
+ '[' -d .git ']'
+ git clean -fdx
Reason | Error: Not supported |
---|---|
Type | BUILD_FAILURE |
Failed PR | 2 (nodejs/node#44079, nodejs/node#44048) |
Appeared | test-joyent-smartos18-x64-3 |
First CI | https://ci.nodejs.org/job/node-test-pull-request/45782/ |
Last CI | https://ci.nodejs.org/job/node-test-pull-request/45794/ |
Example
Error: Not supported
at vm:module(0):1:1
at SourceTextModule.evaluate (internal/vm/module.js:222:32)
at embedder_main_7.js:1:328
at processTicksAndRejections (internal/process/task_queues.js:97:5)
(node:37543) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
Reason | fatal error: ld terminated with signal 9 [Killed] |
---|---|
Type | BUILD_FAILURE |
Failed PR | 2 (nodejs/node#44085, nodejs/node#44075) |
Appeared | test-digitalocean-ubuntu1804_sharedlibs_container-x64-8 |
First CI | https://ci.nodejs.org/job/node-test-pull-request/45774/ |
Last CI | https://ci.nodejs.org/job/node-test-pull-request/45776/ |
Example
fatal error: ld terminated with signal 9 [Killed]
undefined
Example
Unknown
JSTest Failure
Example
not ok 3077 parallel/test-worker-fshandles-error-on-termination
---
duration_ms: 120.143
severity: fail
exitcode: -15
stack: |-
timeout
...
Example
not ok 3079 parallel/test-worker-fshandles-open-close-on-termination
---
duration_ms: 120.118
severity: fail
exitcode: -15
stack: |-
timeout
...
Example
not ok 3344 parallel/test-vm-break-on-sigint
---
duration_ms: 120.72
severity: fail
exitcode: -15
stack: |-
timeout
...
Reason | parallel/test-worker-heap-snapshot |
---|---|
Type | JS_TEST_FAILURE |
Failed PR | 3 (nodejs/node#43521, nodejs/node#44032, nodejs/node#43904) |
Appeared | test-digitalocean-ubuntu1804_sharedlibs_container-x64-8, test-digitalocean-ubuntu1804_sharedlibs_container-x64-2, test-digitalocean-ubuntu1804_sharedlibs_container-x64-9, test-rackspace-win2012r2_vs2019-x64-4, test-rackspace-win2012r2_vs2015-x64-2 |
First CI | https://ci.nodejs.org/job/node-test-pull-request/45712/ |
Last CI | https://ci.nodejs.org/job/node-test-pull-request/45749/ |
Example
not ok 3036 parallel/test-worker-heap-snapshot
---
duration_ms: 1.7
severity: crashed
exitcode: -11
stack: |-
...
Reason | node-api/test_fatal/test |
---|---|
Type | JS_TEST_FAILURE |
Failed PR | 2 (nodejs/node#44013, nodejs/node#44079) |
Appeared | test-joyent-smartos20-x64-3 |
First CI | https://ci.nodejs.org/job/node-test-pull-request/45710/ |
Last CI | https://ci.nodejs.org/job/node-test-pull-request/45782/ |
Example
not ok 3496 node-api/test_fatal/test
---
duration_ms: 300.120
severity: fail
exitcode: -15
stack: |-
timeout
...
Reason | parallel/test-debugger-extract-function-name |
---|---|
Type | JS_TEST_FAILURE |
Failed PR | 2 (nodejs/node#44077, nodejs/node#44080) |
Appeared | test-azure_msft-win10_vs2019-x64-3, test-azure_msft-win10_vs2019-x64-4 |
First CI | https://ci.nodejs.org/job/node-test-pull-request/45765/ |
Last CI | https://ci.nodejs.org/job/node-test-pull-request/45807/ |
Example
not ok 212 parallel/test-debugger-extract-function-name
---
duration_ms: 6.689
severity: fail
exitcode: 1
stack: |-
C:\workspace\node-test-binary-windows-js-suites\node\test\common\debugger.js:84
reject(new Error([
^
Error: Timeout (5000) while waiting for /break (?:on start )?in/i; found: connecting to 127.0.0.1:9229 ...
< Debugger listening on ws://127.0.0.1:9229/c759ca02-d9b3-4188-9c22-ff97a0dae226
<
< For help, see: https://nodejs.org/en/docs/inspector
<
ok
< Debugger attached.
<
debug>
at Timeout.<anonymous> (C:\workspace\node-test-binary-windows-js-suites\node\test\common\debugger.js:84:18)
at listOnTimeout (node:internal/timers:564:17)
at process.processTimers (node:internal/timers:507:7)
Node.js v19.0.0-pre
...
Reason | parallel/test-fs-stat-date |
---|---|
Type | JS_TEST_FAILURE |
Failed PR | 2 (nodejs/node#44070, nodejs/node#44081) |
Appeared | test-requireio_mininodes-debian10-armv7l_pi2-1, test-requireio_securogroup-debian10-arm64_pi3-1 |
First CI | https://ci.nodejs.org/job/node-test-pull-request/45767/ |
Last CI | https://ci.nodejs.org/job/node-test-pull-request/45775/ |
Example
not ok 265 parallel/test-fs-stat-date
---
duration_ms: 2.373
severity: fail
exitcode: 1
stack: |-
node:internal/process/esm_loader:97
internalBinding('errors').triggerUncaughtException(
^
AssertionError [ERR_ASSERTION]: expected -40691 ± 1.0000000000000002, got 0
at closeEnough (file:///home/iojs/build/workspace/node-test-binary-arm/test/parallel/test-fs-stat-date.mjs:26:10)
at runTest (file:///home/iojs/build/workspace/node-test-binary-arm/test/parallel/test-fs-stat-date.mjs:40:3)
at async file:///home/iojs/build/workspace/node-test-binary-arm/test/parallel/test-fs-stat-date.mjs:70:5 {
generatedMessage: false,
code: 'ERR_ASSERTION',
actual: false,
expected: true,
operator: '=='
}
...
Reason | parallel/test-heapsnapshot-near-heap-limit-worker |
---|---|
Type | JS_TEST_FAILURE |
Failed PR | 2 (nodejs/node#44018, nodejs/node#44080) |
Appeared | test-rackspace-win2012r2_vs2019-x64-4, test-rackspace-win2012r2_vs2015-x64-2 |
First CI | https://ci.nodejs.org/job/node-test-pull-request/45715/ |
Last CI | https://ci.nodejs.org/job/node-test-pull-request/45791/ |
Example
not ok 321 parallel/test-heapsnapshot-near-heap-limit-worker
---
duration_ms: 4.194
severity: fail
exitcode: 1
stack: |-
Invoked NearHeapLimitCallback, processing=false, current_limit=52428800, initial_limit=52428800
max_young_gen_size=25165824, young_gen_size=0, old_gen_size=51321892, total_size=51321892
Estimated available memory=6265991168, estimated overhead=25165824
Start generating Heap.20220802.072530.7104.1.001.heapsnapshot...
Wrote snapshot to C:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.291\Heap.20220802.072530.7104.1.001.heapsnapshot
<--- Last few GCs --->
[7104:06986F70] 2494 ms: Mark-sweep (reduce) 48.9 (52.8) -> 48.9 (52.8) MB, 6.8 / 0.0 ms (average mu = 0.312, current mu = -0.155) heap profiler; GC in old space requested
<--- JS stacktrace --->
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
1: 013BBA6B v8::internal::Heap::PageFlagsAreC...
Reason | parallel/test-vm-timeout-escape-promise-2 |
---|---|
Type | JS_TEST_FAILURE |
Failed PR | 2 (nodejs/node#44098, nodejs/node#44074) |
Appeared | test-ibm-rhel7-s390x-3 |
First CI | https://ci.nodejs.org/job/node-test-pull-request/45799/ |
Last CI | https://ci.nodejs.org/job/node-test-pull-request/45801/ |
Example
not ok 3006 parallel/test-vm-timeout-escape-promise-2
---
duration_ms: 0.274
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:141:12)
at Script.runInNewContext (node:vm:146:17)
at Object.runInNewContext (node:vm:306: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:757:5)
at Function.throws (node:assert:903:24)
at Object.<anonymous> (/home/iojs/build/workspace/node-test-commit-linuxone/test/parallel/test-vm-timeout-escape-promise-2.js:26:8)
...
Reason | sequential/test-worker-prof |
---|---|
Type | JS_TEST_FAILURE |
Failed PR | 2 (nodejs/node#43904, nodejs/node#44060) |
Appeared | test-azure_msft-win10_vs2019-x64-1, test-rackspace-win2012r2_vs2019-x64-4, test-digitalocean-ubuntu1804_sharedlibs_container-x64-2 |
First CI | https://ci.nodejs.org/job/node-test-pull-request/45750/ |
Last CI | https://ci.nodejs.org/job/node-test-pull-request/45768/ |
Example
not ok 879 sequential/test-worker-prof
---
duration_ms: 2.680
severity: fail
exitcode: 1
stack: |-
node:assert:124
throw new AssertionError(obj);
^
AssertionError [ERR_ASSERTION]: child exited with non-zero status: {
status: 3221225477,
signal: null,
output: [ null, '', '' ],
pid: 10288,
stdout: '',
stderr: ''
}
at Object.<anonymous> (C:\workspace\node-test-binary-windows-js-suites\node\test\sequential\test-worker-prof.js:61:10)
at Module._compile (node:internal/modules/cjs/loader:1120:14)
at Module._extensions..js (node:internal/modules/cjs/loader:1174:10)
at Module.load (node:internal/modules/cjs/loader:998:32)
at Module._load (node:internal/modules/cjs/loader:839:12)
at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:86:12)
at node:internal/main/run_main_module:17:47 {
generatedMessage: false,
code: 'ERR_ASSERTION',
...
Progress
-
Backing channel 'JNLP4-connect connection from ... is disconnected.
(7) -
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?
(2) -
Error: Not supported
(2) -
fatal error: ld terminated with signal 9 [Killed]
(2) -
Unknown
(16) -
parallel/test-worker-fshandles-error-on-termination
(7) -
parallel/test-worker-fshandles-open-close-on-termination
(7) -
parallel/test-vm-break-on-sigint
(4) -
parallel/test-worker-heap-snapshot
(3) -
node-api/test_fatal/test
(2) -
parallel/test-debugger-extract-function-name
(2) -
parallel/test-fs-stat-date
(2) -
parallel/test-heapsnapshot-near-heap-limit-worker
(2) -
parallel/test-vm-timeout-escape-promise-2
(2) -
sequential/test-worker-prof
(2)
Metadata
Metadata
Assignees
Labels
No labels