Skip to content

Commit 4d1d2b2

Browse files
borsehuss
authored andcommitted
Auto merge of #11335 - ehuss:space-test, r=epage
Clean more aggressively in CI The Windows x86_64 gnu CI job is running dangerously low on disk space. This PR adds another step to delete test output more aggressively. The test output with x86_64-pc-windows-gnu is nearly 9.5GB. The benchmark step is adding about 1GB of space (unfortunately it is rebuilding cargo, which may be hard to avoid without a workspace). Eventually we should probably look at figuring out how to reduce the amount of disk space used by the testsuite. Perhaps something like #9701 (see comments there). Or, making aggressive changes to the tests themselves. Many tests can probably be changed to use `cargo check` instead of `cargo build` (or maybe even `cargo tree`). We can default to not generating debuginfo. Or perhaps there are other changes to put the tests on a diet.
1 parent e3daada commit 4d1d2b2

File tree

1 file changed

+8
-1
lines changed

1 file changed

+8
-1
lines changed

.github/workflows/main.yml

+8-1
Original file line numberDiff line numberDiff line change
@@ -80,6 +80,13 @@ jobs:
8080

8181
# Deny warnings on CI to avoid warnings getting into the codebase.
8282
- run: cargo test --features 'deny-warnings'
83+
# The testsuite generates a huge amount of data, and fetch-smoke-test was
84+
# running out of disk space.
85+
- name: Clear test output
86+
run: |
87+
df -h
88+
rm -rf target/tmp
89+
df -h
8390
- name: Check operability of rustc invocation with argfile
8491
env:
8592
__CARGO_TEST_FORCE_ARGFILE: 1
@@ -111,7 +118,7 @@ jobs:
111118
cargo check --manifest-path benches/capture/Cargo.toml
112119
# The testsuite generates a huge amount of data, and fetch-smoke-test was
113120
# running out of disk space.
114-
- name: Clear test output
121+
- name: Clear benchmark output
115122
run: |
116123
df -h
117124
rm -rf target/tmp

0 commit comments

Comments
 (0)