256a91019a
Follow on from #37851 This may reduce CI time by running doctests in parallel with other tests. It also makes it easier to find the results. Example output: https://github.com/zed-industries/zed/actions/runs/17698218116/job/50300398669?pr=38111 At least on this run, the doctests finished before the main Linux tests, which makes sense because there are many fewer doctests. So they should not be on the critical path. Thanks @maxdeviant for the prompt. <img width="615" height="513" alt="image" src="https://github.com/user-attachments/assets/bcafa636-a68c-4602-97f4-61f7904e6a7b" /> Release Notes: - N/A
24 lines
595 B
YAML
24 lines
595 B
YAML
name: "Run tests"
|
|
description: "Runs the tests"
|
|
|
|
runs:
|
|
using: "composite"
|
|
steps:
|
|
- name: Install Rust
|
|
shell: bash -euxo pipefail {0}
|
|
run: |
|
|
cargo install cargo-nextest --locked
|
|
|
|
- name: Install Node
|
|
uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4
|
|
with:
|
|
node-version: "18"
|
|
|
|
- name: Limit target directory size
|
|
shell: bash -euxo pipefail {0}
|
|
run: script/clear-target-dir-if-larger-than 100
|
|
|
|
- name: Run tests
|
|
shell: bash -euxo pipefail {0}
|
|
run: cargo nextest run --workspace --no-fail-fast
|