-
Notifications
You must be signed in to change notification settings - Fork 25.1k
aarch64: cd: test openmp switch from libomp to libgomp #124353
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/124353
Note: Links to docs will display an error until the docs builds have been completed. ❌ 2 New Failures, 7 Unrelated FailuresAs of commit 070ab85 with merge base dca24d7 ( 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 jobs 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. |
The CI failure is not related to this PR, it's coming from int4mm kernel changes, even the aarch64-linux nightly are broken. We will trigger the CI runs for this PR once this issue is fixed. |
The CI failures are because the int4mm fix is not yet reflected to nightly branch. I will trigger CI again tomorrow. |
Hi @atalman , can you please restart the CI runs fresh. When i re-run the jobs, it's still picking the older torch commit that had the in4mm breaks. |
closing the pull request as the change was merged. |
tests this PR# pytorch/builder#1787
Fixes #pytorch/builder#1774