Skip to content
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

Add maximize-build-space action #158

Closed
wants to merge 3 commits into from
Closed

Conversation

JoshOrndorff
Copy link
Contributor

inspired by cdaa8c7

This PR adds this simple magical (hacky) github action which gets us enough extra disk space to build the massive polkadot crates.

@JoshOrndorff
Copy link
Contributor Author

JoshOrndorff commented Dec 14, 2023

With --release

Running cargo clean && cargo nextest run --release && du -h locally shows that my Tuxedo directory totals to 11G after all tests run. That seems like it should be good enough. Maybe even enough to fit in the 14GB that we have without the magic action.

WithOUT --release
Running cargo clean && cargo nextest run && du -h locally shows that my Tuxedo directory totals to 25G after all tests run. That is more than double, but seems like it still should have fit into the magically expanded disk space.

Anyway, the CI job is running with --release now. I guess we'll see shortly.

@muraca
Copy link
Collaborator

muraca commented Dec 14, 2023

The action did not solve the problem we had, cargo gets stuck on some windows crate.
Thanks for testing my intuition with --release and pointing out it was indeed a good solution.

@muraca muraca closed this Dec 14, 2023
@muraca muraca mentioned this pull request Dec 14, 2023
@JoshOrndorff
Copy link
Contributor Author

cargo gets stuck on some windows crate

How did you determine that. I can't see any logs from the failed jobs. (except for the first few steps which succeeded)

@muraca
Copy link
Collaborator

muraca commented Dec 14, 2023

cargo gets stuck on some windows crate

How did you determine that. I can't see any logs from the failed jobs. (except for the first few steps which succeeded)

I ran the action and looked at the logs in real time for 30 minutes. I don't recommend doing it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants