CI Reliability 2021-10-19
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 25/100
- Tipo di issue
- Bug
- Chiarezza
- Da chiarire
- Stato di attività
- Ferma
- Stack tecnologico
- javascript, nodejs, shell
- Ambito
- ci-cd, devops, testing-qa
Direzione di ricerca
Inizia con gli esempi collegati della console CI e i test indicati: wpt/test-user-timing, parallel/test-http2-pipe-named-pipe, parallel/test-repl-sigint-nested-eval, parallel/test-crypto-dh e sequential/test-net-connect-econnrefused. Confronta i relativi fallimenti sulle piattaforme elencate e riproducili nei job CI corrispondenti. Il lavoro è completato quando i fallimenti segnalati sono compresi e i test interessati passano in modo affidabile.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Failures in node-test-pull-request/40256 to node-test-pull-request/40353 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 |
|---|---|---|---|---|---|---|
| 2021-10-19 00:02 | 1 | 19 | 2 | 5 | 73 | 20.21% |
JSTest Failure
Example
not ok 836 wpt/test-user-timing
---
duration_ms: 9.133
severity: fail
exitcode: 1
stack: |-
---- idlharness.any.js ----
[SKIPPED] idlharness cannot recognize Node.js environment
---- invoke_with_timing_attributes.worker.js ----
[SKIPPED] importScripts not supported
---- performance-measure-invalid.worker.js ----
[SKIPPED] importScripts not supported
---- clear_all_marks.any.js ----
[PASS] Clearing all marks remove all of them.
---- buffered-flag.any.js ----
[PASS] PerformanceObserver with buffered flag sees previous marks
---- buffered-flag.any.js ----
[PASS] PerformanceObserver with buffered flag sees previous measures
---- case-sensitivity.any.js ----
[PASS] getEntriesByType values are case sensitive
---- clear_all_measures.any.js ----
[PASS] Clearing all marks remove all of them.
---- clear_non_existent_mark.any.js ----
[PASS] Clearing a non-existent mark doesn't affect existing marks
---- clear_one_mark.any.js ----
[...
Example
not ok 1322 parallel/test-http2-pipe-named-pipe
---
duration_ms: 0.67
severity: fail
exitcode: 1
stack: |-
node:assert:123
throw new AssertionError(obj);
^
AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:
139837 !== 139244
at WriteStream.<anonymous> (/Users/iojs/build/workspace/node-test-commit-osx-arm/nodes/osx11/test/parallel/test-http2-pipe-named-pipe.js:26:12)
at WriteStream.emit (node:events:402:35)
at finish (node:internal/streams/writable:751:10)
at processTicksAndRejections (node:internal/process/task_queues:83:21) {
generatedMessage: true,
code: 'ERR_ASSERTION',
actual: 139837,
expected: 139244,
operator: 'strictEqual'
}
Node.js v17.0.0-pre
...
Example
not ok 2092 parallel/test-repl-sigint-nested-eval
---
duration_ms: 0.614
severity: fail
exitcode: 1
stack: |-
Stacktrace:
ptr1=0x268fbe141d49
ptr2=(nil)
ptr3=(nil)
ptr4=(nil)
failure_message_object=0x7ffe11c78140
==== JS stack trace =========================================
0: ExitFrame [pc: 0x7f1ff7eb2f79]
1: StubFrame [pc: 0x7f1ff7f3db9d]
Security context: 0x13d38851d901 <JSGlobalObject>
2: _fatalException [0xfef3a6b369] [node:internal/process/execution:151] [bytecode=0xfef3a79639 offset=13](this=0x03c158502ad1 <process map = 0x2173ab0cd9a1>,0x268fbe141d49 <Odd Oddball: termination_exception>,0x268fbe141769 <false>)
3: InternalFrame [pc: 0x7f1ff7e401db]
4: EntryFrame [pc: 0x7f1ff7e3ff03]
5: builtin exit frame: evaluate(this=0x37ecd77fc399 <ModuleWrap map = 0x2173ab0e41e9>,0x37ecd77fc399 <ModuleWrap map = 0x2173ab0e41e9>,-1,0x268fbe141769 <false>)
6: getESMFacade [0x3c158518c21]...
Example
not ok 223 parallel/test-crypto-dh
---
duration_ms: 240.177
severity: fail
exitcode: -15
stack: |-
timeout
...
Example
not ok 3502 sequential/test-net-connect-econnrefused
---
duration_ms: 120.106
severity: fail
exitcode: -15
stack: |-
timeout
pending 50 rounds 1
pending 49 rounds 1
pending 48 rounds 1
pending 47 rounds 1
pending 46 rounds 1
pending 45 rounds 1
pending 44 rounds 1
pending 43 rounds 1
pending 42 rounds 1
pending 41 rounds 1
pending 40 rounds 1
pending 39 rounds 1
pending 38 rounds 1
pending 37 rounds 1
pending 36 rounds 1
pending 35 rounds 1
pending 34 rounds 1
pending 33 rounds 1
pending 32 rounds 1
pending 31 rounds 1
pending 30 rounds 1
pending 29 rounds 1
pending 28 rounds 1
pending 27 rounds 1
pending 26 rounds 1
pending 25 rounds 1
pending 24 rounds 1
pending 23 rounds 1
pending 22 rounds 1
pending 21 rounds 1
pending 20 rounds 1
pending 19 rounds 1
pending 18 rounds 1
pending 17 rounds 1
pending 16 rounds 1
pending 15 rounds 1
pending 14 rounds...
| Reason | parallel/test-inspector-connect-main-thread |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 5 (https://github.com/nodejs/node/pull/40432/, https://github.com/nodejs/node/pull/40379/, https://github.com/nodejs/node/pull/40119/, https://github.com/nodejs/node/pull/40451/, https://github.com/nodejs/node/pull/40450/) |
| Appeared | test-rackspace-ubuntu1604-x64-2 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/40280/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/40298/ |
Example
not ok 1493 parallel/test-inspector-connect-main-thread
---
duration_ms: 0.715
severity: crashed
exitcode: -6
stack: |-
Skip child is done
Message for a test
Worker is done
Message NodeWorker.enable was sent
Message Debugger.enable was sent
Message Runtime.enable was sent
Message Debugger.setBreakpointByUrl was sent
Message Debugger.evaluateOnCallFrame was sent
Message Debugger.resume was sent
...
| Reason | node-api/test_threadsafe_function/test |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 4 (https://github.com/nodejs/node/pull/40094/, https://github.com/nodejs/node/pull/40357/, https://github.com/nodejs/node/pull/40405/, https://github.com/nodejs/node/pull/40450/) |
| Appeared | test-equinix-centos7_container-arm64-1, test-equinix-ubuntu2004_container-arm64-1, test-equinix-ubuntu2004_sharedlibs_container-arm64-1, test-equinix-ubuntu2004_sharedlibs_container-arm64-3 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/40258/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/40298/ |
Example
not ok 3280 node-api/test_threadsafe_function/test
---
duration_ms: 240.94
severity: fail
exitcode: -15
stack: |-
timeout
...
| Reason | parallel/test-child-process-fork-closed-channel-segfault |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 4 (https://github.com/nodejs/node/pull/40432/, https://github.com/nodejs/node/pull/40400/, https://github.com/nodejs/node/pull/39924/, https://github.com/nodejs/node/pull/40416/) |
| Appeared | test-requireio_piccoloaiutante-debian10-arm64_pi3-1, test-requireio_williamkapke-debian10-arm64_pi3-2 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/40268/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/40324/ |
Example
not ok 98 parallel/test-child-process-fork-closed-channel-segfault
---
duration_ms: 3.502
severity: fail
exitcode: 1
stack: |-
/home/iojs/build/workspace/node-test-binary-arm/test/parallel/test-child-process-fork-closed-channel-segfault.js:83
throw err;
^
Error: write EPIPE
at ChildProcess.target._send (node:internal/child_process:844:20)
at ChildProcess.<anonymous> (node:internal/child_process:665:16)
at ChildProcess.emit (node:events:402:35)
at emit (node:internal/child_process:915:12)
at processTicksAndRejections (node:internal/process/task_queues:84:21) {
errno: -32,
code: 'EPIPE',
syscall: 'write'
}
Node.js v17.0.0-pre
...
| Reason | parallel/test-crypto-secure-heap |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 4 (https://github.com/nodejs/node/pull/40434/, https://github.com/nodejs/node/pull/40457/, https://github.com/nodejs/node/pull/40119/, https://github.com/nodejs/node/pull/40478/) |
| Appeared | test-requireio_ceejbot-debian10-armv7l_pi2-1, test-requireio_rvagg-debian10-armv7l_pi2-1, test-requireio_mininodes-debian10-armv7l_pi2-1 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/40265/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/40344/ |
Example
not ok 235 parallel/test-crypto-secure-heap
---
duration_ms: 240.95
severity: fail
exitcode: -15
stack: |-
timeout
...
| Reason | parallel/test-http2-cancel-while-client-reading |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 3 (https://github.com/nodejs/node/pull/40434/, https://github.com/nodejs/node/pull/40422/, https://github.com/nodejs/node/pull/40481/) |
| Appeared | test-orka-macos10.15-x64-2, test-orka-macos11-x64-2 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/40265/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/40337/ |
Example
not ok 1192 parallel/test-http2-cancel-while-client-reading
---
duration_ms: 0.443
severity: fail
exitcode: 1
stack: |-
node:events:368
throw er; // Unhandled 'error' event
^
Error: read ECONNRESET
at TLSWrap.onStreamRead (node:internal/stream_base_commons:220:20)
Emitted 'error' event on ServerHttp2Stream instance at:
at emitErrorNT (node:internal/streams/destroy:164:8)
at emitErrorCloseNT (node:internal/streams/destroy:129:3)
at processTicksAndRejections (node:internal/process/task_queues:83:21) {
errno: -54,
code: 'ECONNRESET',
syscall: 'read'
}
Node.js v17.0.0-pre
...
| Reason | parallel/test-trace-events-fs-sync |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 3 (https://github.com/nodejs/node/pull/36111/, https://github.com/nodejs/node/pull/40433/, https://github.com/nodejs/node/pull/40380/) |
| Appeared | test-azure_msft-win10_vs2019-x64-1 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/40273/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/40352/ |
Example
not ok 677 parallel/test-trace-events-fs-sync
---
duration_ms: 2.505
severity: fail
exitcode: 1
stack: |-
Can't clean tmpdir: C:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.669
Files blocking: [ 'fs.txt', 'node_trace.1.log' ]
C:\workspace\node-test-binary-windows-js-suites\node\test\parallel\test-trace-events-fs-sync.js:133
throw new Error(`${tr}:\n${util.inspect(proc)}`);
^
Error: fs.sync.fstat:
{
status: 1,
signal: null,
output: [
null,
'',
'node:internal/fs/utils:344\r\n' +
' throw err;\r\n' +
' ^\r\n' +
'\r\n' +
"Error: EPERM: operation not permitted, open 'fs.txt'\r\n" +
' at Object.openSync (node:fs:585:3)\r\n' +
' at Object.writeFileSync (node:fs:2153:35)\r\n' +
' at [eval]:1:4\r\n' +
' at Script.runInThisContext (node:vm:129:12)\r\n' +
' at Object.runInThisContext (node:vm:305:38)...
| Reason | pummel/test-fs-watch-non-recursive |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 3 (https://github.com/nodejs/node/pull/40473/, https://github.com/nodejs/node/pull/40478/, https://github.com/nodejs/node/pull/40504/) |
| Appeared | test-azure_msft-win10_vs2019-x64-1, test-azure_msft-win10_vs2019-x64-3 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/40339/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/40349/ |
Example
not ok 778 pummel/test-fs-watch-non-recursive
---
duration_ms: 2.660
severity: fail
exitcode: 1
stack: |-
node:assert:171
throw err;
^
AssertionError [ERR_ASSERTION]: function should not have been called at C:\workspace\node-test-binary-windows-js-suites\node\test\pummel\test-fs-watch-non-recursive.js:43
called with arguments: 'change', 'testsubdir'
at FSWatcher.mustNotCall (C:\workspace\node-test-binary-windows-js-suites\node\test\common\index.js:472:12)
at FSWatcher.emit (node:events:390:28)
at FSEvent.FSWatcher._handle.onchange (node:internal/fs/watchers:212:12) {
generatedMessage: false,
code: 'ERR_ASSERTION',
actual: undefined,
expected: undefined,
operator: 'fail'
}
...
| Reason | sequential/test-debugger-heap-profiler |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 3 (https://github.com/nodejs/node/pull/40405/, https://github.com/nodejs/node/pull/40478/, https://github.com/nodejs/node/pull/40380/) |
| Appeared | test-digitalocean-ubuntu1804_sharedlibs_container-x64-1, test-digitalocean-alpine311_container-x64-1, test-digitalocean-ubuntu1804_sharedlibs_container-x64-9 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/40261/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/40352/ |
Example
not ok 3412 sequential/test-debugger-heap-profiler
---
duration_ms: 13.635
severity: fail
exitcode: 1
stack: |-
/home/iojs/build/workspace/node-test-commit-linux-containered/test/common/debugger.js:84
reject(new Error([
^
Error: Timeout (5000) while waiting for />\s+$/; found: Heap snapshot: 0/0
Heap snapshot: 0/34436
Heap snapshot: 10000/34436Heap snapshot: 20000/34436
Heap snapshot: 30000/34436
Heap snapshot: 34435/34436
Heap snapshot: 34436/34436
Heap snaphost prepared.
Writing snapshot: 102400
Writing snapshot: 204800
Writing snapshot: 307200
Writing snapshot: 409600
Writing snapshot: 512000
Writing snapshot: 614400
Writing snapshot: 716800
Writing snapshot: 819200
Writing snapshot: 921600
Writing snapshot: 1024000
Writing snapshot: 1126400
Writing snapshot: 1228800
Writing snapshot: 1331200
Writing snapshot: 1433600
Writing snapshot: 1536000
...
| Reason | sequential/test-worker-prof |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 3 (https://github.com/nodejs/node/pull/40239/, https://github.com/nodejs/node/pull/40478/, https://github.com/nodejs/node/pull/40488/) |
| Appeared | test-requireio_svincent-debian10-armv7l_pi2-3, test-digitalocean-alpine311_container-x64-1, test-rackspace-win2012r2_vs2015-x64-2 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/40284/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/40336/ |
Example
not ok 837 sequential/test-worker-prof
---
duration_ms: 189.626
severity: fail
exitcode: 1
stack: |-
node:assert:123
throw new AssertionError(obj);
^
AssertionError [ERR_ASSERTION]: child exited with signal: {
error: Error: spawnSync /home/iojs/build/workspace/node-test-binary-arm/out/Release/node ETIMEDOUT
at Object.spawnSync (node:internal/child_process:1081:20)
at spawnSync (node:child_process:812:24)
at Object.<anonymous> (/home/iojs/build/workspace/node-test-binary-arm/test/sequential/test-worker-prof.js:53:23)
at Module._compile (node:internal/modules/cjs/loader:1095:14)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1147:10)
at Module.load (node:internal/modules/cjs/loader:975:32)
at Function.Module._load (node:internal/modules/cjs/loader:822:12)
at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
at node:internal/main/r...
| Reason | parallel/test-crypto-classes |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/40400/, https://github.com/nodejs/node/pull/39924/) |
| Appeared | test-requireio_svincent-debian10-armv7l_pi2-2, test-requireio_joeyvandijk-debian10-armv7l_pi2-2 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/40274/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/40311/ |
Example
not ok 214 parallel/test-crypto-classes
---
duration_ms: 240.64
severity: fail
exitcode: -15
stack: |-
timeout
...
| Reason | parallel/test-crypto-dh-leak |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/39924/, https://github.com/nodejs/node/pull/40119/) |
| Appeared | test-requireio_rvagg-debian10-armv7l_pi2-1, test-requireio_ceejbot-debian10-armv7l_pi2-1 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/40308/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/40321/ |
Example
not ok 234 parallel/test-crypto-dh-leak
---
duration_ms: 240.73
severity: fail
exitcode: -15
stack: |-
timeout
...
Jenkins Failure
Example
java.io.IOException: Backing channel 'JNLP4-connect connection from 203.217.18.114/203.217.18.114:49508' is disconnected.
at hudson.remoting.RemoteInvocationHandler.channelOrFail(RemoteInvocationHandler.java:216)
at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:286)
at com.sun.proxy.$Proxy86.isAlive(Unknown Source)
at hudson.Launcher$RemoteLauncher$ProcImpl.isAlive(Launcher.java:1213)
at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:1205)
| Reason | Build timed out (after 10 minutes). Marking the build as failed. |
|---|---|
| Type | JENKINS_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/40094/, https://github.com/nodejs/node/pull/40357/) |
| Appeared | test-ibm-ubuntu1804-x64-1 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/40258/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/40259/ |
Example
Build timed out (after 10 minutes). Marking the build as failed.
Git Failure
Build Failure
Example
fatal error: ld terminated with signal 9 [Killed]
Example
sh: line 30: sudo: command not found
| Reason | ERROR: Step �Publish JUnit test result report� failed: No test report files were found. Configuration error? |
|---|---|
| Type | BUILD_FAILURE |
| Failed PR | 9 (https://github.com/nodejs/node/pull/40450/, https://github.com/nodejs/node/pull/40380/, https://github.com/nodejs/node/pull/40463/, https://github.com/nodejs/node/pull/40457/, https://github.com/nodejs/node/pull/40239/, https://github.com/nodejs/node/pull/40466/, https://github.com/nodejs/node/pull/39924/, https://github.com/nodejs/node/pull/40119/, https://github.com/nodejs/node/pull/40416/) |
| Appeared | test-azure_msft-win10_vs2019-x64-1, test-azure_msft-win10_vs2019-x64-3, test-azure_msft-win2016_vs2017-x64-3, test-azure_msft-win2016_vs2017-x64-5, test-azure_msft-win10_vcbt2015-x64-3 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/40305/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/40324/ |
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
Example
fatal: No rebase in progress?
| Reason | error: remote GitHub already exists. |
|---|---|
| Type | BUILD_FAILURE |
| Failed PR | 3 (https://github.com/nodejs/node/pull/40094/, https://github.com/nodejs/node/pull/40488/, https://github.com/nodejs/node/pull/40481/) |
| Appeared | test-rackspace-win2012r2_vs2019-x64-6, test-rackspace-win2012r2_vs2019-x64-3, test-rackspace-win2012r2_vs2019-x64-1, test-rackspace-win2012r2_vs2017-x64-1, test-rackspace-win2012r2_vs2019-x64-2 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/40258/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/40337/ |
Example
error: remote GitHub already exists.
> git fetch --prune --no-tags GitHub
> git fetch --prune --no-tags https://github.com/nodejs/build.git +refs/heads/master:refs/remotes/jenkins_tmp
| Reason | fatal error: Killed signal terminated program cc1plus |
|---|---|
| Type | BUILD_FAILURE |
| Failed PR | 3 (https://github.com/nodejs/node/pull/40405/, https://github.com/nodejs/node/pull/40434/, https://github.com/nodejs/node/pull/36111/) |
| Appeared | test-rackspace-fedora32-x64-1 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/40261/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/40273/ |
Example
fatal error: Killed signal terminated program cc1plus
| Reason | ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error? |
|---|---|
| Type | BUILD_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/40119/, https://github.com/nodejs/node/pull/40478/) |
| Appeared | test-requireio_ceejbot-debian10-armv7l_pi2-1, test-requireio_securogroup-debian10-arm64_pi3-1, test-requireio_joeyvandijk-debian10-armv7l_pi2-2, test-requireio_svincent-debian10-armv7l_pi2-2, test-requireio_rvagg-debian10-armv7l_pi2-1, test-requireio_williamkapke-debian10-arm64_pi3-2, test-requireio_louiscntr-debian10-armv7l_pi2-1, test-requireio_davglass-debian10-arm64_pi3-1, test-requireio_piccoloaiutante-debian10-arm64_pi3-1, test-requireio_williamkapke-debian10-arm64_pi3-1 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/40300/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/40343/ |
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-arm] $ /bin/bash -ex /tmp/jenkins8200362485078510179.sh
+ '[' -d .git ']'
+ git clean -fdx
Progress
-
wpt/test-user-timing(15) -
parallel/test-http2-pipe-named-pipe(10) -
parallel/test-repl-sigint-nested-eval(10) -
parallel/test-crypto-dh(7) -
sequential/test-net-connect-econnrefused(7) -
parallel/test-inspector-connect-main-thread(5) -
node-api/test_threadsafe_function/test(4) -
parallel/test-child-process-fork-closed-channel-segfault(4) -
parallel/test-crypto-secure-heap(4) -
parallel/test-http2-cancel-while-client-reading(3) -
parallel/test-trace-events-fs-sync(3) -
pummel/test-fs-watch-non-recursive(3) -
sequential/test-debugger-heap-profiler(3) -
sequential/test-worker-prof(3) -
parallel/test-crypto-classes(2) -
parallel/test-crypto-dh-leak(2) -
Backing channel 'JNLP4-connect connection from ... is disconnected.(8) -
Build timed out (after 10 minutes). Marking the build as failed.(2) -
fatal error: ld terminated with signal 9 [Killed](18) -
sh: line 30: sudo: command not found(16) -
ERROR: Step �Publish JUnit test result report� failed: No test report files were found. Configuration error?(9) -
fatal: No rebase in progress?(7) -
error: remote GitHub already exists.(3) -
fatal error: Killed signal terminated program cc1plus(3) -
ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error?(2)
- Lingua principale
- Shell
- Stelle
- 57
- Fork
- 20
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Guida per i contributori
Apri la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di nodejs/reliability
-
CI Reliability 2026-09-20 Aperta
Difficoltà 4/5 3-5 giorni Idoneità per principianti 35/100
nodejs/reliability#1666 ·
-
CI Reliability 2026-09-19 Aperta
Difficoltà 4/5 3-5 giorni Idoneità per principianti 25/100
nodejs/reliability#1665 ·
-
CI Reliability 2026-09-18 Aperta
Difficoltà 5/5 Più di una settimana Idoneità per principianti 25/100
nodejs/reliability#1664 ·
-
CI Reliability 2026-09-17 Aperta
Difficoltà 4/5 3-5 giorni Idoneità per principianti 35/100
nodejs/reliability#1663 ·
-
CI Reliability 2026-09-16 Aperta
Difficoltà 4/5 3-5 giorni Idoneità per principianti 35/100
nodejs/reliability#1662 ·
Tutte le issue di nodejs/reliability
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
community-scripts/ProxmoxVE#17396 · 1 commento ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
mattpocock/skills#1099 ·
-
Update Vish to 1.1.5 Apertapackage-update
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
oSoWoSo/vOid_Community_repOsitory#144 · 1 commento ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 88/100
-
help wanted new command
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
tldr-pages/tldr#24151 ·