-
Notifications
You must be signed in to change notification settings - Fork 101
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
Disabling cache in the setup-go steps of CI/CD #8147
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #8147 +/- ##
=======================================
Coverage 59.76% 59.77%
=======================================
Files 590 590
Lines 39487 39487
=======================================
+ Hits 23600 23603 +3
+ Misses 14144 14142 -2
+ Partials 1743 1742 -1 ☔ View full report in Codecov by Sentry. |
76d2fc6
to
233b9b8
Compare
Radius functional test overview
Click here to see the list of tools in the current test run
Test Status⌛ Building Radius and pushing container images for functional tests... |
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.
Can you add some background in the description on why this change is being made, what are the drawbacks of disabling it?
233b9b8
to
39472db
Compare
Radius functional test overview
Click here to see the list of tools in the current test run
Test Status⌛ Building Radius and pushing container images for functional tests... |
Updated the description. |
Signed-off-by: ytimocin <[email protected]>
39472db
to
45dc0b3
Compare
Radius functional test overview
Click here to see the list of tools in the current test run
Test Status⌛ Building Radius and pushing container images for functional tests... |
Description
Because the cache already exists on the GitHub runners we use, disabling cache in the setup-go steps of our CI/CD pipelines is expected solve the issue of seeing bunch of logs that say "cannot open: file exists".
The official documentation of setup-go and the part that is relevant: https://github.com/actions/setup-go#caching-dependency-files-and-build-outputs. This points out that setup-go does caching for us. If the cache is already there, we will get all the logs in our workflows.
There is no disadvantage of this approach, as far as I know, since the cache is already there. I actually ran into this comment that says that disabling cache in setup-go step improved the speed of the said step. We can always update our workflows if we see any other disadvantages.
Our runners: https://github.com/radius-project/radius/actions/runners.
References:
Type of change
Fixes:
Run actions/cache@v4
step in functional tests spams thousands of log lines #7790Contributor checklist
Please verify that the PR meets the following requirements, where applicable: