-
Notifications
You must be signed in to change notification settings - Fork 12.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compiletest: delete the compiled program once its test is done. #48144
Conversation
(rust_highfive has picked a reviewer for you, use r? to override) |
14fc678
to
adecdd1
Compare
This should save a lot of space on musl test cases (whose standard library are linked statically).
874b882
to
66ee33a
Compare
As you expected, the musl disk usage for run-pass alone drops from 24 GB to 6 GB after applying this. |
Can you check if this means we no longer skip tests that we've already run? Today if you run |
One might want to run the binary manually if the test fails (e.g., under a debugger). Could there be an opt-out, or could this be restricted to only apply to successful tests? |
This isn't a perfect heuristic, but since the amount of run-fail tests is far lower than run-pass tests for now, it should be sufficient to ensure that we don't run into CI limits. This makes it possible to run the test binary manually (e.g., under gdb/lldb) if it failed to attempt to find out why.
@bors r+ p=5 |
📌 Commit 00bce71 has been approved by |
⌛ Testing commit 00bce71 with merge 87d0aeb7ead612d7fd867c5abb6acf72b7e00bc7... |
@bors retry - prioritize beta backports |
⌛ Testing commit 00bce71 with merge 55f2103615af4b52da9d12834f01a6e9ee77195c... |
@bors retry - prioritize beta backports |
Compiletest: delete the compiled program once its test is done. Reduces CI disk usage which prevents #48118 from succeeding.
☀️ Test successful - status-appveyor, status-travis |
Reduces CI disk usage which prevents #48118 from succeeding.