Skip to content

Resolves Issue #14709 Clarifies date.now() in milliseconds #13048

Resolves Issue #14709 Clarifies date.now() in milliseconds

Resolves Issue #14709 Clarifies date.now() in milliseconds #13048

Triggered via pull request December 25, 2023 11:30
Status Failure
Total duration 2h 6m 21s
Artifacts

nodejs.yml

on: pull_request
prepare-yarn-cache-ubuntu  /  Prepare yarn cache for ubuntu-latest
14s
prepare-yarn-cache-ubuntu / Prepare yarn cache for ubuntu-latest
prepare-yarn-cache-macos  /  Prepare yarn cache for macos-latest
41s
prepare-yarn-cache-macos / Prepare yarn cache for macos-latest
prepare-yarn-cache-windows  /  Prepare yarn cache for windows-latest
37s
prepare-yarn-cache-windows / Prepare yarn cache for windows-latest
TypeScript Compatibility
5m 41s
TypeScript Compatibility
Typecheck Examples and Tests
4m 22s
Typecheck Examples and Tests
Lint
1m 45s
Lint
Validate Yarn dependencies and constraints
17s
Validate Yarn dependencies and constraints
Node LTS on Ubuntu with leak detection
1m 14s
Node LTS on Ubuntu with leak detection
Matrix: test-coverage
Matrix: test-ubuntu
Matrix: test-macos
Matrix: test-windows
Fit to window
Zoom out
Zoom in

Annotations

6 errors
can press "u" to update snapshots: e2e/__tests__/watchModeUpdateSnapshot.test.ts#L50
expect(received).toMatchSnapshot(hint) Snapshot name: `can press "u" to update snapshots: test results 1` - Snapshot - 0 + Received + 1 @@ -14,7 +14,8 @@ | ^ at Object.toMatchSnapshot (__tests__/bar.spec.js:1:35) › 1 snapshot failed. + 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. Snapshot Summary › 1 snapshot failed from 1 test suite. Inspect your code changes or press `u` to update them." at Object.toMatchSnapshot (e2e/__tests__/watchModeUpdateSnapshot.test.ts:50:18)
Windows with shard 1/4 / Node LTS using jest-jasmine2
Process completed with exit code 1.
Node crawler does not pick up symlinked files by default: e2e/Utils.ts#L105
EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\crawl-symlinks-test' at rmSync (e2e/Utils.ts:105:8) at Object.<anonymous> (e2e/__tests__/crawlSymlinks.test.ts:36:10)
Should throw if watchman used with haste.enableSymlinks: e2e/Utils.ts#L105
EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\crawl-symlinks-test' at rmSync (e2e/Utils.ts:105:8) at Object.<anonymous> (e2e/__tests__/crawlSymlinks.test.ts:15:10)
Should throw if watchman used with haste.enableSymlinks: e2e/Utils.ts#L105
EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\crawl-symlinks-test' at rmSync (e2e/Utils.ts:105:8) at Object.<anonymous> (e2e/__tests__/crawlSymlinks.test.ts:36:10)
Windows with shard 4/4 / Node v21.x
Process completed with exit code 1.