Skip to content

Drop cache action restore-keys to prevent bad cache hits#417

Merged
dataflake merged 2 commits intomasterfrom
dataflake/prevent_cache_mixups
May 5, 2026
Merged

Drop cache action restore-keys to prevent bad cache hits#417
dataflake merged 2 commits intomasterfrom
dataflake/prevent_cache_mixups

Conversation

@dataflake
Copy link
Copy Markdown
Member

As observed in several places like zopefoundation/zope.security#128 the restore-keys setting can lead to wrong caches used.

The line break at the end of the file is on purpose to reduce visual clutter in the resulting tests configuration.

@dataflake dataflake requested review from icemac and mauritsvanrees May 1, 2026 07:50
@dataflake dataflake self-assigned this May 1, 2026
@coveralls
Copy link
Copy Markdown

Coverage Report for CI Build 25207206589

Coverage remained the same at 14.851%

Details

  • Coverage remained the same as the base build.
  • Patch coverage: No coverable lines changed in this PR.
  • No coverage regressions found.

Uncovered Changes

No uncovered changes found.

Coverage Regressions

No coverage regressions found.


Coverage Stats

Coverage Status
Relevant Lines: 1265
Covered Lines: 250
Line Coverage: 19.76%
Relevant Branches: 452
Covered Branches: 5
Branch Coverage: 1.11%
Branches in Coverage %: Yes
Coverage Strength: 0.2 hits per line

💛 - Coveralls

Copy link
Copy Markdown
Member

@icemac icemac left a comment

Choose a reason for hiding this comment

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

Yes, let's get rid of the restore keys I am not sure why we had them in the first place. Might be helpful in Python only project but even there probably not always.

@dataflake
Copy link
Copy Markdown
Member Author

I bet it was simply copy-pasted from example code in the cache action documentation.

@dataflake dataflake merged commit 4a3c19b into master May 5, 2026
14 checks passed
@dataflake dataflake deleted the dataflake/prevent_cache_mixups branch May 5, 2026 06:43
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.

3 participants