added reference material for expressJS #14273
Triggered via pull request
January 3, 2025 03:42
Status
Cancelled
Total duration
11m 28s
Artifacts
–
nodejs.yml
on: pull_request
prepare-yarn-cache-ubuntu
/
Prepare yarn cache for ubuntu-latest
17s
prepare-yarn-cache-macos
/
Prepare yarn cache for macos-latest
28s
prepare-yarn-cache-windows
/
Prepare yarn cache for windows-latest
50s
TypeScript Compatibility
5m 34s
Typecheck Examples and Tests
3m 56s
Lint
1m 42s
Validate Yarn dependencies and constraints
17s
Node LTS on Ubuntu with leak detection
52s
Matrix: test-coverage
Matrix: test-ubuntu
Matrix: test-macos
Matrix: test-windows
Annotations
63 errors and 43 warnings
Node LTS on Ubuntu with leak detection
Process completed with exit code 1.
|
Repl › cli › runs without errors:
undefined#L1
expect(received).toBe(expected) // Object.is equality
Expected: ""
Received: "(node:6098) ExperimentalWarning: CommonJS module /home/runner/work/jest/jest/packages/jest-util/build/index.js is loading ES Module /home/runner/work/jest/jest/jest.config.mjs using require().
Support for loading ES Module in require() is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)"
at Object.toBe (packages/jest-repl/src/__tests__/jest_repl.test.js:31:36)
|
Repl › cli › runs without errors:
undefined#L1
expect(received).toBe(expected) // Object.is equality
Expected: ""
Received: "(node:6992) ExperimentalWarning: CommonJS module /home/runner/work/jest/jest/packages/jest-util/build/index.js is loading ES Module /home/runner/work/jest/jest/jest.config.mjs using require().
Support for loading ES Module in require() is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)"
at Object.toBe (packages/jest-repl/src/__tests__/jest_repl.test.js:31:36)
|
Repl › cli › runs without errors:
undefined#L1
expect(received).toBe(expected) // Object.is equality
Expected: ""
Received: "(node:10895) ExperimentalWarning: CommonJS module /home/runner/work/jest/jest/packages/jest-util/build/index.js is loading ES Module /home/runner/work/jest/jest/jest.config.mjs using require().
Support for loading ES Module in require() is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)"
at Object.toBe (packages/jest-repl/src/__tests__/jest_repl.test.js:31:36)
|
Ubuntu with shard 3/4 / Node LTS using jest-jasmine2
Final attempt failed. Child_process exited with error code 1
|
Repl › cli › runs without errors:
undefined#L1
expect(received).toBe(expected) // Object.is equality
Expected: ""
Received: "(node:6365) ExperimentalWarning: CommonJS module /home/runner/work/jest/jest/packages/jest-util/build/index.js is loading ES Module /home/runner/work/jest/jest/jest.config.mjs using require().
Support for loading ES Module in require() is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)"
at Object.toBe (packages/jest-repl/src/__tests__/jest_repl.test.js:31:36)
|
Repl › cli › runs without errors:
undefined#L1
expect(received).toBe(expected) // Object.is equality
Expected: ""
Received: "(node:7293) ExperimentalWarning: CommonJS module /home/runner/work/jest/jest/packages/jest-util/build/index.js is loading ES Module /home/runner/work/jest/jest/jest.config.mjs using require().
Support for loading ES Module in require() is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)"
at Object.toBe (packages/jest-repl/src/__tests__/jest_repl.test.js:31:36)
|
Repl › cli › runs without errors:
undefined#L1
expect(received).toBe(expected) // Object.is equality
Expected: ""
Received: "(node:11450) ExperimentalWarning: CommonJS module /home/runner/work/jest/jest/packages/jest-util/build/index.js is loading ES Module /home/runner/work/jest/jest/jest.config.mjs using require().
Support for loading ES Module in require() is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)"
at Object.toBe (packages/jest-repl/src/__tests__/jest_repl.test.js:31:36)
|
Node LTS on Ubuntu with coverage (3/4)
Final attempt failed. Child_process exited with error code 1
|
Repl › cli › runs without errors:
undefined#L1
expect(received).toBe(expected) // Object.is equality
Expected: ""
Received: "(node:6370) ExperimentalWarning: CommonJS module /home/runner/work/jest/jest/packages/jest-util/build/index.js is loading ES Module /home/runner/work/jest/jest/jest.config.mjs using require().
Support for loading ES Module in require() is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)"
at Object.toBe (packages/jest-repl/src/__tests__/jest_repl.test.js:31:36)
|
Repl › cli › runs without errors:
undefined#L1
expect(received).toBe(expected) // Object.is equality
Expected: ""
Received: "(node:7262) ExperimentalWarning: CommonJS module /home/runner/work/jest/jest/packages/jest-util/build/index.js is loading ES Module /home/runner/work/jest/jest/jest.config.mjs using require().
Support for loading ES Module in require() is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)"
at Object.toBe (packages/jest-repl/src/__tests__/jest_repl.test.js:31:36)
|
Repl › cli › runs without errors:
undefined#L1
expect(received).toBe(expected) // Object.is equality
Expected: ""
Received: "(node:11375) ExperimentalWarning: CommonJS module /home/runner/work/jest/jest/packages/jest-util/build/index.js is loading ES Module /home/runner/work/jest/jest/jest.config.mjs using require().
Support for loading ES Module in require() is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)"
at Object.toBe (packages/jest-repl/src/__tests__/jest_repl.test.js:31:36)
|
Ubuntu with shard 3/4 / Node v22.x
Final attempt failed. Child_process exited with error code 1
|
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)
|
macOS with shard 3/3 / Node v22.x
Canceling since a higher priority waiting request for 'Node CI-testing_express' exists
|
macOS with shard 3/3 / Node v20.x
Canceling since a higher priority waiting request for 'Node CI-testing_express' exists
|
macOS with shard 3/3 / Node v23.x
Canceling since a higher priority waiting request for 'Node CI-testing_express' exists
|
Windows with shard 3/4 / Node v20.x
Canceling since a higher priority waiting request for 'Node CI-testing_express' exists
|
Windows with shard 3/4 / Node v20.x
The operation was canceled.
|
Windows with shard 3/4 / Node v18.x
Canceling since a higher priority waiting request for 'Node CI-testing_express' exists
|
Windows with shard 3/4 / Node v18.x
The operation was canceled.
|
Windows with shard 4/4 / Node v22.x
Canceling since a higher priority waiting request for 'Node CI-testing_express' exists
|
Windows with shard 4/4 / Node v22.x
The operation was canceled.
|
Windows with shard 3/4 / Node LTS using jest-jasmine2
Canceling since a higher priority waiting request for 'Node CI-testing_express' exists
|
Repl › cli › runs without errors:
undefined#L1
expect(received).toBe(expected) // Object.is equality
Expected: ""
Received: "(node:2452) ExperimentalWarning: CommonJS module D:\\a\\jest\\jest\\packages\\jest-util\\build\\index.js is loading ES Module D:\\a\\jest\\jest\\jest.config.mjs using require().
Support for loading ES Module in require() is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)"
at Object.toBe (packages/jest-repl/src/__tests__/jest_repl.test.js:31:36)
|
Windows with shard 3/4 / Node LTS using jest-jasmine2
The operation was canceled.
|
Windows with shard 2/4 / Node v20.x
Canceling since a higher priority waiting request for 'Node CI-testing_express' exists
|
handles a bad revision for "changedSince":
e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\jest-changed-files-test-dir'
at rmSync (e2e/Utils.ts:107:8)
at Object.<anonymous> (e2e/__tests__/jestChangedFiles.test.ts:61:25)
|
handles a bad revision for "changedSince":
e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\jest-changed-files-test-dir'
at rmSync (e2e/Utils.ts:107:8)
at Object.<anonymous> (e2e/__tests__/jestChangedFiles.test.ts:62:24)
|
gets changed files for hg:
e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\jest-changed-files-test-dir'
at rmSync (e2e/Utils.ts:107:8)
at Object.<anonymous> (e2e/__tests__/jestChangedFiles.test.ts:61:25)
|
gets changed files for hg:
e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\jest-changed-files-test-dir'
at rmSync (e2e/Utils.ts:107:8)
at Object.<anonymous> (e2e/__tests__/jestChangedFiles.test.ts:62:24)
|
monitors only root paths for hg:
e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\jest-changed-files-test-dir'
at rmSync (e2e/Utils.ts:107:8)
at Object.<anonymous> (e2e/__tests__/jestChangedFiles.test.ts:61:25)
|
monitors only root paths for hg:
e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\jest-changed-files-test-dir'
at rmSync (e2e/Utils.ts:107:8)
at Object.<anonymous> (e2e/__tests__/jestChangedFiles.test.ts:62:24)
|
handles a bad revision for "changedSince":
e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\jest-changed-files-test-dir'
at rmSync (e2e/Utils.ts:107:8)
at Object.<anonymous> (e2e/__tests__/jestChangedFiles.test.ts:61:25)
|
handles a bad revision for "changedSince":
e2e/Utils.ts#L107
EBUSY: resource busy or locked, rmdir 'C:\Users\RUNNER~1\AppData\Local\Temp\jest-changed-files-test-dir'
at rmSync (e2e/Utils.ts:107:8)
at Object.<anonymous> (e2e/__tests__/jestChangedFiles.test.ts:62:24)
|
Windows with shard 2/4 / Node v20.x
The operation was canceled.
|
macOS with shard 2/3 / Node v22.x
Canceling since a higher priority waiting request for 'Node CI-testing_express' exists
|
Repl › cli › runs without errors:
undefined#L1
expect(received).toBe(expected) // Object.is equality
Expected: ""
Received: "(node:13101) ExperimentalWarning: CommonJS module /Users/runner/work/jest/jest/packages/jest-util/build/index.js is loading ES Module /Users/runner/work/jest/jest/jest.config.mjs using require().
Support for loading ES Module in require() is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)"
at Object.toBe (packages/jest-repl/src/__tests__/jest_repl.test.js:31:36)
|
Repl › cli › runs without errors:
undefined#L1
expect(received).toBe(expected) // Object.is equality
Expected: ""
Received: "(node:14497) ExperimentalWarning: CommonJS module /Users/runner/work/jest/jest/packages/jest-util/build/index.js is loading ES Module /Users/runner/work/jest/jest/jest.config.mjs using require().
Support for loading ES Module in require() is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)"
at Object.toBe (packages/jest-repl/src/__tests__/jest_repl.test.js:31:36)
|
macOS with shard 2/3 / Node v22.x
The operation was canceled.
|
macOS with shard 3/3 / Node v18.x
Canceling since a higher priority waiting request for 'Node CI-testing_express' exists
|
macOS with shard 3/3 / Node v18.x
The operation was canceled.
|
Windows with shard 3/4 / Node v23.x
Canceling since a higher priority waiting request for 'Node CI-testing_express' exists
|
Windows with shard 3/4 / Node v23.x
The operation was canceled.
|
Windows with shard 4/4 / Node LTS using jest-jasmine2
Canceling since a higher priority waiting request for 'Node CI-testing_express' exists
|
Windows with shard 4/4 / Node LTS using jest-jasmine2
The operation was canceled.
|
macOS with shard 2/3 / Node LTS using jest-jasmine2
Canceling since a higher priority waiting request for 'Node CI-testing_express' exists
|
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)
|
macOS with shard 2/3 / Node LTS using jest-jasmine2
The operation was canceled.
|
Windows with shard 4/4 / Node v16.x
Canceling since a higher priority waiting request for 'Node CI-testing_express' exists
|
Windows with shard 4/4 / Node v16.x
The operation was canceled.
|
Windows with shard 4/4 / Node v18.x
Canceling since a higher priority waiting request for 'Node CI-testing_express' exists
|
Windows with shard 4/4 / Node v18.x
The operation was canceled.
|
Windows with shard 3/4 / Node v22.x
Canceling since a higher priority waiting request for 'Node CI-testing_express' exists
|
Windows with shard 4/4 / Node v20.x
Canceling since a higher priority waiting request for 'Node CI-testing_express' exists
|
Windows with shard 3/4 / Node v22.x
The operation was canceled.
|
Windows with shard 4/4 / Node v20.x
The operation was canceled.
|
Windows with shard 4/4 / Node v23.x
Canceling since a higher priority waiting request for 'Node CI-testing_express' exists
|
Windows with shard 4/4 / Node v23.x
The operation was canceled.
|
macOS with shard 3/3 / Node LTS using jest-jasmine2
Canceling since a higher priority waiting request for 'Node CI-testing_express' exists
|
macOS with shard 3/3 / Node LTS using jest-jasmine2
The operation was canceled.
|
macOS with shard 3/3 / Node v16.x
Canceling since a higher priority waiting request for 'Node CI-testing_express' exists
|
macOS with shard 3/3 / Node v16.x
The operation was canceled.
|
prepare-yarn-cache-ubuntu / Prepare yarn cache for ubuntu-latest
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Validate Yarn dependencies and constraints
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Node LTS on Ubuntu with leak detection
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Lint
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Ubuntu with shard 1/4 / Node v23.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Ubuntu with shard 1/4 / Node v22.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Ubuntu with shard 1/4 / Node v20.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Ubuntu with shard 1/4 / Node LTS using jest-jasmine2
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Ubuntu with shard 1/4 / Node v18.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Ubuntu with shard 1/4 / Node v16.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Node LTS on Ubuntu with coverage (4/4)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Node LTS on Ubuntu with coverage (1/4)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Ubuntu with shard 2/4 / Node v18.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Ubuntu with shard 2/4 / Node LTS using jest-jasmine2
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Node LTS on Ubuntu with coverage (2/4)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Ubuntu with shard 2/4 / Node v22.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Ubuntu with shard 2/4 / Node v20.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Ubuntu with shard 2/4 / Node v16.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Typecheck Examples and Tests
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Ubuntu with shard 2/4 / Node v23.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Ubuntu with shard 3/4 / Node v23.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Ubuntu with shard 4/4 / Node LTS using jest-jasmine2
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Ubuntu with shard 3/4 / Node v16.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Ubuntu with shard 3/4 / Node v20.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Ubuntu with shard 4/4 / Node v18.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Ubuntu with shard 3/4 / Node v18.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Ubuntu with shard 4/4 / Node v16.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Ubuntu with shard 4/4 / Node v23.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Ubuntu with shard 4/4 / Node v22.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Ubuntu with shard 3/4 / Node LTS using jest-jasmine2
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Ubuntu with shard 3/4 / Node LTS using jest-jasmine2
Attempt 1 failed. Reason: Child_process exited with error code 1
|
Ubuntu with shard 3/4 / Node LTS using jest-jasmine2
Attempt 2 failed. Reason: Child_process exited with error code 1
|
TypeScript Compatibility
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Node LTS on Ubuntu with coverage (3/4)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Node LTS on Ubuntu with coverage (3/4)
Attempt 1 failed. Reason: Child_process exited with error code 1
|
Node LTS on Ubuntu with coverage (3/4)
Attempt 2 failed. Reason: Child_process exited with error code 1
|
Ubuntu with shard 4/4 / Node v20.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Ubuntu with shard 3/4 / Node v22.x
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Ubuntu with shard 3/4 / Node v22.x
Attempt 1 failed. Reason: Child_process exited with error code 1
|
Ubuntu with shard 3/4 / Node v22.x
Attempt 2 failed. Reason: Child_process exited with error code 1
|
Windows with shard 1/4 / Node v18.x
Attempt 1 failed. Reason: Child_process exited with error code 1
|
Windows with shard 2/4 / Node v20.x
Attempt 1 failed. Reason: Child_process exited with error code 1
|
macOS with shard 2/3 / Node v22.x
Attempt 1 failed. Reason: Child_process exited with error code 1
|