-
Notifications
You must be signed in to change notification settings - Fork 26.3k
[BE] [CI] Skip clean gha workspace if CI is running in a container for checkout-pytorch #137168
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
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/137168
Note: Links to docs will display an error until the docs builds have been completed. ❌ 5 New FailuresAs of commit a876154 with merge base 52d29a2 ( NEW FAILURES - The following jobs have failed:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
huydhn
left a comment
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.
The change LGTM code-wise but I am curious why cleaning up the local workspace needs to be skipped here. An explanation on the PR description would be great.
|
@pytorchbot merge -f "stuck signals" |
Merge startedYour change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Please use Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
For the reusable action checkout-pytorch, skips cleaning workspace when running from a container environment.
The motivation for this change is twofold:
-v. This prevents the possibility of runningrm -rand deleting this mount path;