Flakiness Type
Other / Unknown
Name of Job
Install Dependencies
Name of Test
N/A
Link to Test Run
https://github.com/getsentry/sentry-javascript/actions/runs/5445228367/jobs/9904174554?pr=8438
Details
I was just checking out your CI configuration to get inspiration for how to rework the CI at Ghost, and I noticed that cache-hit has been typo'd as cache_hit here:
|
if: steps.cache_dependencies.outputs.cache_hit != 'true' |
https://github.com/actions/cache#outputs names cache-hit as the value
As a result, the yarn command is always executed, even if the cache was hit, which burns quite a bit of CI time
In the linked test run (just a random PR on your repo), you can see the cache was hit but we still executed the yarn
🙂
Flakiness Type
Other / Unknown
Name of Job
Install Dependencies
Name of Test
N/A
Link to Test Run
https://github.com/getsentry/sentry-javascript/actions/runs/5445228367/jobs/9904174554?pr=8438
Details
I was just checking out your CI configuration to get inspiration for how to rework the CI at Ghost, and I noticed that
cache-hithas been typo'd ascache_hithere:sentry-javascript/.github/workflows/build.yml
Line 182 in 16a29c0
https://github.com/actions/cache#outputs names
cache-hitas the valueAs a result, the
yarncommand is always executed, even if the cache was hit, which burns quite a bit of CI timeIn the linked test run (just a random PR on your repo), you can see the cache was hit but we still executed the
yarn🙂