Repository navigation
CI Reliability 2024-04-23 #842
Copy link
Copy link
Open
Description
Failures in node-test-pull-request/58521 to node-test-pull-request/58617 that failed 2 or more 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 |
|---|---|---|---|---|---|---|
| 2024-04-23 00:08 | 3 | 6 | 6 | 9 | 76 | 6.82% |
Jenkins Failure
| Reason | Backing channel 'JNLP4-connect connection from ... is disconnected. |
|---|---|
| Type | JENKINS_FAILURE |
| Failed PR | 5 (https://github.com/nodejs/node/pull/52573/, https://github.com/nodejs/node/pull/51192/, https://github.com/nodejs/node/pull/52624/, https://github.com/nodejs/node/pull/52465/, https://github.com/nodejs/node/pull/52347/) |
| Appeared | test-rackspace-fedora32-x64-1, test-softlayer-debian12-x64-1, test-digitalocean-debian12-x64-1, test-digitalocean-debian11-x64-1 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/58557/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/58589/ |
Example
java.io.IOException: Backing channel 'JNLP4-connect connection from 119.9.51.79/119.9.51.79:54842' is disconnected.
at hudson.remoting.RemoteInvocationHandler.channelOrFail(RemoteInvocationHandler.java:215)
at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:285)
at jdk.proxy2/jdk.proxy2.$Proxy164.isAlive(Unknown Source)
at hudson.Launcher$RemoteLauncher$ProcImpl.isAlive(Launcher.java:1212)
at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:1204)
Build Failure
| Reason | error C1060: compiler is out of heap space [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_initializers.vcxproj] |
|---|---|
| Type | BUILD_FAILURE |
| Failed PR | 9 (https://github.com/nodejs/node/pull/49709/, https://github.com/nodejs/node/pull/52587/, https://github.com/nodejs/node/pull/51340/, https://github.com/nodejs/node/pull/51192/, https://github.com/nodejs/node/pull/51657/, https://github.com/nodejs/node/pull/52603/, https://github.com/nodejs/node/pull/52465/, https://github.com/nodejs/node/pull/52632/, https://github.com/nodejs/node/pull/52577/) |
| Appeared | test-rackspace-win2022_vs2022-x64-4, test-rackspace-win2022_vs2022-x64-5, test-rackspace-win2022_vs2022-x64-1, test-rackspace-win2022_vs2022-x64-2, test-rackspace-win2022_vs2022-x64-3 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/58524/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/58611/ |
Example
error C1060: compiler is out of heap space [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_initializers.vcxproj]
trusted-object-tq-csa.cc
C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.39.33519\include\tuple(47,90): fatal error C1060: compiler is out of heap space [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_initializers.vcxproj]
promise-tq-csa.cc
C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.39.33519\include\tuple(1011,83): fatal error C1060: compiler is out of heap space [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_initializers.vcxproj]
| Reason | ERROR: Step ‘Record fingerprints of files to track usage’ failed: no workspace for ... |
|---|---|
| Type | BUILD_FAILURE |
| Failed PR | 4 (https://github.com/nodejs/node/pull/52573/, https://github.com/nodejs/node/pull/52616/, https://github.com/nodejs/node/pull/51192/, https://github.com/nodejs/node/pull/52465/) |
| Appeared | test-softlayer-debian12-x64-1, test-rackspace-fedora32-x64-1, test-digitalocean-debian12-x64-1, test-digitalocean-debian11-x64-1 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/58554/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/58595/ |
Example
ERROR: Step ‘Record fingerprints of files to track usage’ failed: no workspace for node-test-commit-linux/nodes=debian12-x64 #57373
Collecting metadata...
Metadata collection done.
Notifying upstream projects of job completion
Finished: FAILURE
| Reason | fatal error: Killed signal terminated program cc1plus |
|---|---|
| Type | BUILD_FAILURE |
| Failed PR | 4 (https://github.com/nodejs/node/pull/52365/, https://github.com/nodejs/node/pull/51657/, https://github.com/nodejs/node/pull/52593/, https://github.com/nodejs/node/pull/52465/) |
| Appeared | test-rackspace-fedora32-x64-1, test-digitalocean-debian12-x64-1, test-digitalocean-alpine318_container-x64-1, test-digitalocean-rhel8_arm_cross_container-x64-1, test-digitalocean-debian11-x64-1, test-digitalocean-rhel8_arm_cross_container-x64-2 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/58527/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/58590/ |
Example
fatal error: Killed signal terminated program cc1plus
CCTest Failure
JSTest Failure
Example
not ok 1397 parallel/test-error-serdes
---
duration_ms: 120079.51800
severity: fail
exitcode: -15
stack: |-
timeout
...
Example
not ok 1494 parallel/test-fs-read-stream-concurrent-reads
---
duration_ms: 120107.57900
severity: fail
exitcode: -15
stack: |-
timeout
...
Example
not ok 3970 parallel/test-file-write-stream4
---
duration_ms: 360104.56800
severity: fail
exitcode: -15
stack: |-
timeout
...
Example
not ok 4006 benchmark/test-benchmark-crypto
---
duration_ms: 2316.12900
severity: fail
exitcode: 1
stack: |-
node:assert:126
throw new AssertionError(obj);
^
AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:
1 !== 0
at main (/home/iojs/build/workspace/node-test-commit-arm/benchmark/crypto/timingSafeEqual.js:21:10)
at /home/iojs/build/workspace/node-test-commit-arm/benchmark/common.js:54:9
at process.processTicksAndRejections (node:internal/process/task_queues:77:11) {
generatedMessage: true,
code: 'ERR_ASSERTION',
actual: 1,
expected: 0,
operator: 'strictEqual'
}
Node.js v22.0.0-pre
node:assert:126
throw new AssertionError(obj);
^
AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:
1 !== 0
at ChildProcess.<anonymous> (/home/iojs/build/workspace/node-test-commit-arm/test/common/benchmark.js:28:12)
at Chil...
Example
not ok 75 parallel/test-blob-file-backed
---
duration_ms: 175.74300
severity: fail
exitcode: 1
stack: |-
node:internal/blob:291
const error = lazyDOMException('The blob could not be read', 'NotReadableError');
^
DOMException [NotReadableError]: The blob could not be read
at BlobReader.<anonymous> (node:internal/blob:291:25)
Node.js v22.0.0-pre
...
Example
not ok 3613 parallel/test-stream-readable-unpipe-resume
---
duration_ms: 120027.40100
severity: fail
exitcode: -15
stack: |-
timeout
...
| Reason | parallel/test-net-write-fully-async-buffer |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 3 (https://github.com/nodejs/node/pull/52505/, https://github.com/nodejs/node/pull/52465/, https://github.com/nodejs/node/pull/52108/) |
| Appeared | test-equinix-ubuntu2004_sharedlibs_container-arm64-4, test-equinix-debian11_container-armv7l-1, test-equinix-ubuntu2004_container-armv7l-2, test-equinix-ubuntu2004_container-arm64-2 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/58530/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/58592/ |
Example
not ok 3902 parallel/test-net-write-fully-async-buffer
---
duration_ms: 360117.23700
severity: fail
exitcode: -15
stack: |-
timeout
...
| Reason | parallel/test-performance-function |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 3 (https://github.com/nodejs/node/pull/51340/, https://github.com/nodejs/node/pull/52616/, https://github.com/nodejs/node/pull/52465/) |
| Appeared | test-ibm-rhel8-x64-1, undefined |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/58552/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/58572/ |
Example
not ok 2376 parallel/test-performance-function
---
duration_ms: 245.76500
severity: fail
exitcode: 1
stack: |-
node:internal/histogram:291
validateInteger(val, 'val', 1);
^
RangeError [ERR_OUT_OF_RANGE]: The value of "val" is out of range. It must be >= 1 && <= 9007199254740991. Received 0
at RecordableHistogram.record (node:internal/histogram:291:5)
at processComplete (node:internal/perf/timerify:40:15)
at timerified m (node:internal/perf/timerify:87:5)
at /home/iojs/build/workspace/node-test-commit-linux/test/parallel/test-performance-function.js:103:5 {
code: 'ERR_OUT_OF_RANGE'
}
Node.js v22.0.0-pre
...
| Reason | sequential/test-perf-hooks |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/51050/, https://github.com/nodejs/node/pull/52638/) |
| Appeared | test-orka-macos11-x64-1, test-digitalocean-ubuntu2204_sharedlibs_container-x64-6 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/58528/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/58602/ |
Example
not ok 4133 sequential/test-perf-hooks
---
duration_ms: 1618.23700
severity: fail
exitcode: 1
stack: |-
check initial nodeTiming
{
"name": "node",
"entryType": "node",
"startTime": 0,
"duration": 83.701415,
"nodeStart": 5.219475984573364,
"v8Start": 11.280551016330719,
"environment": 18.309584975242615,
"loopStart": -1,
"loopExit": -1,
"bootstrapComplete": 31.161038994789124,
"idleTime": 0
}
Start timer
Check nodeTiming in timer
{
"name": "node",
"entryType": "node",
"startTime": 0,
"duration": 1234.517341,
"nodeStart": 5.219475984573364,
"v8Start": 11.280551016330719,
"environment": 18.309584975242615,
"loopStart": 85.32227700948715,
"loopExit": -1,
"bootstrapComplete": 31.161038994789124,
"idleTime": 1145.274724
}
Check nodeTiming in process exit event
{
"name": "node",
"entryType": "node",
"startTime": 0,
"d...
Progress
-
Backing channel 'JNLP4-connect connection from ... is disconnected.(5) -
error C1060: compiler is out of heap space [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_initializers.vcxproj](9) -
ERROR: Step ‘Record fingerprints of files to track usage’ failed: no workspace for ...(4) -
fatal error: Killed signal terminated program cc1plus(4) -
parallel/test-error-serdes(26) -
parallel/test-fs-read-stream-concurrent-reads(11) -
parallel/test-file-write-stream4(6) -
benchmark/test-benchmark-crypto(5) -
parallel/test-blob-file-backed(4) -
parallel/test-stream-readable-unpipe-resume(4) -
parallel/test-net-write-fully-async-buffer(3) -
parallel/test-performance-function(3) -
sequential/test-perf-hooks(2)
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels
Activity