CI Reliability 2022-12-28
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 18/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- cpp, javascript, shell
- Domain
- build-system, ci-cd, testing-qa
Research direction
Start by reviewing the listed CI jobs and failure examples, especially test/parallel/test-child-process-cwd.js, test/parallel/test-child-process-exec-cwd.js, test/pummel/test-fs-readfile-tostring-fail.js, test/parallel/test-runner-reporters, test/cctest/test_inspector_socket.cc, and the SmartOS build logs. Reproduce the failures on the named platforms and determine which failures still occur; done requires an agreed scope and consistently passing CI.
Written by the indexing model from the issue text.
Description
Failures in node-test-pull-request/48644 to node-test-pull-request/48742 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-12-28 00:12 | 0 | 4 | 31 | 5 | 60 | 4.21% |
JSTest Failure
Example
not ok 102 parallel/test-child-process-cwd
---
duration_ms: 0.430
severity: fail
exitcode: 1
stack: |-
node:assert:124
throw new AssertionError(obj);
^
AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:
+ actual - expected
+ 'C:\\Windows'
- 'C:\\WINDOWS'
^
at ChildProcess.<anonymous> (c:\workspace\node-test-binary-windows-js-suites\node\test\parallel\test-child-process-cwd.js:56:26)
at ChildProcess.<anonymous> (c:\workspace\node-test-binary-windows-js-suites\node\test\common\index.js:448:15)
at ChildProcess.emit (node:events:519:28)
at maybeClose (node:internal/child_process:1098:16)
at ChildProcess._handle.onexit (node:internal/child_process:304:5) {
generatedMessage: true,
code: 'ERR_ASSERTION',
actual: 'C:\\Windows',
expected: 'C:\\WINDOWS',
operator: 'strictEqual'
}
Node.js v20.0.0-pre
...
| Reason | parallel/test-child-process-exec-cwd |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 8 (https://github.com/nodejs/node/pull/45258/, https://github.com/nodejs/node/pull/45750/, https://github.com/nodejs/node/pull/41439/, https://github.com/nodejs/node/pull/45923/, https://github.com/nodejs/node/pull/45038/, https://github.com/nodejs/node/pull/44004/, https://github.com/nodejs/node/pull/45960/, https://github.com/nodejs/node/pull/45966/) |
| Appeared | test-nearform_arm-win10_vs2019-arm64-1 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/48651/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/48738/ |
Example
not ok 103 parallel/test-child-process-exec-cwd
---
duration_ms: 0.498
severity: fail
exitcode: 1
stack: |-
node:assert:400
throw err;
^
AssertionError [ERR_ASSERTION]: The expression evaluated to a falsy value:
assert(stdout.startsWith(dir))
at c:\workspace\node-test-binary-windows-js-suites\node\test\parallel\test-child-process-exec-cwd.js:38:3
at c:\workspace\node-test-binary-windows-js-suites\node\test\common\index.js:413:17
at c:\workspace\node-test-binary-windows-js-suites\node\test\common\index.js:448:15
at ChildProcess.exithandler (node:child_process:411:7)
at ChildProcess.emit (node:events:519:28)
at maybeClose (node:internal/child_process:1098:16)
at ChildProcess._handle.onexit (node:internal/child_process:304:5) {
generatedMessage: true,
code: 'ERR_ASSERTION',
actual: false,
expected: true,
operator: '=='
}
Node.js v20.0.0-pre
...
| Reason | pummel/test-fs-readfile-tostring-fail |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 8 (https://github.com/nodejs/node/pull/45886/, https://github.com/nodejs/node/pull/45887/, https://github.com/nodejs/node/pull/45912/, https://github.com/nodejs/node/pull/45885/, https://github.com/nodejs/node/pull/45258/, https://github.com/nodejs/node/pull/45878/, https://github.com/nodejs/node/pull/45914/, https://github.com/nodejs/node/pull/45923/) |
| Appeared | test-digitalocean-freebsd12-x64-1 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/48647/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/48658/ |
Example
not ok 3451 pummel/test-fs-readfile-tostring-fail
---
duration_ms: 50.674
severity: fail
exitcode: 7
stack: |-
/usr/home/iojs/build/workspace/node-test-commit-freebsd/nodes/freebsd12-x64/test/pummel/test-fs-readfile-tostring-fail.js:73
throw err;
^
AssertionError [ERR_ASSERTION]: 275906560 bytes written (expected 539555154 bytes).
at WriteStream.<anonymous> (/usr/home/iojs/build/workspace/node-test-commit-freebsd/nodes/freebsd12-x64/test/pummel/test-fs-readfile-tostring-fail.js:37:10)
at WriteStream.<anonymous> (/usr/home/iojs/build/workspace/node-test-commit-freebsd/nodes/freebsd12-x64/test/common/index.js:448:15)
at WriteStream.emit (node:events:519:28)
at finish (node:internal/streams/writable:750:10)
at finishMaybe (node:internal/streams/writable:735:9)
at afterWrite (node:internal/streams/writable:507:3)
at onwrite (node:internal/streams/writable:480:7)
at node:internal/fs/streams:443:5
at FSReqCall...
Example
not ok 615 parallel/test-runner-reporters
---
duration_ms: 5.917
severity: fail
exitcode: 1
stack: |-
TAP version 13
# Subtest: node:test reporters
# Subtest: should default to outputing TAP to stdout
ok 1 - should default to outputing TAP to stdout
---
duration_ms: 5328.1972
...
| Reason | pummel/test-policy-integrity-dep |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/45038/, https://github.com/nodejs/node/pull/45947/) |
| Appeared | test-macstadium-macos11.0-arm64-3 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/48717/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/48720/ |
Example
not ok 3484 pummel/test-policy-integrity-dep
---
duration_ms: 1.326
severity: crashed
exitcode: -10
stack: |-
...
CCTest Failure
| Reason | ../test/cctest/test_inspector_socket.cc:323: Failure |
|---|---|
| Type | CC_TEST_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/45847/, https://github.com/nodejs/node/pull/45912/) |
| Appeared | test-digitalocean-alpine312_container-x64-2 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/48723/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/48730/ |
Example
../test/cctest/test_inspector_socket.cc:323: Failure
Value of: (!expectation.read_expected)
Actual: true
Expected: false
[ FAILED ] InspectorSocketTest.HostIPv6NonRoutable (5000 ms)
Build Failure
Example
Error: getWindowSize EINVAL
outline = at WriteStream._refreshSize (tty.js:133:31)
outline = at process.<anonymous> (internal/bootstrap/switches/is_main_thread.js:127:41)
outline = at process.emit (events.js:400:28)
outline = Emitted 'error' event on WriteStream instance at:
outline = at WriteStream._refreshSize (tty.js:133:10)
| Reason | ERROR: No acceptable C compiler found! |
|---|---|
| Type | BUILD_FAILURE |
| Failed PR | 6 (https://github.com/nodejs/node/pull/45886/, https://github.com/nodejs/node/pull/45936/, https://github.com/nodejs/node/pull/44004/, https://github.com/nodejs/node/pull/45038/, https://github.com/nodejs/node/pull/45960/, https://github.com/nodejs/node/pull/45970/) |
| Appeared | test-orka-macos10.14-x64-2 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/48647/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/48734/ |
Example
ERROR: No acceptable C compiler found!
Please make sure you have a C compiler installed on your system and/or
consider adjusting the CC environment variable if you installed
it in a non-standard prefix.
make: *** [build-ci] Error 1
Progress
-
parallel/test-child-process-cwd(8) -
parallel/test-child-process-exec-cwd(8) -
pummel/test-fs-readfile-tostring-fail(8) -
parallel/test-runner-reporters(4) -
pummel/test-policy-integrity-dep(2) -
../test/cctest/test_inspector_socket.cc:323: Failure(2) -
Error: getWindowSize EINVAL(19) -
ERROR: No acceptable C compiler found!(6)
- 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
-
Update Vish to 1.1.5 Openpackage-update
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
oSoWoSo/vOid_Community_repOsitory#144 · 1 comment ·
-
help wanted new command
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
tldr-pages/tldr#24151 ·
-
PacReq: Rune IDE Openpackage request
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
pacstall/pacstall-programs#9402 ·
-
[BUG] ci: the first prefetch-images.sh call runs before shard.txt exists, so it is always a no-op Openbug github-actions
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
update-request
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
msys2/MINGW-packages#31768 ·