-
Notifications
You must be signed in to change notification settings - Fork 24.6k
Set bash shell on Windows #128854
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
Set bash shell on Windows #128854
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/128854
Note: Links to docs will display an error until the docs builds have been completed. ❗ 1 Active SEVsThere are 1 currently active SEVs. If your PR is affected, please view them below: ✅ No FailuresAs of commit b2b39c8 with merge base c6b180a ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
I'll land this once windows build and test jobs finish successfully |
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.
LGTM, should we specify it as default one for the platform?
@pytorchbot merge -f 'CI-only fix. Force merge to fix trunk. Lint and windows jobs have passed' |
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 |
Has #124613 been tested with Windows AMI before merging? |
Fixes the issue with AMI build when Miniconda variables in profile where overwritten by `` Install-Choco.ps1 `` Fixes the issue with Windows AMI: pytorch/pytorch#128854
Attempt to fix the missing python3 command on the new Windows AMI https://github.com/pytorch/pytorch/actions/runs/9551494945/job/26325922503. I added the logic to copy python to python3 to make the command available, it worked with the previous AMI, but start to fail now and the cause is not clear (maybe it's not the AMI, but a new GitHub runner version)