chore(ci): trace target directory content for cache troubleshooting #170
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kbakdev
approved these changes
Feb 25, 2023
|
@daniellavoie Yup good idea, merging. |
philpax
pushed a commit
that referenced
this pull request
May 23, 2023
chore(ci): trace target directory content for cache troubleshooting
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
#153 reported a suspicious cache usage increase.
This PR introduces a new step in the build process to output the content of the
targetdirectory after the build. This will help investigate if something is wrong builds after builds.I ran multiple builds with this change and couldn't observe any file change or file increase from the same commits.
Here is an example of the new step in action: https://github.com/daniellavoie/Ambient/actions/runs/4257943674/jobs/7408628309