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

ci: remove Magic Nix Cache #745

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

ci: remove Magic Nix Cache #745

wants to merge 1 commit into from

Conversation

danth
Copy link
Owner

@danth danth commented Jan 4, 2025

Due to the large number of derivations we are building, this almost always gets disabled due to rate limits before it's able to fetch anything which isn't already on cache.nixos.org. Rate limiting also spams the log with warnings which are unrelated to the build.

Due to the large number of derivations we are building, this almost
always gets disabled due to rate limits before it's able to fetch
anything which isn't already on cache.nixos.org. Rate limiting also
spams the log with warnings which are unrelated to the build.
Copy link
Collaborator

@trueNAHO trueNAHO left a comment

Choose a reason for hiding this comment

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

Getting lots of rate-limiting failures described in the usage notes. could this be addressed by using an optional alternate github token with a higher rate limit like the one used by nix-installer-action?

-- DeterminateSystems/magic-nix-cache-action#28

@trueNAHO trueNAHO added performance Improvements to or issues about performance backport release-24.11 labels Jan 4, 2025
@trueNAHO
Copy link
Collaborator

trueNAHO commented Jan 5, 2025

Due to the large number of derivations we are building, this almost always gets disabled due to rate limits before it's able to fetch anything which isn't already on cache.nixos.org. Rate limiting also spams the log with warnings which are unrelated to the build.

The main reason we recently hit the rate limit all the time is due to the enormous amount of backports done, which is not very representative of "normal" usage.

FYI, I am currently working on a patch to significantly reduce our CI time by only testing the derivations that are relevant to the PR. This might further reduce rate limit hits.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport release-24.11 performance Improvements to or issues about performance
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants