Move test-arm-backend-vkml to OSDC - #23271
Merged
Merged
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/23271
Note: Links to docs will display an error until the docs builds have been completed. ✅ You can merge normally! (1 Unrelated Failure)As of commit 7530fa4 with merge base fb60708 ( 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. |
meta-cla
Bot
added
the
CLA Signed
This PR needs a
|
This job was added after pull.yml was migrated, so it came in against the old template: it was the last `runner: linux.*` and the last `linux_job_v2` caller left in the file. Matches its sibling test-arm-backend-no-driver: v3, `needs: docker-image`, and the hash-pinned image tag rather than the floating `ci-image:<name>` that only v2 resolves. Keeps the 24.04 arm-sdk image, which docker-builds.yml does build. linux.2xlarge.memory is an r5.2xlarge, 8 vCPU / 64 GiB, so mt-l-x86iavx512-8-64 is an exact match rather than a judgement call. Also drops `sudo sysctl fs.inotify.max_user_watches`. Nothing in this job watches files: the three legs run pytest, a cmake/ctest build, and a wrapper that scans a `tee`'d log, and there is no inotify reference anywhere in backends/arm or .ci. It arrived with the job in #22841, which does not mention it in the description or review. It could not have taken effect here in any case -- it is a node-level knob and these pods are not privileged -- so leaving it would only have meant a guaranteed-failing command or a `|| true` implying a dependency that does not exist. Authored with Claude Code.
huydhn
force-pushed
the
osdc/arm-vkml
branch
from
September 30, 2026 05:52
34668ff to
7530fa4
Compare
huydhn
commented
Sep 30, 2026
psiddh
approved these changes
Sep 30, 2026
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Last
runner: linux.*and lastlinux_job_v2caller inpull.yml. The job was added after the file was migrated, so it came in against the old template.needs: docker-image, hash-pinned image tag instead of the floatingci-image:<name>that only v2 resolves. Matches its siblingtest-arm-backend-no-driver. Keeps the 24.04 arm-sdk image, whichdocker-builds.ymlbuilds.linux.2xlarge.memoryis an r5.2xlarge (8 vCPU / 64 GiB), somt-l-x86iavx512-8-64is an exact match.sudo sysctl fs.inotify.max_user_watches=1048576. Nothing in this job watches files — the three legs run pytest, a cmake/ctest build, and a wrapper that scans atee'd log — and there is noinotifyreference anywhere inbackends/armor.ci. It arrived with the job in Arm backend: Enable Vulkan validation layer #22841, which does not mention it in the description or review. It could not have taken effect here regardless: it is a node-level knob and these pods are not privileged.Testing
pull_requestruns all three matrix legs (test_pytest_ops_vkml,test_ootb_tests_vgf,test_runtime_vgf) here.