CI Reliability 2022-12-25
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 57
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
Failures in node-test-pull-request/48627 to node-test-pull-request/48724 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-25 00:13 | 2 | 6 | 25 | 4 | 63 | 6.38% |
JSTest Failure
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...
| Reason | parallel/test-child-process-cwd |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 6 (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/) |
| 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/48715/ |
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 | 6 (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/) |
| 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/48715/ |
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
...
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 | parallel/test-fs-watch-recursive |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/45914/, https://github.com/nodejs/node/pull/45826/) |
| Appeared | test-equinix-rhel8_container-arm64-2, test-orka-macos10.15-x64-2 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/48627/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/48638/ |
Example
not ok 1265 parallel/test-fs-watch-recursive
---
duration_ms: 5.601
severity: fail
exitcode: 1
stack: |-
(node:838111) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 exit listeners added to [process]. Use emitter.setMaxListeners() to increase limit
(Use `node --trace-warnings ...` to show where the warning was created)
node:internal/process/promises:289
triggerUncaughtException(err, true /* fromPromise */);
^
AssertionError [ERR_ASSERTION]: The expression evaluated to a falsy value:
assert(!process._getActiveHandles().some((handle) => handle.constructor.name === 'StatWatcher'))
at FSWatcher.<anonymous> (/home/iojs/build/workspace/node-test-commit-arm/test/parallel/test-fs-watch-recursive.js:264:5) {
generatedMessage: true,
code: 'ERR_ASSERTION',
actual: false,
expected: true,
operator: '=='
}
Node.js v20.0.0-pre
...
| 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
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 | 7 (https://github.com/nodejs/node/pull/45914/, https://github.com/nodejs/node/pull/45887/, https://github.com/nodejs/node/pull/45882/, 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/) |
| Appeared | test-orka-macos10.14-x64-2 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/48627/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/48706/ |
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
Jenkins Failure
Progress
-
pummel/test-fs-readfile-tostring-fail(10) -
parallel/test-child-process-cwd(6) -
parallel/test-child-process-exec-cwd(6) -
parallel/test-runner-reporters(6) -
parallel/test-fs-watch-recursive(2) -
pummel/test-policy-integrity-dep(2) -
Error: getWindowSize EINVAL(18) -
ERROR: No acceptable C compiler found!(7)
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.
Research direction
Start with the generated reliability report and the linked CI console output for test/parallel/test-child-process-cwd.js, test/parallel/test-child-process-exec-cwd.js, test/parallel/test-runner-reporters, and test/parallel/test-fs-watch-recursive. Compare the failures across the named platforms and reproduce them in the relevant CI jobs. Done means the reported recurring failures have an identified fix and the affected CI tests pass reliably.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js, shell
- Domain
- ci-cd, devops, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100