CI Reliability 2023-08-28
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- javascript, node.js, shell
- Domain
- ci-cd, testing-qa
Research direction
Start with the listed failing tests, including test/parallel/test-child-process-exec-timeout-kill.js and test/sequential/test-cli-syntax-require.js, and review their CI logs on the named platforms. The work is done when the reported failures are understood and the affected CI tests pass reliably across those environments.
Written by the indexing model from the issue text.
Description
Failures in node-test-pull-request/53486 to node-test-pull-request/53584 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 |
|---|---|---|---|---|---|---|
| 2023-08-28 00:12 | 0 | 0 | 20 | 3 | 77 | 0.00% |
JSTest Failure
| Reason | parallel/test-child-process-exec-timeout-kill |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 5 (https://github.com/nodejs/node/pull/49206/, https://github.com/nodejs/node/pull/49211/, https://github.com/nodejs/node/pull/49185/, https://github.com/nodejs/node/pull/48607/, https://github.com/nodejs/node/pull/49249/) |
| Appeared | test-ibm-rhel7-s390x-1 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/53512/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/53538/ |
Example
not ok 480 parallel/test-child-process-exec-timeout-kill
---
duration_ms: 0.112
severity: fail
exitcode: 1
stack: |-
[stdout]
[stderr] /home/iojs/build/workspace/node-test-commit-linuxone/test/parallel/test-child-process-exec-timeout-kill.js:17
logInTimeout(kExpiringChildRunTime);
^
TypeError: logInTimeout is not a function
at Object.<anonymous> (/home/iojs/build/workspace/node-test-commit-linuxone/test/parallel/test-child-process-exec-timeout-kill.js:17:3)
at Module._compile (node:internal/modules/cjs/loader:1198:14)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1252:10)
at Module.load (node:internal/modules/cjs/loader:1076:32)
at Function.Module._load (node:internal/modules/cjs/loader:911:12)
at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
at node:internal/main/run_main_module:22:47
node:assert:124
throw new AssertionError(obj);
^
...
| Reason | sequential/test-cpu-prof-kill |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 5 (https://github.com/nodejs/node/pull/49206/, https://github.com/nodejs/node/pull/49211/, https://github.com/nodejs/node/pull/49185/, https://github.com/nodejs/node/pull/48607/, https://github.com/nodejs/node/pull/49249/) |
| Appeared | test-ibm-rhel7-s390x-3 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/53512/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/53538/ |
Example
not ok 3616 sequential/test-cpu-prof-kill
---
duration_ms: 1.40
severity: fail
exitcode: 1
stack: |-
Dispatching message { "id": 1, "method": "Profiler.enable" }
Receive CPU profile message
{"id":1,"result":{}}
Dispatching message { "id": 2, "method": "Profiler.setSamplingInterval", "params": { "interval": 50 } }
Receive CPU profile message
{"id":2,"result":{}}
Dispatching message { "id": 3, "method": "Profiler.start" }
Receive CPU profile message
{"id":3,"result":{}}
EndStartedProfilers
V8CpuProfilerConnection::End(), ending = false
Dispatching message { "id": 4, "method": "Profiler.stop" }
Receive CPU profile message
Writing profile response (id = 4)
Written result to /home/iojs/node-tmp/.tmp.3615/CPU.20230823.062841.4659.0.001.cpuprofile
[
{
id: 1,
callFrame: {
functionName: '(root)',
scriptId: '0',
url: '',
lineNumber: -1,
columnNumber: -1
},
...
| Reason | parallel/test-crypto-dh |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 3 (https://github.com/nodejs/node/pull/49260/, https://github.com/nodejs/node/pull/49249/, https://github.com/nodejs/node/pull/48607/) |
| Appeared | test-azure_msft-win11_vs2022-arm64-6, test-azure_msft-win11_vs2022-arm64-5, test-rackspace-win2012r2_vs2015-x64-1 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/53487/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/53546/ |
Example
not ok 926 parallel/test-crypto-dh
---
duration_ms: 120223.03200
severity: fail
exitcode: 1
stack: |-
timeout
...
| Reason | parallel/test-fs-watch-recursive-symlink |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 3 (https://github.com/nodejs/node/pull/48655/, https://github.com/nodejs/node/pull/49211/, https://github.com/nodejs/node/pull/49274/) |
| Appeared | test-ibm-rhel8-s390x-4 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/53496/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/53584/ |
Example
not ok 1385 parallel/test-fs-watch-recursive-symlink
---
duration_ms: 120082.46400
severity: fail
exitcode: -15
stack: |-
timeout
...
| Reason | parallel/test-tls-ticket-cluster |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 3 (https://github.com/nodejs/node/pull/49211/, https://github.com/nodejs/node/pull/49206/, https://github.com/nodejs/node/pull/49150/) |
| Appeared | test-nearform-macos10.15-x64-3, test-azure_msft-win2022_vs2019-x64-2, test-rackspace-win2012r2_vs2015-x64-1 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/53521/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/53550/ |
Example
not ok 2829 parallel/test-tls-ticket-cluster
---
duration_ms: 571.49500
severity: fail
exitcode: 1
stack: |-
[primary] got "listening"
[primary] connecting 61762 session? false
[worker] connection reused? false
[primary] got "not-reused"
[primary] connecting 61762 session? true
[worker] connection reused? true
[primary] got "reused"
[primary] connecting 61762 session? true
[worker] connection reused? true
[primary] got "reused"
[primary] connecting 61762 session? true
[primary] got "listening"
[worker] connection reused? true
[primary] got "reused"
[primary] connecting 61762 session? true
[worker] connection reused? true
[primary] got "reused"
[primary] connecting 61762 session? true
[worker] connection reused? true
[primary] got "reused"
[primary] connecting 61762 session? true
[worker] connection reused? true
[primary] got "reused"
[primary] connecting 61762 session? true
[worker] connection reused?...
| Reason | sequential/test-cli-syntax-require |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 3 (https://github.com/nodejs/node/pull/49150/, https://github.com/nodejs/node/pull/49238/, https://github.com/nodejs/node/pull/49274/) |
| Appeared | test-ibm-ubi81_container-x64-1, test-osuosl-aix72-ppc64_be-3 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/53549/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/53584/ |
Example
not ok 3868 sequential/test-cli-syntax-require
---
duration_ms: 175.49100
severity: fail
exitcode: 1
stack: |-
node:assert:1026
throw err;
^
AssertionError [ERR_ASSERTION]: The input did not match the regular expression /^SyntaxError: \b/m. Input:
''
at ChildProcess.<anonymous> (/home/iojs/build/workspace/node-test-commit-linux-containered/test/sequential/test-cli-syntax-require.js:34:14)
at ChildProcess.<anonymous> (/home/iojs/build/workspace/node-test-commit-linux-containered/test/common/index.js:474:15)
at ChildProcess.emit (node:events:514:28)
at ChildProcess._handle.onexit (node:internal/child_process:294:12) {
generatedMessage: true,
code: 'ERR_ASSERTION',
actual: '',
expected: /^SyntaxError: \b/m,
operator: 'match'
}
Node.js v21.0.0-pre
...
| Reason | parallel/test-fs-watch-recursive-add-file |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/49249/, https://github.com/nodejs/node/pull/49185/) |
| Appeared | test-ibm-rhel8-s390x-1, test-ibm-rhel8-s390x-2 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/53509/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/53525/ |
Example
not ok 1323 parallel/test-fs-watch-recursive-add-file
---
duration_ms: 120065.05900
severity: fail
exitcode: -15
stack: |-
timeout
...
| Reason | parallel/test-fs-watch-recursive-add-file-to-existing-subfolder |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/49274/, https://github.com/nodejs/node/pull/49206/) |
| Appeared | test-ibm-rhel8-s390x-4 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/53492/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/53512/ |
Example
not ok 1240 parallel/test-fs-watch-recursive-add-file-to-existing-subfolder
---
duration_ms: 120109.35100
severity: fail
exitcode: -15
stack: |-
timeout
...
| Reason | parallel/test-fs-watch-recursive-add-file-to-new-folder |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/49211/, https://github.com/nodejs/node/pull/49206/) |
| Appeared | test-ibm-rhel8-s390x-4 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/53504/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/53512/ |
Example
not ok 1239 parallel/test-fs-watch-recursive-add-file-to-new-folder
---
duration_ms: 120097.74700
severity: fail
exitcode: -15
stack: |-
timeout
...
| Reason | parallel/test-fs-watch-recursive-add-file-with-url |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/49288/, https://github.com/nodejs/node/pull/49150/) |
| Appeared | test-ibm-rhel8-s390x-4, test-ibm-rhel8-s390x-3 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/53499/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/53558/ |
Example
not ok 1389 parallel/test-fs-watch-recursive-add-file-with-url
---
duration_ms: 120065.49800
severity: fail
exitcode: -15
stack: |-
timeout
...
| Reason | parallel/test-http-server-consumed-timeout |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/49249/, https://github.com/nodejs/node/pull/49150/) |
| Appeared | test-ibm-rhel7-s390x-1, test-ibm-rhel8-s390x-3 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/53519/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/53558/ |
Example
not ok 1499 parallel/test-http-server-consumed-timeout
---
duration_ms: 1.342
severity: fail
exitcode: 1
stack: |-
node:assert:171
throw err;
^
AssertionError [ERR_ASSERTION]: Request timeout should not fire
at IncomingMessage.<anonymous> (/home/iojs/build/workspace/node-test-commit-linuxone/test/parallel/test-http-server-consumed-timeout.js:51:14)
at IncomingMessage.emit (node:events:513:28)
at Socket.socketOnTimeout (node:_http_server:624:50)
at Socket.emit (node:events:513:28)
at Socket._onTimeout (node:net:550:8)
at listOnTimeout (node:internal/timers:559:17)
at processTimers (node:internal/timers:502:7) {
generatedMessage: false,
code: 'ERR_ASSERTION',
actual: undefined,
expected: undefined,
operator: 'fail'
}
...
| Reason | parallel/test-inspector-break-when-eval |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/49161/, https://github.com/nodejs/node/pull/49185/) |
| Appeared | test-ibm-rhel8-s390x-2, test-ibm-rhel8-s390x-1 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/53489/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/53520/ |
Example
not ok 1827 parallel/test-inspector-break-when-eval
---
duration_ms: 15617.55500
severity: fail
exitcode: 1
stack: |-
[test] Connecting to a child Node process
[test] Testing /json/list
[err] Debugger listening on ws://127.0.0.1:38537/ef948993-2de7-4904-8d9e-a330913a6852
[err] For help, see: https://nodejs.org/en/docs/inspector
[err]
[test] Setting up a debugger
[err] Debugger attached.
[err]
Timed out waiting for matching notification (Initial pause)
1
...
| Reason | parallel/test-runner-inspect |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/49274/, https://github.com/nodejs/node/pull/49249/) |
| Appeared | test-ibm-rhel8-s390x-4 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/53492/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/53538/ |
Example
not ok 3607 parallel/test-runner-inspect
---
duration_ms: 120068.88900
severity: fail
exitcode: -15
stack: |-
timeout
[test] Connecting to a child Node process
[test] Testing /json/list
[err] (node:2699187) Warning: Using the inspector with --test forces running at a concurrency of 1. Use the inspectPort option to run with concurrency
[err] (Use `node --trace-warnings ...` to show where the warning was created)
[err]
[out] TAP version 13
[out]
[err] Debugger listening on ws://127.0.0.1:40709/388ce237-645b-46c3-8e50-4195aa09025b
[err] For help, see: https://nodejs.org/en/docs/inspector
[err]
[err] Debugger attached.
[err]
[err] For help, see: https://nodejs.org/en/docs/inspector
[err]
[out] # Debugger ending on ws://127.0.0.1:40709/388ce237-645b-46c3-8e50-4195aa09025b
[out]
...
| Reason | pummel/test-heapdump-shadow-realm |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/48050/, https://github.com/nodejs/node/pull/49249/) |
| Appeared | test-digitalocean-fedora38-x64-2, test-softlayer-debian10-x64-1 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/53495/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/53501/ |
Example
not ok 3620 pummel/test-heapdump-shadow-realm
---
duration_ms: 55818.92700
severity: crashed
exitcode: -6
stack: |-
<--- Last few GCs --->
[2348528:0x74869d0] 36147 ms: Mark-Compact (reduce) 976.4 (992.8) -> 975.8 (993.3) MB, 510.25 / 0.01 ms (+ 600.2 ms in 60 steps since start of marking, biggest step 31.0 ms, walltime since start of marking 1543 ms) (average mu = 0.405, current mu = 0.[2348528:0x74869d0] 37550 ms: Mark-Compact (reduce) 977.8 (993.9) -> 977.3 (994.4) MB, 1139.33 / 0.00 ms (+ 118.3 ms in 18 steps since start of marking, biggest step 14.0 ms, walltime since start of marking 1271 ms) (average mu = 0.263, current mu = 0
<--- JS stacktrace --->
FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
1: 0xc9d530 node::Abort() [out/Release/node]
2: 0xb7d7c6 [out/Release/node]
3: 0xee72e0 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [out/Release/node]
4: 0xe...
| Reason | sequential/test-http-regr-gh-2928 |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/49206/, https://github.com/nodejs/node/pull/49211/) |
| Appeared | test-rackspace-win2012r2_vs2015-x64-1, test-rackspace-win2012r2_vs2015-x64-2 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/53512/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/53530/ |
Example
not ok 926 sequential/test-http-regr-gh-2928
---
duration_ms: 639.00300
severity: fail
exitcode: 3221226505
stack: |-
.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.
...
| Reason | sequential/test-single-executable-application-snapshot-and-code-cache |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/49221/, https://github.com/nodejs/node/pull/49155/) |
| Appeared | test-rackspace-debian10-x64-1, test-digitalocean-ubuntu1804_sharedlibs_container-x64-4 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/53543/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/53578/ |
Example
not ok 3988 sequential/test-single-executable-application-snapshot-and-code-cache
---
duration_ms: 8731.88000
severity: fail
exitcode: 1
stack: |-
warning: Can't find string offset for section name '.note'
node:assert:125
throw new AssertionError(obj);
^
AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:
+ actual - expected
+ ''
- 'Hello from snapshot'
at Object.<anonymous> (/home/iojs/build/workspace/node-test-commit-linux/test/sequential/test-single-executable-application-snapshot-and-code-cache.js:62:10)
at Module._compile (node:internal/modules/cjs/loader:1241:14)
at Module._extensions..js (node:internal/modules/cjs/loader:1295:10)
at Module.load (node:internal/modules/cjs/loader:1091:32)
at Module._load (node:internal/modules/cjs/loader:938:12)
at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:83:12)
at node:internal/main/run_main_module:23:47 {
...
| Reason | sequential/test-timers-set-interval-excludes-callback-duration |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/48919/, https://github.com/nodejs/node/pull/49274/) |
| Appeared | test-ibm-rhel7-s390x-3, test-ibm-rhel8-s390x-3 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/53490/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/53584/ |
Example
not ok 3733 sequential/test-timers-set-interval-excludes-callback-duration
---
duration_ms: 0.581
severity: fail
exitcode: 1
stack: |-
node:assert:400
throw err;
^
AssertionError [ERR_ASSERTION]: The expression evaluated to a falsy value:
assert(Date.now() - first < 100)
at Timeout._onTimeout (/home/iojs/build/workspace/node-test-commit-linuxone/test/sequential/test-timers-set-interval-excludes-callback-duration.js:17:5)
at listOnTimeout (node:internal/timers:559:17)
at processTimers (node:internal/timers:502:7) {
generatedMessage: true,
code: 'ERR_ASSERTION',
actual: false,
expected: true,
operator: '=='
}
...
| Reason | sequential/test-worker-prof |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/49274/, https://github.com/nodejs/node/pull/49150/) |
| Appeared | test-azure_msft-win2022_vs2019-x64-2, test-ibm-rhel8-s390x-4, test-nearform-macos11.0-arm64-1 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/53492/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/53548/ |
Example
not ok 941 sequential/test-worker-prof
---
duration_ms: 30228.28300
severity: fail
exitcode: 1
stack: |-
node:assert:125
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:1124:20)
at spawnSync (node:child_process:876:24)
at Object.<anonymous> (C:\workspace\node-test-binary-windows-js-suites\node\test\sequential\test-worker-prof.js:52:23)
at Module._compile (node:internal/modules/cjs/loader:1241:14)
at Module._extensions..js (node:internal/modules/cjs/loader:1295:10)
at Module.load (node:internal/modules/cjs/loader:1091:32)
at Module._load (node:internal/modules/cjs/loader:938:12)
at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:83:12)
at node:internal/main/ru...
Jenkins Failure
| Reason | Build timed out (after 60 minutes). Marking the build as failed. |
|---|---|
| Type | JENKINS_FAILURE |
| Failed PR | 7 (https://github.com/nodejs/node/pull/49161/, https://github.com/nodejs/node/pull/48050/, https://github.com/nodejs/node/pull/49249/, https://github.com/nodejs/node/pull/49274/, https://github.com/nodejs/node/pull/49185/, https://github.com/nodejs/node/pull/49103/, https://github.com/nodejs/node/pull/49150/) |
| Appeared | test-rackspace-win2022_vs2022-x64-2, test-rackspace-win2012r2_vs2019-x64-1 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/53489/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/53545/ |
Example
Build timed out (after 60 minutes). Marking the build as failed.
CCTest Failure
| Reason | C:\workspace\node-compile-windows\node\test\cctest\test_inspector_socket.cc(323): error: Value of: (!expectation.read_expected) |
|---|---|
| Type | CC_TEST_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/49279/, https://github.com/nodejs/node/pull/49150/) |
| Appeared | test-rackspace-win2022_vs2022-x64-4, test-rackspace-win2012r2_vs2019-x64-1 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/53516/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/53550/ |
Example
C:\workspace\node-compile-windows\node\test\cctest\test_inspector_socket.cc(323): error: Value of: (!expectation.read_expected)
Actual: true
Expected: false
[ FAILED ] InspectorSocketTest.HostIPv6NonRoutable (5001 ms)
Git Failure
Build Failure
Example
Failed to trigger fanned build
| Reason | fatal: '/home/iojs/.ccache/node.shared.reference' does not appear to be a git repository |
|---|---|
| Type | BUILD_FAILURE |
| Failed PR | 5 (https://github.com/nodejs/node/pull/49288/, https://github.com/nodejs/node/pull/49211/, https://github.com/nodejs/node/pull/49206/, https://github.com/nodejs/node/pull/49185/, https://github.com/nodejs/node/pull/49150/) |
| Appeared | test-equinix-ubuntu2004_container-armv7l-1, test-equinix-ubuntu2004_container-armv7l-2 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/53499/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/53551/ |
Example
fatal: '/home/iojs/.ccache/node.shared.reference' does not appear to be a git repository
fatal: Could not read from remote repository.
fatal: failed to run repack
| Reason | ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error? |
|---|---|
| Type | BUILD_FAILURE |
| Failed PR | 4 (https://github.com/nodejs/node/pull/49185/, https://github.com/nodejs/node/pull/48607/, https://github.com/nodejs/node/pull/49150/, https://github.com/nodejs/node/pull/48244/) |
| Appeared | test-equinix-ubuntu2004_sharedlibs_container-arm64-5, test-equinix-ubuntu2004_container-armv7l-1, test-equinix-ubuntu2004_container-armv7l-2, test-equinix_mnx-smartos20-x64-4, test-osuosl-aix72-ppc64_be-4, test-equinix-ubuntu1804_sharedlibs_container-arm64-5, test-equinix-ubuntu2004_sharedlibs_container-arm64-2, test-osuosl-ubuntu2004_container-armv7l-1, test-osuosl-aix72-ppc64_be-3, test-equinix-rhel8_container-arm64-1, test-equinix-ubuntu1804_sharedlibs_container-arm64-1, test-equinix-ubuntu2004_container-arm64-2 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/53531/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/53562/ |
Example
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: No files found with the specified search criteria. |
|---|---|
| Type | BUILD_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/49150/, https://github.com/nodejs/node/pull/49161/) |
| Appeared | test-rackspace-win2012r2_vs2019-x64-2, test-rackspace-win2022_vs2022-x64-4 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/53552/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/53559/ |
Example
ERROR: No files found with the specified search criteria.
1 file(s) copied.
> set DEBUG_HELPER=1
> call vcbuild.bat arm64 release msi
| Reason | fatal: bad object refs/heads/jenkins-node-test-commit-arm-fanned-44627007be7eb3934e39bdd3df7e8f2556a2cd44-binary-pi1p/cc-armv7 |
|---|---|
| Type | BUILD_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/49150/, https://github.com/nodejs/node/pull/49161/) |
| Appeared | test-rackspace-win2019_vs2019-x64-3, test-rackspace-win2012r2_vs2019-x64-1, test-rackspace-win2022_vs2022-x64-3, test-rackspace-win2022_vs2022-x64-1, test-rackspace-win2022_vs2022-x64-5 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/53552/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/53559/ |
Example
fatal: bad object refs/heads/jenkins-node-test-commit-arm-fanned-44627007be7eb3934e39bdd3df7e8f2556a2cd44-binary-pi1p/cc-armv7
fatal: bad object refs/heads/jenkins-node-test-commit-arm-fanned-44627007be7eb3934e39bdd3df7e8f2556a2cd44-binary-pi1p/cc-armv7
Progress
-
parallel/test-child-process-exec-timeout-kill(5) -
sequential/test-cpu-prof-kill(5) -
parallel/test-crypto-dh(3) -
parallel/test-fs-watch-recursive-symlink(3) -
parallel/test-tls-ticket-cluster(3) -
sequential/test-cli-syntax-require(3) -
parallel/test-fs-watch-recursive-add-file(2) -
parallel/test-fs-watch-recursive-add-file-to-existing-subfolder(2) -
parallel/test-fs-watch-recursive-add-file-to-new-folder(2) -
parallel/test-fs-watch-recursive-add-file-with-url(2) -
parallel/test-http-server-consumed-timeout(2) -
parallel/test-inspector-break-when-eval(2) -
parallel/test-runner-inspect(2) -
pummel/test-heapdump-shadow-realm(2) -
sequential/test-http-regr-gh-2928(2) -
sequential/test-single-executable-application-snapshot-and-code-cache(2) -
sequential/test-timers-set-interval-excludes-callback-duration(2) -
sequential/test-worker-prof(2) -
Build timed out (after 60 minutes). Marking the build as failed.(7) -
C:\workspace\node-compile-windows\node\test\cctest\test_inspector_socket.cc(323): error: Value of: (!expectation.read_expected)(2) -
Failed to trigger fanned build(17) -
fatal: '/home/iojs/.ccache/node.shared.reference' does not appear to be a git repository(5) -
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?(4) -
ERROR: No files found with the specified search criteria.(2) -
fatal: bad object refs/heads/jenkins-node-test-commit-arm-fanned-44627007be7eb3934e39bdd3df7e8f2556a2cd44-binary-pi1p/cc-armv7(2)
- Dominant language
- Shell
- Stars
- 57
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from nodejs/reliability
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
nodejs/reliability#1666 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
nodejs/reliability#1665 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
nodejs/reliability#1664 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
nodejs/reliability#1663 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
nodejs/reliability#1662 ·
All issues in nodejs/reliability
Similar issues
-
area: compat bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
intake mcp-intake needs-ac needs-human-review priority:medium type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Ikalus1988/MisakaNet#2019 · 2 comments ·
-
type:content-error
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
stephrobert/blog-roadmap#15 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
hust-open-atom-club/hustmirror-cli#52 · 1 comment ·