Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion .github/workflows/ci-node.yml
Original file line number Diff line number Diff line change
Expand Up @@ -528,7 +528,9 @@ jobs:
ci-node-${{ runner.os }}-${{ fromJSON(inputs.node-versions || '[""]')[0] || 'nvmrc' }}-

- name: Build what the tests read
run: pnpm run --if-present checks:prepare
run: |
pnpm run --if-present checks:prepare
pnpm run --if-present typecheck

- name: Start services
id: services
Expand Down
16 changes: 9 additions & 7 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -588,13 +588,15 @@ a nightly run never retries a failed test or failed `extra-commands`.

In the `nightly` tier only, after the Node.js jobs, the `Stress` job looks for
tests that pass alone but time out under load. On Linux, with the first
`node-versions` entry or `.nvmrc`, it installs, runs `setup-commands` and
`checks:prepare`, starts the services, then runs `pnpm run test` three times
beside four busy loops per CPU. The loops take CPU time from the test runner's
workers, as a loaded machine does, while the workers keep the count the runner
picks from the CPUs it sees. It fails when any run fails, and its summary
counts the failed runs. A pull request never runs it, and a caller sets nothing
for it.
`node-versions` entry or `.nvmrc`, it installs, runs `setup-commands`,
`checks:prepare` and `typecheck`, starts the services, then runs `pnpm run test`
three times beside four busy loops per CPU. The loops take CPU time from the
test runner's workers, as a loaded machine does, while the workers keep the
count the runner picks from the CPUs it sees. It fails when any run fails, and
its summary counts the failed runs. A pull request never runs it, and a caller
sets nothing for it. It runs no `pnpm run checks`, so `typecheck` gives the
tests the build, such as a `dist/` folder, that `checks` gives them in the
Node.js job.

On a pull request and in the merge queue, each job fetches the target branch
into `origin/<branch>`, such as `origin/main`, and the diff base into the
Expand Down