Node Nightly CI #101
nightly.yml
on: schedule
prepare-yarn-cache-macos
/
Prepare yarn cache for macos-latest
39s
prepare-yarn-cache-ubuntu
/
Prepare yarn cache for ubuntu-latest
19s
prepare-yarn-cache-windows
/
Prepare yarn cache for windows-latest
39s
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
3 errors
can press "t" to filter by test name:
e2e/__tests__/watchModePatterns.test.ts#L70
expect(received).toMatchSnapshot(hint)
Snapshot name: `can press "t" to filter by test name: test results 1`
- Snapshot - 0
+ Received + 2
PASS __tests__/bar.spec.js
+ A worker process has failed to exit gracefully and has been force exited. This is likely caused by tests leaking due to improper teardown. Try running with --detectOpenHandles to find leaks. Active timers can also cause this, ensure that .unref() was called on them.
+
PASS __tests__/foo.spec.js
at Object.toMatchSnapshot (e2e/__tests__/watchModePatterns.test.ts:70:18)
|
globalSetup works with ESM modules:
e2e/Utils.ts#L105
EBUSY: resource busy or locked, rmdir '\\?\C:\Users\RUNNER~1\AppData\Local\Temp\jest-global-setup-rejection'
at rmSync (e2e/Utils.ts:105:8)
at Object.<anonymous> (e2e/__tests__/globalSetup.test.ts:41:10)
|
test-windows / Node Nightly on windows-latest using jest-jasmine2 (1/4)
Process completed with exit code 1.
|