CI Reliability 2024-03-17
Open
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- node.js, shell
- Domain
- ci-cd, devops, testing-qa
Research direction
Start by reviewing the listed CI job logs and the named failures, including parallel/test-domain-error-types, parallel/test-debugger-heap-profiler, and parallel/test-worker-memory. Use the generated ncu-ci walk pr command context to compare occurrences across platforms; done means the recurring CI failures are understood and addressed so the affected pull requests no longer fail for these reasons.
Written by the indexing model from the issue text.
Description
Failures in node-test-pull-request/57682 to node-test-pull-request/57781 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 |
|---|---|---|---|---|---|---|
| 2024-03-17 00:08 | 0 | 1 | 31 | 6 | 62 | 1.06% |
JSTest Failure
Example
not ok 945 parallel/test-domain-error-types
---
duration_ms: 1441.34600
severity: crashed
exitcode: -11
stack: |-
...
| Reason | parallel/test-debugger-heap-profiler |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 4 (https://github.com/nodejs/node/pull/52023/, https://github.com/nodejs/node/pull/52024/, https://github.com/nodejs/node/pull/52051/, https://github.com/nodejs/node/pull/52040/) |
| Appeared | test-azure_msft-win11_vs2022-arm64-4, test-azure_msft-win2016_vs2017-x64-2 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/57688/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/57709/ |
Example
not ok 182 parallel/test-debugger-heap-profiler
---
duration_ms: 2464.99000
severity: fail
exitcode: 1
stack: |-
Can't clean tmpdir: d:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.180
Files blocking: [ 'node.heapsnapshot' ]
d:\workspace\node-test-binary-windows-js-suites\node\test\common\tmpdir.js:69
throw e;
^
Error: EBUSY: resource busy or locked, rmdir 'd:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.180'
at rmdirSync (node:fs:1219:11)
at _rmdirSync (node:internal/fs/rimraf:235:5)
at rimrafSync (node:internal/fs/rimraf:193:7)
at Object.rmSync (node:fs:1268:10)
at rmSync (d:\workspace\node-test-binary-windows-js-suites\node\test\common\tmpdir.js:20:8)
at onexit (d:\workspace\node-test-binary-windows-js-suites\node\test\common\tmpdir.js:54:5)
at process.<anonymous> (d:\workspace\node-test-binary-windows-js-suites\node\test\common\tmpdir.js:43:14)
at process.emit (...
| Reason | parallel/test-worker-memory |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 4 (https://github.com/nodejs/node/pull/52040/, https://github.com/nodejs/node/pull/52077/, https://github.com/nodejs/node/pull/52071/, https://github.com/nodejs/node/pull/52101/) |
| Appeared | test-azure_msft-win10_vs2019-x64-3, test-azure_msft-win2016_vs2017-x64-1, test-rackspace-win2022_vs2022-x64-6 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/57708/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/57761/ |
Example
not ok 886 parallel/test-worker-memory
---
duration_ms: 2110.14900
severity: fail
exitcode: 3221226356
stack: |-
run() called with n=15 (numWorkers=4)
run() called with n=15 (numWorkers=4)
run() called with n=15 (numWorkers=4)
run() called with n=15 (numWorkers=4)
run() called with n=14 (numWorkers=4)
run() called with n=14 (numWorkers=4)
run() called with n=14 (numWorkers=4)
run() called with n=14 (numWorkers=4)
run() called with n=13 (numWorkers=4)
run() called with n=13 (numWorkers=4)
run() called with n=13 (numWorkers=4)
run() called with n=13 (numWorkers=4)
run() called with n=12 (numWorkers=4)
run() called with n=12 (numWorkers=4)
run() called with n=12 (numWorkers=4)
run() called with n=12 (numWorkers=4)
run() called with n=11 (numWorkers=4)
run() called with n=11 (numWorkers=4)
run() called with n=11 (numWorkers=4)
run() called with n=10 (numWorkers=4)
run() called with n=10 (numWorkers=4)
run() called wi...
| Reason | parallel/test-cluster-fork-stdio |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 3 (https://github.com/nodejs/node/pull/51977/, https://github.com/nodejs/node/pull/52092/, https://github.com/nodejs/node/pull/52110/) |
| Appeared | test-azure_msft-win11_vs2022-arm64-3, test-azure_msft-win10_vs2019-x64-3 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/57756/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/57781/ |
Example
not ok 915 parallel/test-cluster-fork-stdio
---
duration_ms: 120313.66400
severity: fail
exitcode: 1
stack: |-
timeout
...
| Reason | parallel/test-runner-output |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 3 (https://github.com/nodejs/node/pull/52023/, https://github.com/nodejs/node/pull/51091/, https://github.com/nodejs/node/pull/51021/) |
| Appeared | test-digitalocean-freebsd12-x64-2, test-azure_msft-win11_vs2022-x64-1, test-orka-macos11-x64-2 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/57688/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/57768/ |
Example
not ok 2466 parallel/test-runner-output
---
duration_ms: 26034.59100
severity: fail
exitcode: 1
stack: |-
TAP version 13
# Subtest: test runner output
# Subtest: test-runner/output/abort.js
ok 1 - test-runner/output/abort.js
---
duration_ms: 14159.988486
...
| Reason | sequential/test-worker-fshandles-open-close-on-termination |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 3 (https://github.com/nodejs/node/pull/52023/, https://github.com/nodejs/node/pull/52051/, https://github.com/nodejs/node/pull/52037/) |
| Appeared | test-rackspace-win2019_vs2019-x64-3, test-azure_msft-win2016_vs2017-x64-2, test-azure_msft-win11_vs2022-x64-1 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/57688/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/57713/ |
Example
not ok 973 sequential/test-worker-fshandles-open-close-on-termination
---
duration_ms: 1050.04300
severity: crashed
exitcode: 3221225477
stack: |-
...
| Reason | benchmark/test-benchmark-http2 |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/52037/, https://github.com/nodejs/node/pull/51136/) |
| Appeared | test-azure_msft-win2016_vs2017-x64-2, test-azure_msft-win2016_vs2017-x64-1 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/57712/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/57766/ |
Example
not ok 184 benchmark/test-benchmark-http2
---
duration_ms: 1960.63900
severity: fail
exitcode: 1
stack: |-
Error: test-double-http2 failed with 3221226505.
at ChildProcess.<anonymous> (C:\workspace\node-test-binary-windows-native-suites\node\benchmark\_http-benchmarkers.js:242:16)
at Object.onceWrapper (node:events:632:26)
at ChildProcess.emit (node:events:517:28)
at maybeClose (node:internal/child_process:1098:16)
at ChildProcess._handle.onexit (node:internal/child_process:303:5)
node:assert:125
throw new AssertionError(obj);
^
AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:
3221226505 !== 0
at ChildProcess.<anonymous> (C:\workspace\node-test-binary-windows-native-suites\node\test\common\benchmark.js:28:12)
at ChildProcess.emit (node:events:517:28)
at ChildProcess._handle.onexit (node:internal/child_process:292:12) {
generatedMessage: true,
code: 'ERR_ASSERTIO...
| Reason | parallel/test-blob-file-backed |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/52062/, https://github.com/nodejs/node/pull/51972/) |
| Appeared | test-digitalocean-fedora38-x64-2, test-digitalocean-alpine318_container-x64-1 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/57719/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/57771/ |
Example
not ok 318 parallel/test-blob-file-backed
---
duration_ms: 111.65700
severity: fail
exitcode: 1
stack: |-
node:internal/per_context/domexception:53
ErrorCaptureStackTrace(this);
^
DOMException [NotReadableError]: The blob could not be read
at new DOMException (node:internal/per_context/domexception:53:5)
at __node_internal_ (node:internal/util:695:10)
at BlobReader.<anonymous> (node:internal/blob:292:25)
Node.js v20.11.2-pre
...
| Reason | parallel/test-file-write-stream4 |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/52051/, https://github.com/nodejs/node/pull/51977/) |
| Appeared | test-digitalocean-ubuntu2204_sharedlibs_container-x64-1, test-digitalocean-alpine315_container-x64-2 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/57702/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/57779/ |
Example
not ok 1396 parallel/test-file-write-stream4
---
duration_ms: 120091.07400
severity: fail
exitcode: -15
stack: |-
timeout
...
| Reason | parallel/test-fs-read-stream-concurrent-reads |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/52077/, https://github.com/nodejs/node/pull/51091/) |
| Appeared | test-equinix-ubuntu2004_container-armv7l-2, test-ibm-ubuntu2204_sharedlibs_container-x64-2 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/57741/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/57751/ |
Example
not ok 1192 parallel/test-fs-read-stream-concurrent-reads
---
duration_ms: 1229.63500
severity: crashed
exitcode: -11
stack: |-
...
| Reason | parallel/test-performance-function |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/51050/, https://github.com/nodejs/node/pull/51977/) |
| Appeared | test-ibm-rhel8-x64-1, test-ibm-rhel8-x64-2 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/57736/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/57748/ |
Example
not ok 2346 parallel/test-performance-function
---
duration_ms: 195.65100
severity: fail
exitcode: 1
stack: |-
node:internal/histogram:291
validateInteger(val, 'val', 1);
^
RangeError [ERR_OUT_OF_RANGE]: The value of "val" is out of range. It must be >= 1 && <= 9007199254740991. Received 0
at RecordableHistogram.record (node:internal/histogram:291:5)
at processComplete (node:internal/perf/timerify:40:15)
at timerified m (node:internal/perf/timerify:87:5)
at /home/iojs/build/workspace/node-test-commit-linux/test/parallel/test-performance-function.js:103:5 {
code: 'ERR_OUT_OF_RANGE'
}
Node.js v22.0.0-pre
...
| Reason | parallel/test-shadow-realm-gc-module |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/52024/, https://github.com/nodejs/node/pull/51362/) |
| Appeared | test-digitalocean-ubi81_container-x64-1, test-ibm-ubi81_container-x64-1 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/57700/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/57722/ |
Example
not ok 2431 parallel/test-shadow-realm-gc-module
---
duration_ms: 5262.37100
severity: crashed
exitcode: -6
stack: |-
<--- Last few GCs --->
) [2298362:0x6515000] 4715 ms: Mark-Compact 19.1 (32.4) -> 16.5 (33.4) MB, pooled: 0 MB, 12.07 / 0.01 ms (+ 16.1 ms in 0 steps since start of marking, biggest step 0.0 ms, walltime since start of marking 43 ms) (average mu = 0.627, current mu = 0.661) [2298362:0x6515000] 4886 ms: Mark-Compact (reduce) 23.6 (34.4) -> 20.1 (21.9) MB, pooled: 0 MB, 38.68 / 0.01 ms (+ 43.8 ms in 0 steps since start of marking, biggest step 0.0 ms, walltime since start of marking 129 ms) (average mu = 0.620, current mu
<--- JS stacktrace --->
FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
----- Native stack trace -----
1: 0xd70c70 node::OOMErrorHandler(char const*, v8::OOMDetails const&) [out/Release/node]
2: 0x10dc910 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, v8::OO...
| Reason | parallel/test-tls-ticket-cluster |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/52077/, https://github.com/nodejs/node/pull/51136/) |
| Appeared | test-nearform-macos10.15-x64-1, test-ibm-rhel8-x64-1 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/57741/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/57766/ |
Example
not ok 2808 parallel/test-tls-ticket-cluster
---
duration_ms: 479.76500
severity: fail
exitcode: 1
stack: |-
[primary] got "listening"
[primary] connecting 55824 session? false
[primary] got "listening"
[worker] connection reused? false
[primary] got "not-reused"
[primary] connecting 55824 session? true
[worker] connection reused? true
[primary] got "reused"
[primary] connecting 55824 session? true
[worker] connection reused? true
[primary] got "reused"
[primary] connecting 55824 session? true
[worker] connection reused? true
[primary] got "reused"
[primary] connecting 55824 session? true
[worker] connection reused? true
[primary] got "reused"
[primary] connecting 55824 session? true
[worker] connection reused? true
[primary] got "reused"
[primary] connecting 55824 session? true
[worker] connection reused? true
[primary] got "reused"
[primary] connecting 55824 session? true
[worker] connection reused?...
| Reason | sequential/test-http-regr-gh-2928 |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/52038/, https://github.com/nodejs/node/pull/51136/) |
| Appeared | test-digitalocean-freebsd12-x64-1, test-azure_msft-win2016_vs2017-x64-1 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/57716/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/57766/ |
Example
not ok 3915 sequential/test-http-regr-gh-2928
---
duration_ms: 120076.64400
severity: fail
exitcode: -15
stack: |-
timeout
.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+....
| Reason | sequential/test-worker-fshandles-error-on-termination |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/52040/, https://github.com/nodejs/node/pull/52110/) |
| Appeared | test-rackspace-win2019_vs2019-x64-3, test-azure_msft-win2016_vs2017-x64-2 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/57709/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/57781/ |
Example
not ok 974 sequential/test-worker-fshandles-error-on-termination
---
duration_ms: 953.00100
severity: fail
exitcode: 134
stack: |-
# foo[9736]: at C:\workspace\node-compile-windows\node\src\util-inl.h:376
# Assertion failed: !(n > 0) || (ret != nullptr)
----- Native stack trace -----
1: 00007FF79977245B node::SetCppgcReference+16059
2: 00007FF7996D8B01 EVP_MD_meth_get_input_blocksize+79921
3: 00007FF799521FB4 X509_get0_tbs_sigalg+28980
4: 00007FF79966F885 DH_get0_priv_key+71525
5: 000001B29FE0EEDF
----- JavaScript stack trace -----
1: getCLIOptionsFromBinding (node:internal/options:20:32)
2: getOptionValue (node:internal/options:45:19)
3: addReadOnlyProcessAlias (node:internal/process/pre_execution:283:17)
4: patchProcessObject (node:internal/process/pre_execution:265:3)
5: prepareExecution (node:internal/process/pre_execution:104:21)
6: prepareWorkerThreadExecution (node:internal/process/pre_execution:...
Git Failure
Build Failure
Example
fatal: No rebase in progress?
| Reason | ERROR: Step ‘Record fingerprints of files to track usage’ failed: no workspace for ... |
|---|---|
| Type | BUILD_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/51362/, https://github.com/nodejs/node/pull/45427/) |
| Appeared | test-digitalocean-fedora38-x64-2, test-digitalocean-fedora37-x64-1, test-rackspace-fedora32-x64-1 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/57759/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/57778/ |
Example
ERROR: Step ‘Record fingerprints of files to track usage’ failed: no workspace for node-test-commit-linux/nodes=fedora-latest-x64 #56666
Collecting metadata...
Metadata collection done.
Notifying upstream projects of job completion
Finished: FAILURE
| Reason | Makefile:1348: recipe for target 'tools/.mdlintstamp' failed |
|---|---|
| Type | BUILD_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/52037/, https://github.com/nodejs/node/pull/51977/) |
| Appeared | test-ibm-ubuntu1804-x64-1 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/57729/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/57774/ |
Example
Makefile:1348: recipe for target 'tools/.mdlintstamp' failed
make: *** [tools/.mdlintstamp] Error 1
+ cat test-eslint.tap
+ grep -v '^ok\|^TAP version 13\|^1\.\.'
+ sed '/^\s*$/d'
+ exit 1
| Reason | error C1060: compiler is out of heap space [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_initializers.vcxproj] |
|---|---|
| Type | BUILD_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/45427/, https://github.com/nodejs/node/pull/51977/) |
| Appeared | test-rackspace-win2022_vs2022-x64-1, test-rackspace-win2022_vs2022-x64-6 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/57750/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/57779/ |
Example
error C1060: compiler is out of heap space [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_initializers.vcxproj]
iterator-from-tq-csa.cc
C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.39.33519\include\tuple(315,1): fatal error C1060: compiler is out of heap space [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_initializers.vcxproj]
math-tq-csa.cc
C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.39.33519\include\tuple(47,90): fatal error C1060: compiler is out of heap space [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_initializers.vcxproj]
Jenkins Failure
CCTest Failure
Progress
-
parallel/test-domain-error-types(5) -
parallel/test-debugger-heap-profiler(4) -
parallel/test-worker-memory(4) -
parallel/test-cluster-fork-stdio(3) -
parallel/test-runner-output(3) -
sequential/test-worker-fshandles-open-close-on-termination(3) -
benchmark/test-benchmark-http2(2) -
parallel/test-blob-file-backed(2) -
parallel/test-file-write-stream4(2) -
parallel/test-fs-read-stream-concurrent-reads(2) -
parallel/test-performance-function(2) -
parallel/test-shadow-realm-gc-module(2) -
parallel/test-tls-ticket-cluster(2) -
sequential/test-http-regr-gh-2928(2) -
sequential/test-worker-fshandles-error-on-termination(2) -
fatal: No rebase in progress?(8) -
ERROR: Step ‘Record fingerprints of files to track usage’ failed: no workspace for ...(2) -
Makefile:1348: recipe for target 'tools/.mdlintstamp' failed(2) -
error C1060: compiler is out of heap space [C:\workspace\node-compile-windows\node\tools\v8_gypfiles\v8_initializers.vcxproj](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
-
out-of-date
Difficulty 1/5 Under an hour Newbie friendliness 82/100
CachyOS/CachyOS-PKGBUILDS#1894 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
community-scripts/ProxmoxVE#17396 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
mattpocock/skills#1099 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
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 ·