CI Reliability 2022-08-07
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 15/100
- Issue 类型
- 缺陷
- 描述清晰度
- 需要澄清
- 活跃度
- 停滞
- 技术栈
- shell
- 领域
- ci-cd, devops, testing-qa
调研方向
这是一份生成的可靠性报告,涵盖 Jenkins 失败、构建失败和 JavaScript 测试失败。请从链接的 CI job 示例以及列出的测试开始,例如 parallel/test-diagnostics-channel-net 和 parallel/test-debugger-extract-function-name。要视为完成,需要隔离出一个当前且可复现的失败,并确定修复方案;此处未指定任何源文件或测试更改。
由索引模型根据 Issue 内容生成。
描述
Failures in node-test-pull-request/45789 to node-test-pull-request/45888 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-07 00:17 | 0 | 9 | 31 | 5 | 55 | 9.47% |
Jenkins Failure
| Reason | Backing channel 'JNLP4-connect connection from ... is disconnected. |
|---|---|
| Type | JENKINS_FAILURE |
| Failed PR | 6 (https://github.com/nodejs/node/pull/38905/, https://github.com/nodejs/node/pull/44110/, https://github.com/nodejs/node/pull/44129/, https://github.com/nodejs/node/pull/44102/, https://github.com/nodejs/node/pull/44091/, https://github.com/nodejs/node/pull/44100/) |
| Appeared | test-digitalocean-freebsd12-x64-2, test-nearform-macos10.15-x64-3, test-nearform-macos11.0-arm64-1, test-azure_msft-win10_vs2019-x64-1 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/45797/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/45875/ |
Example
java.io.IOException: Backing channel 'JNLP4-connect connection from 107.170.28.213/107.170.28.213:43882' 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 workspace for ... |
|---|---|
| Type | BUILD_FAILURE |
| Failed PR | 4 (https://github.com/nodejs/node/pull/44080/, https://github.com/nodejs/node/pull/44129/, https://github.com/nodejs/node/pull/44132/, https://github.com/nodejs/node/pull/44102/) |
| Appeared | test-nearform-macos10.15-x64-3, test-digitalocean-freebsd12-x64-2 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/45812/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/45842/ |
Example
ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for node-test-commit-osx/nodes=osx1015 #46644
Collecting metadata...
Metadata collection done.
Notifying upstream projects of job completion
Finished: FAILURE
| Reason | ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error? |
|---|---|
| Type | BUILD_FAILURE |
| Failed PR | 3 (https://github.com/nodejs/node/pull/44080/, https://github.com/nodejs/node/pull/44132/, https://github.com/nodejs/node/pull/44074/) |
| Appeared | test-equinix-debian10_container-armv7l-2, test-equinix-ubuntu2004_container-armv7l-1, test-equinix-debian10_container-armv7l-1 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/45805/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/45888/ |
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/jenkins11862886316364044763.sh
+ '[' -d .git ']'
+ git clean -fdx
undefined
Example
Unknown
JSTest Failure
Example
not ok 652 parallel/test-diagnostics-channel-net
---
duration_ms: 0.268
severity: fail
exitcode: 1
stack: |-
Mismatched <anonymous> function calls. Expected exactly 1, actual 0.
...
| Reason | parallel/test-heapsnapshot-near-heap-limit-worker |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 5 (https://github.com/nodejs/node/pull/44080/, https://github.com/nodejs/node/pull/44090/, https://github.com/nodejs/node/pull/44110/, https://github.com/nodejs/node/pull/44109/, https://github.com/nodejs/node/pull/44102/) |
| Appeared | test-rackspace-win2012r2_vs2019-x64-4, test-rackspace-win2012r2_vs2019-x64-6, test-rackspace-win2012r2_vs2019-x64-5 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/45791/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/45842/ |
Example
not ok 328 parallel/test-heapsnapshot-near-heap-limit-worker
---
duration_ms: 4.506
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=51250696, total_size=51250696
Estimated available memory=6149320704, estimated overhead=25165824
Start generating Heap.20220804.165945.4268.1.001.heapsnapshot...
Wrote snapshot to C:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.291\Heap.20220804.165945.4268.1.001.heapsnapshot
<--- Last few GCs --->
[4268:06503560] 2753 ms: Mark-sweep (reduce) 48.8 (52.8) -> 48.8 (52.8) MB, 6.2 / 0.0 ms (average mu = 0.333, current mu = -0.150) 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: 012FEB2B v8::internal::Heap::PageFlagsAreC...
| Reason | parallel/test-debugger-extract-function-name |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 3 (https://github.com/nodejs/node/pull/44080/, https://github.com/nodejs/node/pull/44101/, https://github.com/nodejs/node/pull/44140/) |
| Appeared | test-azure_msft-win10_vs2019-x64-3, test-azure_msft-win10_vs2019-x64-1 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/45807/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/45861/ |
Example
not ok 214 parallel/test-debugger-extract-function-name
---
duration_ms: 6.690
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: < Debugger listening on ws://127.0.0.1:9229/e480ce69-73fd-48ce-bcb5-7b82c4320235
< For help, see: https://nodejs.org/en/docs/inspector
<
connecting to 127.0.0.1:9229 ...
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
...
Example
not ok 2975 parallel/test-vm-break-on-sigint
---
duration_ms: 120.90
severity: fail
exitcode: -15
stack: |-
timeout
...
| Reason | parallel/test-vm-timeout-escape-promise-2 |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 3 (https://github.com/nodejs/node/pull/44098/, https://github.com/nodejs/node/pull/44074/, https://github.com/nodejs/node/pull/44102/) |
| Appeared | test-azure_msft-win10_vs2019-x64-1, 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/45847/ |
Example
not ok 748 parallel/test-vm-timeout-escape-promise-2
---
duration_ms: 0.299
severity: fail
exitcode: 1
stack: |-
C:\workspace\node-test-binary-windows-js-suites\node\test\parallel\test-vm-timeout-escape-promise-2.js:20
throw new Error(
^
Error: escaped timeout at 100 milliseconds!
at loop (C:\workspace\node-test-binary-windows-js-suites\node\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 (C:\workspace\node-test-binary-windows-js-suites\node\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> (C:\workspace\node-test-binary-windows-js-suites\node\test\parallel\test-vm-timeout-escape-promise-2.js:26:8)
...
| Reason | parallel/test-worker-fshandles-open-close-on-termination |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 3 (https://github.com/nodejs/node/pull/44069/, https://github.com/nodejs/node/pull/44101/, https://github.com/nodejs/node/pull/44129/) |
| Appeared | test-digitalocean-ubuntu1804_sharedlibs_container-x64-2, test-rackspace-win2012r2_vs2019-x64-4, test-digitalocean-ubuntu1804_sharedlibs_container-x64-9 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/45798/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/45868/ |
Example
not ok 2980 parallel/test-worker-fshandles-open-close-on-termination
---
duration_ms: 120.105
severity: fail
exitcode: -15
stack: |-
timeout
...
| Reason | parallel/test-crypto-secure-heap |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/44090/, https://github.com/nodejs/node/pull/44129/) |
| Appeared | test-digitalocean-freebsd12-x64-2 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/45813/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/45834/ |
Example
not ok 451 parallel/test-crypto-secure-heap
---
duration_ms: 0.407
severity: fail
exitcode: 1
stack: |-
node:assert:1027
throw err;
^
AssertionError [ERR_ASSERTION]: The input did not match the regular expression /--secure-heap must be a power of 2/. Input:
''
at ChildProcess.<anonymous> (/usr/home/iojs/build/workspace/node-test-commit-freebsd/nodes/freebsd12-x64/test/parallel/test-crypto-secure-heap.js:71:12)
at ChildProcess.<anonymous> (/usr/home/iojs/build/workspace/node-test-commit-freebsd/nodes/freebsd12-x64/test/common/index.js:420:15)
at ChildProcess.emit (node:events:513:28)
at Process.ChildProcess._handle.onexit (node:internal/child_process:291:12) {
generatedMessage: true,
code: 'ERR_ASSERTION',
actual: '',
expected: /--secure-heap must be a power of 2/,
operator: 'match'
}
...
| Reason | parallel/test-worker-fshandles-error-on-termination |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/44069/, https://github.com/nodejs/node/pull/44129/) |
| Appeared | test-digitalocean-ubuntu1804_sharedlibs_container-x64-2, test-digitalocean-ubuntu1804_sharedlibs_container-x64-3, test-digitalocean-ubuntu1804_sharedlibs_container-x64-9 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/45798/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/45868/ |
Example
not ok 2979 parallel/test-worker-fshandles-error-on-termination
---
duration_ms: 120.37
severity: fail
exitcode: -15
stack: |-
timeout
...
| Reason | parallel/test-worker-heap-snapshot |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/44080/, https://github.com/nodejs/node/pull/44139/) |
| Appeared | test-joyent-smartos20-x64-3, test-rackspace-win2012r2_vs2017-x64-4 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/45815/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/45852/ |
Example
not ok 3188 parallel/test-worker-heap-snapshot
---
duration_ms: 1.253
severity: crashed
exitcode: -6
stack: |-
FATAL ERROR: HandleScope::HandleScope Entering the V8 API without proper locking in place
1: 13c3bde node::Abort() [/home/iojs/build/workspace/node-test-commit-smartos/nodes/smartos20-64/out/Release/node]
2: 13c6fbf node::FatalError(char const*, char const*) [/home/iojs/build/workspace/node-test-commit-smartos/nodes/smartos20-64/out/Release/node]
3: 15e599a v8::Utils::ReportApiFailure(char const*, char const*) [/home/iojs/build/workspace/node-test-commit-smartos/nodes/smartos20-64/out/Release/node]
4: 15e711c v8::HandleScope::HandleScope(v8::Isolate*) [/home/iojs/build/workspace/node-test-commit-smartos/nodes/smartos20-64/out/Release/node]
5: 133f074 node::BaseObject::~BaseObject() [/home/iojs/build/workspace/node-test-commit-smartos/nodes/smartos20-64/out/Release/node]
6: 130c321 node::AsyncWrap::~AsyncWrap() [/home/iojs/build/workspace/node-test-commit-sm...
Progress
-
Backing channel 'JNLP4-connect connection from ... is disconnected.(6) -
ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for ...(4) -
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?(3) -
Unknown(12) -
parallel/test-diagnostics-channel-net(13) -
parallel/test-heapsnapshot-near-heap-limit-worker(5) -
parallel/test-debugger-extract-function-name(3) -
parallel/test-vm-break-on-sigint(3) -
parallel/test-vm-timeout-escape-promise-2(3) -
parallel/test-worker-fshandles-open-close-on-termination(3) -
parallel/test-crypto-secure-heap(2) -
parallel/test-worker-fshandles-error-on-termination(2) -
parallel/test-worker-heap-snapshot(2)
- 主要语言
- Shell
- 星标
- 57
- 派生
- 20
- PR 合并指标
- 30 天内没有已合并 PR
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
nodejs/reliability 的其他 Issue
-
难度 4/5 3-5 天 新手友好度 35/100
nodejs/reliability#1666 ·
-
难度 4/5 3-5 天 新手友好度 25/100
nodejs/reliability#1665 ·
-
难度 5/5 一周以上 新手友好度 25/100
nodejs/reliability#1664 ·
-
难度 4/5 3-5 天 新手友好度 35/100
nodejs/reliability#1663 ·
-
难度 4/5 3-5 天 新手友好度 35/100
nodejs/reliability#1662 ·
查看 nodejs/reliability 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 68/100
community-scripts/ProxmoxVE#17396 · 1 条评论 ·
-
难度 2/5 1-3 小时 新手友好度 68/100
mattpocock/skills#1099 ·
-
package-update
难度 2/5 1-3 小时 新手友好度 78/100
oSoWoSo/vOid_Community_repOsitory#144 · 1 条评论 ·
-
难度 2/5 1-3 小时 新手友好度 88/100
-
help wanted new command
难度 2/5 1-3 小时 新手友好度 72/100
tldr-pages/tldr#24151 ·