-
Notifications
You must be signed in to change notification settings - Fork 25.2k
CI: add opt-in aarch64 linux workflow #121284
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/121284
Note: Links to docs will display an error until the docs builds have been completed. ❌ 2 New Failures, 4 Unrelated FailuresAs of commit 49517c3 with merge base a8574a9 ( NEW FAILURES - The following jobs have failed:
FLAKY - The following jobs failed but were likely due to flakiness present on trunk:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
rebased the PR to the latest PyTorch to get tlparse upgrade (to 0.3.7) changes. |
0da4d5d
to
7ee1866
Compare
7044e33
to
0fbce1c
Compare
9cb781e
to
b946187
Compare
@snadampal could you please take a look at failing lint jobs ? |
Had somebody had a chance to figure out what is amiss with sccache? |
@pytorchbot successfully started a revert job. Check the current status here. |
@snadampal your PR has been successfully reverted. |
This reverts commit 32cf04c. Reverted #121284 on behalf of https://github.com/malfet due to Test only changes has not been reverted ([comment](#121284 (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.
If you are updating lint runner please update it for all platforms rather than for one (and if it could not be done for some reason mention it in PR description)
- Do not make changes that would restrict usability for run_test.py for the purposes of CI, as users should be able to run them on their machines without any restrictions specific to CI
- Do not leave the temporary changes in the workflow job (this supposed to be an opt-in workflow but now it runs on every pull, but not on trunk, which is wrong)
And please allow maintainers suggests changes to your PR, otherwise I could have re-landed it myself
The CI summary says 4 unrelated failures and 2 new. But looking at the failure log, it seems all the 6 tests are unrelated, looks flaky. I was able to restart 2 of them, but didn't see any rerun jobs option for the rest. |
@pytorchbot merge -i |
Merge startedYour change will be merged while ignoring the following 6 checks: pull / linux-focal-py3.12-clang10 / test (default, 1, 3, linux.2xlarge), pull / linux-focal-py3.11-clang10 / test (default, 1, 3, linux.2xlarge), pull / linux-focal-py3.8-clang10 / test (default, 1, 3, linux.2xlarge), pull / linux-focal-py3.11-clang10 / test (crossref, 1, 2, linux.2xlarge), pull / linux-focal-py3.8-clang10 / test (crossref, 1, 2, linux.2xlarge), trunk / win-vs2019-cpu-py3 / test (default, 1, 3, windows.4xlarge.nonephemeral) Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
aarch64 linux workflow is triggered for ciflow/aarch64 tags. Pull Request resolved: #121284 Approved by: https://github.com/atalman, https://github.com/malfet
This reverts commit 32cf04c. Reverted pytorch#121284 on behalf of https://github.com/malfet due to Test only changes has not been reverted ([comment](pytorch#121284 (comment)))
Triggered by `ciflow/linux-aarch64` and runs only `test_modules`, `test_mkldnn`, `test_mkldnn_fusion` and `test_openmp` as test for now. TODOS: - Enable sscache for fast CI - Extend to a more reasonable test coverage Pull Request resolved: #121284 Approved by: https://github.com/atalman, https://github.com/malfet
Triggered by
ciflow/linux-aarch64
and runs onlytest_modules
,test_mkldnn
,test_mkldnn_fusion
andtest_openmp
as test for now.TODOS: