Skip to content

Use gpu_cpp_unittest for slim CUDA guard tests#19378

Open
rascani wants to merge 1 commit intopytorch:mainfrom
rascani:export-D104297130
Open

Use gpu_cpp_unittest for slim CUDA guard tests#19378
rascani wants to merge 1 commit intopytorch:mainfrom
rascani:export-D104297130

Conversation

@rascani
Copy link
Copy Markdown
Contributor

@rascani rascani commented May 7, 2026

Summary:
The test_cuda_guard and test_cuda_stream_guard targets in executorch/backends/aoti/slim/cuda/test/ skip at runtime via GTEST_SKIP() in SetUp() when no CUDA device is available. On CPU-only sandcastle hosts they emit SKIPPED on every run, never accumulate a PASS record, and TestInfra flags them with a CONTINUOUS_STATE violation, marking them DISABLED_FAILING and contributing 15 phantom failures to the ai_infra_mobile_platform oncall feed.

Switch the wrapper macro from cpp_unittest to gpu_cpp_unittest. The GPU wrapper expands the kwargs through gpu_common.convert_cpp_args, which adds CI labels and the appropriate select_accelerator() so Buck marks the targets incompatible with non-GPU configurations. TestInfra then omits them from CPU schedules entirely instead of running and reporting SKIPPED.

Authored with Claude.

Differential Revision: D104297130

Summary:
The `test_cuda_guard` and `test_cuda_stream_guard` targets in `executorch/backends/aoti/slim/cuda/test/` skip at runtime via `GTEST_SKIP()` in `SetUp()` when no CUDA device is available. On CPU-only sandcastle hosts they emit SKIPPED on every run, never accumulate a PASS record, and TestInfra flags them with a `CONTINUOUS_STATE` violation, marking them DISABLED_FAILING and contributing 15 phantom failures to the ai_infra_mobile_platform oncall feed.

Switch the wrapper macro from `cpp_unittest` to `gpu_cpp_unittest`. The GPU wrapper expands the kwargs through `gpu_common.convert_cpp_args`, which adds CI labels and the appropriate `select_accelerator()` so Buck marks the targets incompatible with non-GPU configurations. TestInfra then omits them from CPU schedules entirely instead of running and reporting SKIPPED.

Authored with Claude.

Differential Revision: D104297130
@pytorch-bot
Copy link
Copy Markdown

pytorch-bot Bot commented May 7, 2026

🔗 Helpful Links

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

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

❌ 1 New Failure

As of commit a8812b4 with merge base fa857bd (image):

NEW FAILURE - The following job has failed:

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

@meta-codesync
Copy link
Copy Markdown
Contributor

meta-codesync Bot commented May 7, 2026

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

@meta-cla meta-cla Bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label May 7, 2026
@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 7, 2026

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.

@rascani rascani requested a review from Gasoonjia May 7, 2026 22:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. fb-exported meta-exported

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant