Uh oh!
There was an error while loading. Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork 16
Open
Description
Failures in node-test-pull-request/45970 to node-test-pull-request/46064 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-19 00:16 | 1 | 12 | 45 | 1 | 41 | 12.24% |
JSTest Failure
| Reason | node-api/test_threadsafe_function/test |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 4 (nodejs/node#44201, nodejs/node#44204, nodejs/node#44229, nodejs/node#44269) |
| Appeared | test-equinix-ubuntu2004_container-armv7l-1 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/45973/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/46062/ |
Example
not ok 104 node-api/test_threadsafe_function/test --- duration_ms: 360.108 severity: fail exitcode: -15 stack: |- timeout ... | Reason | parallel/test-vm-timeout-escape-promise-2 |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 4 (nodejs/node#44217, nodejs/node#44216, nodejs/node#44220, nodejs/node#44203) |
| Appeared | test-azure_msft-win10_vs2019-x64-1, test-azure_msft-win10_vs2019-x64-4, test-azure_msft-win10_vs2019-x64-3 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/46009/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/46055/ |
Example
not ok 750 parallel/test-vm-timeout-escape-promise-2 --- duration_ms: 0.405 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 | sequential/test-http-regr-gh-2928 |
|---|---|
| Type | JS_TEST_FAILURE |
| Failed PR | 3 (nodejs/node#44233, nodejs/node#44180, nodejs/node#44234) |
| Appeared | test-digitalocean-freebsd12-x64-2 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/46020/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/46042/ |
Example
not ok 3643 sequential/test-http-regr-gh-2928 --- duration_ms: 120.92 severity: fail exitcode: -15 stack: |- timeout .+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+.+. ... Jenkins Failure
| Reason | Backing channel 'JNLP4-connect connection from ... is disconnected. |
|---|---|
| Type | JENKINS_FAILURE |
| Failed PR | 5 (nodejs/node#44095, nodejs/node#44204, nodejs/node#44223, nodejs/node#44234, nodejs/node#44248) |
| Appeared | test-digitalocean-freebsd12-x64-1, test-digitalocean-freebsd12-x64-2, test-orka-macos11-x64-2, test-nearform-macos11.0-arm64-1, test-nearform-macos10.15-x64-1 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/45980/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/46041/ |
Example
java.io.IOException: Backing channel 'JNLP4-connect connection from 45.55.90.237/45.55.90.237:30532' 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 (nodejs/node#44169, nodejs/node#44201, nodejs/node#44223, nodejs/node#44229) |
| Appeared | test-digitalocean-freebsd12-x64-1, test-orka-macos10.15-x64-2, test-nearform-macos11.0-arm64-1, test-nearform-macos10.15-x64-1 |
| First CI | https://ci.nodejs.org/job/node-test-pull-request/45981/ |
| Last CI | https://ci.nodejs.org/job/node-test-pull-request/46021/ |
Example
ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for node-test-commit-freebsd/nodes=freebsd12-x64 #45426 Collecting metadata... Metadata collection done. Notifying upstream projects of job completion Finished: FAILURE undefined
Example
Unknown Progress
node-api/test_threadsafe_function/test(4)parallel/test-vm-timeout-escape-promise-2(4)sequential/test-http-regr-gh-2928(3)Backing channel 'JNLP4-connect connection from ... is disconnected.(5)ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for ...(4)Unknown(11)
Metadata
Metadata
Assignees
Labels
No labels