Skip to content

[ExecuTorch][WebGPU] Op-tests for the 10 unary activations#21155

Open
JCNTH wants to merge 1 commit into
gh/JCNTH/115/basefrom
gh/JCNTH/115/head
Open

[ExecuTorch][WebGPU] Op-tests for the 10 unary activations#21155
JCNTH wants to merge 1 commit into
gh/JCNTH/115/basefrom
gh/JCNTH/115/head

Conversation

@JCNTH

@JCNTH JCNTH commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

Stack from ghstack (oldest at bottom):

Adds the declarative op-test suites for the unary activations ported in the diff below. Each op gets a torch reference plus a deterministic, range-bounded input so the fp64 golden is well-defined — positive for sqrt/rsqrt, spanning the ±3 knees for hardswish, and reaching the ±15 clamp for tanh — driving the manifest-based Dawn golden.

Key changes:

  • test/ops/test_unary_activations.pyUnaryModule + UNARY_G1 (op name -> torch fn + linspace input gen).
  • test/op_tests/cases.py — registers the 10 suites (a mat + a rank3 case each) via a factory loop, mirroring the existing per-op registration convention.

Differential Revision: D112257657

[ghstack-poisoned]
@pytorch-bot

pytorch-bot Bot commented Jul 22, 2026

Copy link
Copy Markdown

🔗 Helpful Links

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

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:

✅ You can merge normally! (1 Unrelated Failure)

As of commit 40e3cf6 with merge base 266e0dc (image):

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 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 Jul 22, 2026
@github-actions

Copy link
Copy Markdown

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.

This was referenced Jul 22, 2026
@JCNTH
JCNTH requested a review from psiddh July 23, 2026 02:11

@psiddh psiddh left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving full WebGPU stack

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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants