Skip to content

Run schedule CI more often due to link cache #2218

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

Closed
wants to merge 1 commit into from

Conversation

marxin
Copy link
Contributor

@marxin marxin commented Jan 22, 2025

This attempt runs CI job more often so that the chunk of expired links to github.com is relatively small and so it's going to prevent: 429 Too Many Requests error.

CC: @camelid @Kobzol

@camelid
Copy link
Member

camelid commented Jan 25, 2025

Thanks! I wonder if it would be better to just make the cache last longer instead though. Any thoughts on that? On a related note, do you know if the cache also includes links that were in the previous cache?

@marxin
Copy link
Contributor Author

marxin commented Jan 25, 2025

Oh, I finally understand what's wrong with the cache reuse:

Failed to save: Unable to reserve cache with key linkcheck--0.8.1, another job may be creating this cache. More details: Cache already exists. Scope: refs/heads/master, Key: linkcheck--0.8.1, Version: 33f8fd511bed9c91c40778bc5c27cb58425caa894ab50f9c5705d83cb78660e0
Warning: Cache save failed.

Let me prepare a separate PR, where I am going to fix it.

@marxin marxin closed this Jan 25, 2025
@marxin
Copy link
Contributor Author

marxin commented Jan 25, 2025

Fix: #2223

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