Disable VGF tests (#18899)

[digantdesai]

Summary:

Temporary to unblock diff train.

Differential Revision: D100808720

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/18899

• 📄 Preview Python docs built from this PR

Note: Links to docs will display an error until the docs builds have been completed.

❗ 1 Active SEVs

There are 1 currently active SEVs. If your PR is affected, please view them below:

• Rolling out OSDC (ARC) runners on pull workflow for PyTorch trunk commits

❌ 1 New Failure, 2 Unrelated Failures

As of commit 3315692 with merge base 87e65ac ():

NEW FAILURE - The following job has failed:

• pull / test-coreml-bc-macos (macos-m2-stable) / macos-job (gh)
  RuntimeError: Command bash /Users/ec2-user/runner/_work/_temp/exec_script failed with exit code 128

BROKEN TRUNK - The following jobs failed but were present on the merge base:

👉 Rebase onto the `viable/strict` branch to avoid these failures

• pull / unittest / windows / windows-job (gh) (trunk failure)
  ##[error]The operation was canceled.
• pull / unittest-editable / windows / windows-job (gh) (trunk failure)
  ##[error]The operation was canceled.

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[meta-codesync]

@digantdesai has exported this pull request. If you are a Meta employee, you can view the originating Diff in D100808720.

[github-actions]

This PR needs a release notes: label

If your change should be included in the release notes (i.e. would users of this library care about this change?), please use a label starting with release notes:. This helps us keep track and include your important work in the next release notes.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "release notes: none"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.

[Copilot]

Pull request overview

Temporarily disables VGF-related ARM backend test setup to avoid Sandcastle seccomp-related crashes and unblock the diff train.

Changes:

• Disabled VGF enablement flag in ARM test target generation (removes VGF-specific env/preloads).
• Added skip_on_mode_mac = True to ARM pytest targets.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The inline comment suggests this is a Sandcastle-specific seccomp issue, but _ENABLE_VGF = False disables VGF-related env/preload deps for all builds. Either scope this flag to the environment(s) affected (e.g., Sandcastle-only) or update the comment to reflect that this is a global disable, and add a TODO/link to the tracking task/issue for re-enabling so it doesn’t become permanent by accident.

Suggested change

	_ENABLE_VGF = False # Disabled: memfd_create blocked by seccomp on Sandcastle causes segfaults before Python pre-flight check can run
	# Disabled globally as a temporary workaround.
	# Root cause: on Sandcastle, seccomp blocks `memfd_create`, which causes
	# segfaults before the Python pre-flight check can run.
	# TODO: Re-enable VGF once the Sandcastle seccomp issue is resolved, or
	# scope this workaround to Sandcastle-only so other environments can use VGF.
	_ENABLE_VGF = False

[Copilot]

skip_on_mode_mac = True is applied to every python_pytest target generated in this loop, which effectively makes all ARM pytest targets opt out of mac mode. This isn’t mentioned in the PR description (which focuses on disabling VGF tests); please either document the rationale here / in the PR description, or narrow the skip to only the specific tests/mode(s) that actually need it.