-
Notifications
You must be signed in to change notification settings - Fork 32
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
try a new approach to reuse cached builds #67
base: develop
Are you sure you want to change the base?
Conversation
32bd1c2
to
8ab81c4
Compare
With the above algorithm and a modified systemd package, the expected rebuilds are:
These packages all use the bundled Go modules feature, which may be causing spurious rebuilds:
These package rebuilds are a mystery, though at least it's consistent for both x86_64 and aarch64 runners:
|
c5b1630
to
be4a777
Compare
Signed-off-by: Ben Cressey <[email protected]>
Signed-off-by: Ben Cressey <[email protected]>
Signed-off-by: Ben Cressey <[email protected]>
Trying a run with a couple
|
OK, with the
... just the set of packages we expect to be rebuilt! 🎉 |
We're now on a version of Twoliter that supports this hack, so it's getting closer. I realized a shortcoming of the approach here: it only handles file-level modifications that would trigger rebuilds. The environment will be the same for both builds, so we won't do rebuilds for any of the The full set:
Of these, the most interesting is |
Issue number:
Follow-up on #65
Description of changes:
Try a new strategy to force use of cache:
Testing done:
😬
Terms of contribution:
By submitting this pull request, I agree that this contribution is dual-licensed under the terms of both the Apache License, version 2.0, and the MIT license.