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

Remove caching from native cargo action #458

Merged
merged 1 commit into from
Dec 8, 2023

Conversation

aaronmondal
Copy link
Member

@aaronmondal aaronmondal commented Dec 8, 2023

If we share caches between workflows, the runners run out of storage. If we separate the caches we have too many of them and keep stepping over GitHub's cache limitations. Remove caching entirely as this workflows doesn't take that long and we need the caches for Bazel and Nix.


This change is Reviewable

If we share caches between workflows, the runners run out of storage. If
we separate the caches we have too many of them and keep stepping over
GitHub's cache limitations. Remove caching entirely as this workflows
doesn't take *that* long and we need the caches for Bazel and Nix.
Copy link
Member

@allada allada left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewable status: 0 of 1 files reviewed, 1 unresolved discussion (waiting on @aaronmondal)


-- commits line 4 at r1:
shall we instead just pay for more storage?

Copy link
Member Author

@aaronmondal aaronmondal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewable status: 0 of 1 files reviewed, 1 unresolved discussion (waiting on @allada)


-- commits line 4 at r1:

Previously, allada (Nathan (Blaise) Bruer) wrote…

shall we instead just pay for more storage?

I think at this point it makes sense to use larger runners. We can't increase the size of the GHA cache, but e.g. having 4 or 8 cores and a few gigs more ram and storage would obsolete any cache issues we have at the moment since things would build fast enough from scratch that we don't need caching anymore.

Copy link
Member

@allada allada left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:lgtm:

Reviewed 1 of 1 files at r1, all commit messages.
Reviewable status: :shipit: complete! all files reviewed, all discussions resolved (waiting on @aaronmondal)


-- commits line 4 at r1:

Previously, aaronmondal (Aaron Siddhartha Mondal) wrote…

I think at this point it makes sense to use larger runners. We can't increase the size of the GHA cache, but e.g. having 4 or 8 cores and a few gigs more ram and storage would obsolete any cache issues we have at the moment since things would build fast enough from scratch that we don't need caching anymore.

Crazy you can't pay for more storage.

@aaronmondal aaronmondal merged commit 4eab282 into TraceMachina:main Dec 8, 2023
21 checks passed
Copy link
Member

@adam-singer adam-singer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed all commit messages.
Reviewable status: :shipit: complete! all files reviewed, all discussions resolved

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.

None yet

3 participants