-
Notifications
You must be signed in to change notification settings - Fork 9
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
workflow troubleshooting #3361
workflow troubleshooting #3361
Conversation
looking at some previous runs, this one for example, post-run took 6 minutes |
|
Nice! If I'm understanding correctly, 8782930 looks like it also resolved it by clearing up space on the VM? This feels like the least change to get things working. (I believe that the Preference is for the first solution 8782930, since it preserves caching. But if you do go with the |
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.
Preference for solution in prior commit, unless I'm missing some consideration :)
This reverts commit 9d884a4.
aye aye |
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!
workflows please cooperate now! |
trying to troubleshooting the docker/e2e issues...
okay, each commit represents a solution to the recent issue of workflows for smoketest and cypress
both appear to resolve the issue, I am partial to the latter since I do not know if there is a purpose to the postrun save, disabling it solves the issue for sure and shaves some time off test runs
related to docker layer caching action: satackey/action-docker-layer-caching#139 (comment)
per conversation here
https://talent-cloud.slack.com/archives/C0259G6KXJ6/p1657839973910039