-
Notifications
You must be signed in to change notification settings - Fork 24.3k
[Do not revert] Re-enable Mac testing #142270
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/142270
Note: Links to docs will display an error until the docs builds have been completed. ❌ 2 New Failures, 3 Unrelated FailuresAs of commit 544e7cc with merge base cca33d5 ( NEW FAILURES - The following jobs have failed:
FLAKY - The following jobs failed but were likely due to flakiness present on trunk:
BROKEN TRUNK - The following job failed but were present on the merge base:👉 Rebase onto the `viable/strict` branch to avoid these failures
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
✅ Deploy Preview for chimerical-cranachan-793287 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
@pytorchbot rebase -b main |
@pytorchbot started a rebase job onto refs/remotes/origin/main. Check the current status here |
Successfully rebased |
c248e83
to
0b1f601
Compare
@pytorchbot merge -f "Re-enable testing" |
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 |
See #142270 for additional info. Make all mac default shard tests run with keep going / continue on error so we can see all the test failures. Red signal will show up later, but you can see failing tests mid run on HUD by clicking the additional test failures button After the job is finished, searching for "consistently: " in the logs will find the failed tests Pull Request resolved: #142421 Approved by: https://github.com/malfet Co-authored-by: Nikita Shulga <2453524+malfet@users.noreply.github.com>
The bash script modification in pytorch#135386 results in tests on mac in default shard not running. This PR is expected to cause test failures, but we need to start getting signal, so landing with known failures Pull Request resolved: pytorch#142270 Approved by: https://github.com/malfet, https://github.com/seemethere, https://github.com/atalman Co-authored-by: Nikita Shulga <2453524+malfet@users.noreply.github.com>
) See pytorch#142270 for additional info. Make all mac default shard tests run with keep going / continue on error so we can see all the test failures. Red signal will show up later, but you can see failing tests mid run on HUD by clicking the additional test failures button After the job is finished, searching for "consistently: " in the logs will find the failed tests Pull Request resolved: pytorch#142421 Approved by: https://github.com/malfet Co-authored-by: Nikita Shulga <2453524+malfet@users.noreply.github.com>
The bash script modification in pytorch#135386 results in tests on mac in default shard not running. This PR is expected to cause test failures, but we need to start getting signal, so landing with known failures Pull Request resolved: pytorch#142270 Approved by: https://github.com/malfet, https://github.com/seemethere, https://github.com/atalman Co-authored-by: Nikita Shulga <2453524+malfet@users.noreply.github.com>
) See pytorch#142270 for additional info. Make all mac default shard tests run with keep going / continue on error so we can see all the test failures. Red signal will show up later, but you can see failing tests mid run on HUD by clicking the additional test failures button After the job is finished, searching for "consistently: " in the logs will find the failed tests Pull Request resolved: pytorch#142421 Approved by: https://github.com/malfet Co-authored-by: Nikita Shulga <2453524+malfet@users.noreply.github.com>
The bash script modification in #135386 results in tests on mac in default shard not running.
This PR is expected to cause test failures, but we need to start getting signal, so landing with known failures
cc @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @ipiszy @yf225 @chenyang78 @kadeng @muchulee8 @ColinPeppler @amjames @desertfire @chauhang @aakhundov