You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
not ok 679 parallel/test-runner-watch-mode
---
duration_ms: 4692.99100
severity: fail
exitcode: 1
stack: |-
TAP version 13
# Subtest: test runner watch mode
# Subtest: should run tests repeatedly
ok 1 - should run tests repeatedly
---
duration_ms: 1597.4058
...
not ok 943 sequential/test-single-executable-application-snapshot-and-code-cache
---
duration_ms: 19060.87800
severity: fail
exitcode: 1
stack: |-
[process 1904]: --- stderr ---
Aborted()
[process 1904]: --- stdout ---
�[36mStart injection of NODE_SEA_BLOB in C:\workspace\node-test-binary-windows-js-suites\node\test\.tmp.942\sea.exe...�[0m
�[31mError: Aborted(). Build with -sASSERTIONS for more info.�[0m
[process 1904]: status = 1, signal = null
C:\workspace\node-test-binary-windows-js-suites\node\test\common\child_process.js:86
throw new Error(`${failures.join('\n')}`);
^
Error: - process terminated with status 1, expected 0
at logAndThrow (C:\workspace\node-test-binary-windows-js-suites\node\test\common\child_process.js:86:11)
at expectSyncExit (C:\workspace\node-test-binary-windows-js-suites\node\test\common\child_process.js:91:5)
at spawnSyncAndExitWithoutError (C:\workspace\node-test-binary-windows-js-suites\...
not ok 2944 parallel/test-inspector-debug-end
---
duration_ms: 120088.62600
severity: fail
exitcode: -15
stack: |-
timeout
Test there's no crash stopping server that was not started
Test there's no crash stopping server without connecting
[err] Debugger listening on ws://127.0.0.1:37909/9e6fda0c-c60f-454f-a11e-a5f2c5f1b9f5
[err] For help, see: https://nodejs.org/en/docs/inspector
[err]
Test there's no crash stopping server after connecting
[test] Connecting to a child Node process
[test] Testing /json/list
[err] Debugger listening on ws://127.0.0.1:36641/e189ff87-b900-4dcd-8e80-64a3af1f557c
[err] For help, see: https://nodejs.org/en/docs/inspector
[err]
[err] Debugger attached.
[err]
...
error: The last gc run reported the following. Please correct the root cause
and remove .git/gc.log.
Automatic cleanup will not be performed until the file is removed.
warning: There are too many unreachable loose objects; run 'git prune' to remove them.
Reason
fatal: '/home/iojs/.ccache/node.shared.reference' does not appear to be a git repository
Failures in node-test-pull-request/53822 to node-test-pull-request/53918 that failed 2 or more PRs
(Generated with
ncu-ci walk pr --stats=true --markdown /home/runner/work/reliability/reliability/results.md
)JSTest Failure
parallel/test-runner-watch-mode
Example
parallel/test-tls-socket-close
Example
sequential/test-single-executable-application-snapshot-and-code-cache
Example
sequential/test-tls-psk-client
Example
parallel/test-crypto-dh-generate-keys
Example
parallel/test-debugger-break
Example
parallel/test-inspector-debug-end
Example
parallel/test-runner-output
Example
parallel/test-tls-ticket-cluster
Example
sequential/test-cli-syntax-require
Example
sequential/test-http-regr-gh-2928
Example
Jenkins Failure
CCTest Failure
Git Failure
Build Failure
Failed to trigger sub builds
Example
error: The last gc run reported the following. Please correct the root cause
Example
fatal: '/home/iojs/.ccache/node.shared.reference' does not appear to be a git repository
Example
Progress
parallel/test-runner-watch-mode
(5)parallel/test-tls-socket-close
(5)sequential/test-single-executable-application-snapshot-and-code-cache
(5)sequential/test-tls-psk-client
(3)parallel/test-crypto-dh-generate-keys
(2)parallel/test-debugger-break
(2)parallel/test-inspector-debug-end
(2)parallel/test-runner-output
(2)parallel/test-tls-ticket-cluster
(2)sequential/test-cli-syntax-require
(2)sequential/test-http-regr-gh-2928
(2)Failed to trigger sub builds
(2)error: The last gc run reported the following. Please correct the root cause
(2)fatal: '/home/iojs/.ccache/node.shared.reference' does not appear to be a git repository
(2)The text was updated successfully, but these errors were encountered: