-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
Improve caching for Community Integration Tests against Pro #9114
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks a lot for jumping on this! I think we have to adjust the restore key a bit, but then this should greatly speed up the community tests in our PRs! 🚀 ⌛
@@ -49,7 +49,6 @@ def my_patch(fn, self, **kwargs): | |||
patched_kwargs = { | |||
**kwargs, | |||
"WaiterConfig": { | |||
# TODO: make these configurable |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change doesn't seem to be related, but if it's on purpose, it's okay to sneak this one in ;)
Motivation
Currently the
Community Integration Tests against Pro
are the slowest part of our community test suite on PRs.In this PR we attempt to reduce the runtime of these tests to get them to a point where we don't have to wait an additional 20+ minutes until the pro tests against community are done for a green pipeline.
The initial commit will currently never find a cache hit since we don't execute the action on master. Additionally the cache key seems to be calculated incorrectly by considering too many files for caching and never actually restored the venv/lib cache, even in a single PR with multiple runs.
Successful caching of the built lambda common packages should already save ~8 minutes.
Changes
DISABLE_BOTO_RETRIES=1
for test executionOutcome
The proper caching of the venv + libs wasn't as impactful as I had initially hoped. It still reduced the total run time by a few (~4) minutes. In combination with the saved 8 minutes ( from the lambda common cache) of the initial test run, a PR's first run of
Community Integration Tests against Pro
should be about ~12 min faster now.