Node Nightly CI #289
SimenBnightly.yml
on: schedule
prepare-yarn-cache-macos
/
Prepare yarn cache for macos-latest
18s
prepare-yarn-cache-ubuntu
/
Prepare yarn cache for ubuntu-latest
26s
prepare-yarn-cache-windows
/
Prepare yarn cache for windows-latest
52s
Matrix: test-macos / test-jasmine
Matrix: test-macos / test
Matrix: test-ubuntu / test-jasmine
Matrix: test-ubuntu / test
Matrix: test-windows / test-jasmine
Matrix: test-windows / test
Notify failed build
4s
Annotations
8 errors and 2 warnings
|
|
|
test-windows / Node nightly on windows-latest (2/4)
Unexpected HTTP response: 500
|
|
|
|
test-macos / Node Nightly on macos-latest using jest-jasmine2 (4/4)
Unexpected HTTP response: 522
|
|
test-windows / Node Nightly on windows-latest using jest-jasmine2 (3/4)
Unexpected HTTP response: 500
|
|
|
|
does not trigger unexpected token error message for regular syntax errors:
e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\unexpected-token'
at rmSync (e2e/Utils.ts:107:8)
at Object.<anonymous> (e2e/__tests__/unexpectedToken.test.ts:16:24)
|
|
notify › does not report --notify flag:
e2e/__tests__/detectOpenHandles.ts#L111
expect(received).toBe(expected) // Object.is equality
Expected: ""
Received: "Jest did not exit one second after the test run has completed.·
'This usually means that there are asynchronous operations that weren't stopped in your tests. Consider running Jest with `--detectOpenHandles` to troubleshoot this issue."
at Object.toBe (e2e/__tests__/detectOpenHandles.ts:111:27)
|
|
test-windows / Node Nightly on windows-latest using jest-jasmine2 (1/4)
Attempt 1 failed. Reason: Child_process exited with error code 1
|
|
test-macos / Node Nightly on macos-latest using jest-jasmine2 (2/4)
Attempt 1 failed. Reason: Child_process exited with error code 1
|