CI Reliability 2023-06-12
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- javascript, node.js, shell
- Domain
- ci-cd, devops, testing-qa
Research direction
Start with the listed CI examples and the named tests: parallel/test-child-process-stdio-reuse-readable-stdio, parallel/test-fs-watch-recursive-add-file-to-existing-subfolder, parallel/test-performance-function, parallel/test-child-process-pipe-dataflow, sequential/test-perf-hooks, and parallel/test-blob-file-backed. Compare their platform-specific logs and test files; done requires identifying and addressing the causes of the recurring failures so the CI jobs stop reporting them.
Written by the indexing model from the issue text.
Description
Failures in node-test-pull-request/52116 to node-test-pull-request/52215 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 |
|---|---|---|---|---|---|---|
| 2023-06-12 00:16 | 0 | 0 | 30 | 1 | 69 | 0.00% |
JSTest Failure
Example
not ok 111 parallel/test-child-process-stdio-reuse-readable-stdio
---
duration_ms: 270.99800
severity: fail
exitcode: 1
stack: |-
node:assert:125
throw new AssertionError(obj);
^
AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:
+ actual - expected
+ '����\x07\x00\x00\x00$�)\x10\x02\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x07\x00\x0F\x00\x00\x00\x00\x00������������\x07\x00\x00\x00$�)\x10\x02\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x07\x00\x0F\x00\x00\x00\x00\x00������������\x07\x00\x00\x00$�)\x10\x02\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x07\x00\x0F\x00\x00\x00\x00\x00������������\x07\x00\x00\x00$�)\x10\x02\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x07\x00\x0F\x00\x00\x00\x00\x00������������\x07\x00\x00\x00$�)\x10\x02\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x07\x00\x0F\x00\x00\x00\x00\x00������������\x07\x00\x00\x00$�)\x10\x02\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x07\x00\x0F\x00\x00\x00\x00\x00������������\x07\x00\x...
| Reason | parallel/test-fs-watch-recursive-add-file-to-existing-subfolder |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 8 (https://github.com/nodejs/node/pull/48354/, https://github.com/nodejs/node/pull/48186/, https://github.com/nodejs/node/pull/48378/, https://github.com/nodejs/node/pull/48395/, https://github.com/nodejs/node/pull/46561/, https://github.com/nodejs/node/pull/48232/, https://github.com/nodejs/node/pull/47854/, https://github.com/nodejs/node/pull/48415/) |
| Appeared | test-ibm-rhel8-s390x-1, test-ibm-rhel8-s390x-4, test-ibm-rhel8-s390x-3 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/52120/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/52203/ |
Example
not ok 1325 parallel/test-fs-watch-recursive-add-file-to-existing-subfolder
---
duration_ms: 120064.51000
severity: fail
exitcode: -15
stack: |-
timeout
...
| Reason | parallel/test-performance-function |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 7 (https://github.com/nodejs/node/pull/48297/, https://github.com/nodejs/node/pull/47791/, https://github.com/nodejs/node/pull/48370/, https://github.com/nodejs/node/pull/48325/, https://github.com/nodejs/node/pull/46561/, https://github.com/nodejs/node/pull/48383/, https://github.com/nodejs/node/pull/48415/) |
| Appeared | undefined |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/52123/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/52203/ |
Example
not ok 2273 parallel/test-performance-function
---
duration_ms: 214.88200
severity: fail
exitcode: 1
stack: |-
node:internal/event_target:1037
process.nextTick(() => { throw err; });
^
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:283: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-custom-suites-freestyle/test/parallel/test-performance-function.js:98:5
at runNextTicks (node:internal/process/task_queues:60:5)
at listOnTimeout (node:internal/timers:540:9)
at process.processTimers (node:internal/timers:514:7)
Emitted 'error' event on Worker instance at:
at [kOnErrorMessage] (node:internal/worker:326:10)
at [kOnMessage] (node:internal/worker:337:37)...
Example
not ok 119 parallel/test-child-process-pipe-dataflow
---
duration_ms: 0.309
severity: fail
exitcode: 1
stack: |-
node:assert:125
throw new AssertionError(obj);
^
AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:
+ actual - expected
+ '144646'
- '1048577'
at process.<anonymous> (C:\workspace\node-test-binary-windows-js-suites\node\test\parallel\test-child-process-pipe-dataflow.js:71:12)
at process.emit (node:events:525:35) {
generatedMessage: true,
code: 'ERR_ASSERTION',
actual: '144646',
expected: '1048577',
operator: 'strictEqual'
}
Node.js v18.16.1-pre
...
Example
not ok 3884 sequential/test-perf-hooks
---
duration_ms: 413.36700
severity: fail
exitcode: 1
stack: |-
{
name: 'node',
entryType: 'node',
startTime: 0,
duration: { around: 301.69351506233215 },
nodeStart: { around: 0 },
v8Start: { around: 0 },
bootstrapComplete: { around: 301.6493549346924, delay: 2500 },
environment: { around: 0 },
loopStart: -1,
loopExit: -1
}
node:assert:399
throw err;
^
AssertionError [ERR_ASSERTION]: environment: 265.3230710029602 >= 250
at checkNodeTiming (/home/iojs/build/workspace/node-test-commit-arm/test/sequential/test-perf-hooks.js:31:7)
at Object.<anonymous> (/home/iojs/build/workspace/node-test-commit-arm/test/sequential/test-perf-hooks.js:43:1)
at Module._compile (node:internal/modules/cjs/loader:1255:14)
at Module._extensions..js (node:internal/modules/cjs/loader:1309:10)
at Module.load (node:internal/modules/cjs/loader:1113:32)
...
| Reason | parallel/test-blob-file-backed |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/47688/, https://github.com/nodejs/node/pull/48384/) |
| Appeared | test-orka-macos11-x64-2, test-nearform-macos10.15-x64-2 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/52160/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/52161/ |
Example
not ok 75 parallel/test-blob-file-backed
---
duration_ms: 325.30300
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:663:10)
at BlobReader.<anonymous> (node:internal/blob:349:27)
Node.js v21.0.0-pre
...
| Reason | parallel/test-fs-watch-recursive-add-file-to-new-folder |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/48332/, https://github.com/nodejs/node/pull/47854/) |
| Appeared | test-ibm-rhel8-s390x-1, test-ibm-rhel8-s390x-4 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/52145/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/52197/ |
Example
not ok 1266 parallel/test-fs-watch-recursive-add-file-to-new-folder
---
duration_ms: 120034.22200
severity: fail
exitcode: -15
stack: |-
timeout
...
| Reason | parallel/test-fs-watch-recursive-update-file |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/48304/, https://github.com/nodejs/node/pull/48410/) |
| Appeared | test-ibm-rhel8-s390x-1, test-ibm-rhel8-s390x-4 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/52141/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/52194/ |
Example
not ok 1376 parallel/test-fs-watch-recursive-update-file
---
duration_ms: 120056.01300
severity: fail
exitcode: -15
stack: |-
timeout
...
| Reason | parallel/test-http-request-join-authorization-headers |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/48275/, https://github.com/nodejs/node/pull/46561/) |
| Appeared | test-orka-macos11-x64-2, test-ibm-aix72-ppc64_be-2 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/52166/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/52193/ |
Example
not ok 1248 parallel/test-http-request-join-authorization-headers
---
duration_ms: 389.74500
severity: fail
exitcode: 1
stack: |-
node:assert:125
throw new AssertionError(obj);
^
AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:
'1, 2' !== '1'
at Server.<anonymous> (/Users/iojs/build/workspace/node-test-commit-osx/nodes/osx11-x64/test/parallel/test-http-request-join-authorization-headers.js:39:12)
at Server.<anonymous> (/Users/iojs/build/workspace/node-test-commit-osx/nodes/osx11-x64/test/common/index.js:466:15)
at Server.emit (node:events:511:28)
at parserOnIncoming (node:_http_server:1121:12)
at HTTPParser.parserOnHeadersComplete (node:_http_common:119:17) {
generatedMessage: true,
code: 'ERR_ASSERTION',
actual: '1, 2',
expected: '1',
operator: 'strictEqual'
}
Node.js v21.0.0-pre
...
| Reason | parallel/test-http-server-consumed-timeout |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/48369/, https://github.com/nodejs/node/pull/48414/) |
| Appeared | test-ibm-rhel8-s390x-1, test-ibm-rhel7-s390x-1 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/52134/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/52213/ |
Example
not ok 1303 parallel/test-http-server-consumed-timeout
---
duration_ms: 1030.80200
severity: fail
exitcode: 1
stack: |-
node:assert:172
throw err;
^
AssertionError [ERR_ASSERTION]: Request timeout should not fire
at IncomingMessage.<anonymous> (/home/iojs/build/workspace/node-test-commit-linuxone/test/parallel/test-http-server-consumed-timeout.js:51:14)
at IncomingMessage.emit (node:events:511:28)
at Socket.socketOnTimeout (node:_http_server:753:50)
at Socket.emit (node:events:511:28)
at Socket._onTimeout (node:net:582:8)
at listOnTimeout (node:internal/timers:573:17)
at process.processTimers (node:internal/timers:514:7) {
generatedMessage: false,
code: 'ERR_ASSERTION',
actual: undefined,
expected: undefined,
operator: 'fail'
}
Node.js v21.0.0-pre
...
| Reason | parallel/test-http2-misbehaving-multiplex |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/48378/, https://github.com/nodejs/node/pull/48232/) |
| Appeared | test-osuosl-rhel8-ppc64_le-4, test-orka-macos11-x64-1 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/52147/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/52188/ |
Example
not ok 1711 parallel/test-http2-misbehaving-multiplex
---
duration_ms: 220.54900
severity: fail
exitcode: 1
stack: |-
node:assert:125
throw new AssertionError(obj);
^
AssertionError [ERR_ASSERTION]: Expected "actual" to be strictly unequal to: 5
at Http2Server.<anonymous> (/home/iojs/build/workspace/node-test-commit-plinux/nodes/rhel8-ppc64le/test/parallel/test-http2-misbehaving-multiplex.js:45:10)
at Http2Server.<anonymous> (/home/iojs/build/workspace/node-test-commit-plinux/nodes/rhel8-ppc64le/test/common/index.js:466:15)
at Http2Server.emit (node:events:511:28)
at ServerHttp2Session.sessionOnStream (node:internal/http2/core:3004:19)
at ServerHttp2Session.emit (node:events:511:28)
at emit (node:internal/http2/core:329:3)
at process.processTicksAndRejections (node:internal/process/task_queues:85:22) {
generatedMessage: true,
code: 'ERR_ASSERTION',
actual: 5,
expected: 5,
operator: 'notStri...
| Reason | parallel/test-inspector-async-hook-setup-at-inspect-brk |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/48147/, https://github.com/nodejs/node/pull/48129/) |
| Appeared | test-ibm-rhel8-s390x-4, test-osuosl-rhel8-ppc64_le-2 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/52153/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/52190/ |
Example
not ok 1818 parallel/test-inspector-async-hook-setup-at-inspect-brk
---
duration_ms: 15583.36100
severity: fail
exitcode: 1
stack: |-
[test] Connecting to a child Node process
[test] Testing /json/list
[err] Debugger listening on ws://127.0.0.1:34989/a73afa15-e5ee-4671-80f8-226ef26d8ee8
[err] For help, see: https://nodejs.org/en/docs/inspector
[err]
[err] Debugger attached.
[err]
Timed out waiting for matching notification (break on [eval]:1)
1
...
| Reason | parallel/test-inspector-console |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/48244/, https://github.com/nodejs/node/pull/48186/) |
| Appeared | test-ibm-rhel8-s390x-1, test-osuosl-rhel8-ppc64_le-2 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/52117/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/52143/ |
Example
not ok 1830 parallel/test-inspector-console
---
duration_ms: 15240.85100
severity: fail
exitcode: 1
stack: |-
[test] Connecting to a child Node process
[test] Testing /json/list
[err] Debugger listening on ws://127.0.0.1:35137/0d37ef11-f364-42af-979d-6afb3759bce4
[err] For help, see: https://nodejs.org/en/docs/inspector
[err]
[err] Debugger attached.
[err]
Timed out waiting for matching notification (Runtime.consoleAPICalled)
1
...
| Reason | parallel/test-inspector-wait-for-connection |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/48344/, https://github.com/nodejs/node/pull/48332/) |
| Appeared | test-nearform-macos10.15-x64-3 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/52119/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/52146/ |
Example
not ok 1781 parallel/test-inspector-wait-for-connection
---
duration_ms: 15540.09200
severity: fail
exitcode: 1
stack: |-
[test] Connecting to a child Node process
[test] Testing /json/list
[err] Debugger listening on ws://127.0.0.1:56749/3f6f30c0-41be-4dd7-96c7-9c8459dea172
[err] For help, see: https://nodejs.org/en/docs/inspector
[err]
[err] Debugger attached.
[err]
[out] before wait for debugger
[out]
Timed out waiting for matching notification (Console output matching "after wait for debugger")
1
...
| Reason | parallel/test-runner-output |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/48186/, https://github.com/nodejs/node/pull/46561/) |
| Appeared | undefined, test-ibm-ubuntu1804-x64-2 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/52128/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/52177/ |
Example
not ok 2568 parallel/test-runner-output
---
duration_ms: 3237.73900
severity: fail
exitcode: 1
stack: |-
TAP version 13
# Subtest: test runner output
# Subtest: test-runner/output/abort.js
not ok 1 - test-runner/output/abort.js
---
duration_ms: 1347.692168
failureType: 'testCodeFailure'
error: |-
Expected values to be strictly equal:
+ actual - expected ... Lines skipped
'TAP version 13\n' +
'# Subtest: promise timeout signal\n' +
...
| Reason | parallel/test-tls-ticket-cluster |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/48332/, https://github.com/nodejs/node/pull/46561/) |
| Appeared | test-nearform-macos10.15-x64-3, test-azure_msft-win10_vs2019-x64-2 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/52145/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/52184/ |
Example
not ok 2790 parallel/test-tls-ticket-cluster
---
duration_ms: 566.33500
severity: fail
exitcode: 1
stack: |-
[primary] got "listening"
[primary] connecting 59996 session? false
[worker] connection reused? false
[primary] got "not-reused"
[primary] connecting 59996 session? true
[worker] connection reused? true
[primary] got "reused"
[primary] connecting 59996 session? true
[worker] connection reused? true
[primary] got "reused"
[primary] connecting 59996 session? true
[worker] connection reused? true
[primary] got "reused"
[primary] connecting 59996 session? true
[worker] connection reused? true
[primary] got "reused"
[primary] connecting 59996 session? true
[worker] connection reused? true
[primary] got "reused"
[primary] connecting 59996 session? true
[worker] connection reused? true
[primary] got "reused"
[primary] connecting 59996 session? true
[worker] connection reused? true
[primary] got "reuse...
| Reason | sequential/test-single-executable-application |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/47854/, https://github.com/nodejs/node/pull/48416/) |
| Appeared | test-osuosl-rhel8-ppc64_le-2, test-osuosl-rhel8-ppc64_le-4 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/52197/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/52202/ |
Example
not ok 3922 sequential/test-single-executable-application
---
duration_ms: 9381.04200
severity: fail
exitcode: 1
stack: |-
Wrote single executable preparation blob to sea-prep.blob
warning: Can't find string offset for section name '.note.100'
warning: Can't find string offset for section name '.note.100'
warning: Can't find string offset for section name '.note.100'
warning: Can't find string offset for section name '.note.100'
warning: Can't find string offset for section name '.note.100'
warning: Can't find string offset for section name '.note'
warning: Can't find string offset for section name '.note.100'
warning: Can't find string offset for section name '.note.100'
warning: Can't find string offset for section name '.note.100'
node:child_process:924
throw err;
^
Error: Command failed: /home/iojs/node-tmp/.tmp.3921/sea -a --b=c d
at checkExecSyncError (node:child_process:885:11)
at execFileSync (node:child_pro...
| Reason | sequential/test-single-executable-application-disable-experimental-sea-warning |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/47854/, https://github.com/nodejs/node/pull/48416/) |
| Appeared | test-osuosl-rhel8-ppc64_le-2, test-osuosl-rhel8-ppc64_le-4 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/52197/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/52202/ |
Example
not ok 3923 sequential/test-single-executable-application-disable-experimental-sea-warning
---
duration_ms: 7906.99400
severity: fail
exitcode: 1
stack: |-
Wrote single executable preparation blob to sea-prep.blob
warning: Can't find string offset for section name '.note.100'
warning: Can't find string offset for section name '.note.100'
warning: Can't find string offset for section name '.note.100'
warning: Can't find string offset for section name '.note.100'
warning: Can't find string offset for section name '.note.100'
warning: Can't find string offset for section name '.note'
warning: Can't find string offset for section name '.note.100'
warning: Can't find string offset for section name '.note.100'
warning: Can't find string offset for section name '.note.100'
node:child_process:924
throw err;
^
Error: Command failed: /home/iojs/node-tmp/.tmp.3922/sea -a --b=c d
at checkExecSyncError (node:child_process:885:11)
...
| Reason | sequential/test-single-executable-application-empty |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/47854/, https://github.com/nodejs/node/pull/48416/) |
| Appeared | test-osuosl-rhel8-ppc64_le-2, test-osuosl-rhel8-ppc64_le-4 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/52197/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/52202/ |
Example
not ok 3924 sequential/test-single-executable-application-empty
---
duration_ms: 7757.88000
severity: fail
exitcode: 1
stack: |-
Wrote single executable preparation blob to sea-prep.blob
warning: Can't find string offset for section name '.note.100'
warning: Can't find string offset for section name '.note.100'
warning: Can't find string offset for section name '.note.100'
warning: Can't find string offset for section name '.note.100'
warning: Can't find string offset for section name '.note.100'
warning: Can't find string offset for section name '.note'
warning: Can't find string offset for section name '.note.100'
warning: Can't find string offset for section name '.note.100'
warning: Can't find string offset for section name '.note.100'
node:child_process:924
throw err;
^
Error: Command failed: /home/iojs/node-tmp/.tmp.3923/sea
at checkExecSyncError (node:child_process:885:11)
at execFileSync (node:child_process:...
| Reason | wpt/test-webcrypto |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/48402/, https://github.com/nodejs/node/pull/46561/) |
| Appeared | test-orka-macos11-x64-1, test-orka-macos11-x64-2 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/52178/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/52201/ |
Example
not ok 3950 wpt/test-webcrypto
---
duration_ms: 45102.68100
severity: crashed
exitcode: -6
stack: |-
[SKIPPED] algorithm-discards-context.https.window.js: Not relevant in Node.js context
[SKIPPED] historical.any.js: Not relevant in Node.js context
[PASS] setup - define tests
[PASS] X25519 key derivation checks for all-zero value result with a key of order 0
[PASS] X25519 key derivation checks for all-zero value result with a key of order 1
[PASS] X25519 key derivation checks for all-zero value result with a key of order 8
[PASS] X25519 key derivation checks for all-zero value result with a key of order p-1 (order 2)
[PASS] X25519 key derivation checks for all-zero value result with a key of order p (=0, order 4)
[PASS] X25519 key derivation checks for all-zero value result with a key of order p+1 (=1, order 1)
[PASS] X448 key derivation checks for all-zero value result with a key of order 0
[PASS] X448 key derivation checks for all-zero value result with a...
CCTest Failure
Jenkins Failure
| Reason | Build timed out (after 120 minutes). Marking the build as failed. |
|---|---|
| Type | JENKINS_FAILURE |
| Failed PR | 2 (https://github.com/nodejs/node/pull/48242/, https://github.com/nodejs/node/pull/48413/) |
| Appeared | test-digitalocean-fedora32-x64-1 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/52127/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/52204/ |
Example
Build timed out (after 120 minutes). Marking the build as failed.
Build Failure
| Reason | fatal: '/home/iojs/.ccache/node.shared.reference' does not appear to be a git repository |
|---|---|
| Type | BUILD_FAILURE |
| Failed PR | 3 (https://github.com/nodejs/node/pull/48325/, https://github.com/nodejs/node/pull/48232/, https://github.com/nodejs/node/pull/46826/) |
| Appeared | test-equinix-ubuntu2004_container-armv7l-1 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/52176/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/52212/ |
Example
fatal: '/home/iojs/.ccache/node.shared.reference' does not appear to be a git repository
fatal: Could not read from remote repository.
fatal: unable to create thread: Resource temporarily unavailable
fatal: failed to run repack
Progress
-
parallel/test-child-process-stdio-reuse-readable-stdio(12) -
parallel/test-fs-watch-recursive-add-file-to-existing-subfolder(8) -
parallel/test-performance-function(7) -
parallel/test-child-process-pipe-dataflow(4) -
sequential/test-perf-hooks(4) -
parallel/test-blob-file-backed(2) -
parallel/test-fs-watch-recursive-add-file-to-new-folder(2) -
parallel/test-fs-watch-recursive-update-file(2) -
parallel/test-http-request-join-authorization-headers(2) -
parallel/test-http-server-consumed-timeout(2) -
parallel/test-http2-misbehaving-multiplex(2) -
parallel/test-inspector-async-hook-setup-at-inspect-brk(2) -
parallel/test-inspector-console(2) -
parallel/test-inspector-wait-for-connection(2) -
parallel/test-runner-output(2) -
parallel/test-tls-ticket-cluster(2) -
sequential/test-single-executable-application(2) -
sequential/test-single-executable-application-disable-experimental-sea-warning(2) -
sequential/test-single-executable-application-empty(2) -
wpt/test-webcrypto(2) -
Build timed out (after 120 minutes). Marking the build as failed.(2) -
fatal: '/home/iojs/.ccache/node.shared.reference' does not appear to be a git repository(3)
- 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 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100