Skip to content

Conversation

@zonglinpeng
Copy link
Contributor

Summary:
Have to ship this as an intermediate step to unblock 3 workstreams on the stack

Modify aten tests to ingress FACTO generated testcases.

  • Each test gets 30~50 cases with good coverage on
    • Optimized VS unoptimized flows
    • dtype switch cases

Known issues:

  • FACTO test class is too big to run on default "heavyweight" CI
    • current skipping the whole target on CI. Will add back once skycastle flow is ready
  • some FACTO is creating inputs that kernels does not handle, mainly dtypes
    • will create exception handling for that.
  • TODO marks the 2 FACTO doesnt work well on the 2 ops.

Differential Revision: D79121474

@pytorch-bot
Copy link

pytorch-bot bot commented Aug 18, 2025

🔗 Helpful Links

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

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

❌ 4 New Failures

As of commit 1bafbd8 with merge base 335de46 (image):

NEW FAILURES - The following jobs have failed:

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 Aug 18, 2025
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D79121474

@github-actions
Copy link

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.

zonglinpeng added a commit to zonglinpeng/executorch that referenced this pull request Aug 18, 2025
Summary:

**Have to ship this as an intermediate step to unblock 3 workstreams on the stack**

Modify aten tests to ingress FACTO generated testcases.
- Each test gets 30~50 cases with good coverage on
  - Optimized VS unoptimized flows
  - dtype switch cases

Known issues:
- FACTO test class is too big to run on default "heavyweight" CI
  - current skipping the whole target on CI. Will add back once skycastle flow is ready
- some FACTO is creating inputs that kernels does not handle, mainly dtypes
  - will create exception handling for that.
- TODO marks the 2 FACTO doesnt work well on the 2 ops.

Differential Revision: D79121474
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D79121474

zonglinpeng added a commit to zonglinpeng/executorch that referenced this pull request Aug 19, 2025
Summary:

**Have to ship this as an intermediate step to unblock 3 workstreams on the stack**

Modify aten tests to ingress FACTO generated testcases.
- Each test gets 30~50 cases with good coverage on
  - Optimized VS unoptimized flows
  - dtype switch cases

Known issues:
- FACTO test class is too big to run on default "heavyweight" CI
  - current skipping the whole target on CI. Will add back once skycastle flow is ready
- some FACTO is creating inputs that kernels does not handle, mainly dtypes
  - will create exception handling for that.
- TODO marks the 2 FACTO doesnt work well on the 2 ops.

Differential Revision: D79121474
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D79121474

zonglinpeng added a commit to zonglinpeng/executorch that referenced this pull request Aug 19, 2025
Summary:
Pull Request resolved: pytorch#13483

**Have to ship this as an intermediate step to unblock 3 workstreams on the stack**

Modify aten tests to ingress FACTO generated testcases.
- Each test gets 30~50 cases with good coverage on
  - Optimized VS unoptimized flows
  - dtype switch cases

Known issues:
- FACTO test class is too big to run on default "heavyweight" CI
  - current skipping the whole target on CI. Will add back once skycastle flow is ready
- some FACTO is creating inputs that kernels does not handle, mainly dtypes
  - will create exception handling for that.
- TODO marks the 2 FACTO doesnt work well on the 2 ops.

Differential Revision: D79121474
zonglinpeng added a commit to zonglinpeng/executorch that referenced this pull request Aug 19, 2025
Summary:

**Have to ship this as an intermediate step to unblock 3 workstreams on the stack**

Modify aten tests to ingress FACTO generated testcases.
- Each test gets 30~50 cases with good coverage on
  - Optimized VS unoptimized flows
  - dtype switch cases

Known issues:
- FACTO test class is too big to run on default "heavyweight" CI
  - current skipping the whole target on CI. Will add back once skycastle flow is ready
- some FACTO is creating inputs that kernels does not handle, mainly dtypes
  - will create exception handling for that.
- TODO marks the 2 FACTO doesnt work well on the 2 ops.

Reviewed By: manuelcandales

Differential Revision: D79121474
zonglinpeng added a commit to zonglinpeng/executorch that referenced this pull request Aug 19, 2025
Summary:

**Have to ship this as an intermediate step to unblock 3 workstreams on the stack**

Modify aten tests to ingress FACTO generated testcases.
- Each test gets 30~50 cases with good coverage on
  - Optimized VS unoptimized flows
  - dtype switch cases

Known issues:
- FACTO test class is too big to run on default "heavyweight" CI
  - current skipping the whole target on CI. Will add back once skycastle flow is ready
- some FACTO is creating inputs that kernels does not handle, mainly dtypes
  - will create exception handling for that.
- TODO marks the 2 FACTO doesnt work well on the 2 ops.

Reviewed By: manuelcandales, hsharma35

Differential Revision: D79121474
zonglinpeng added a commit to zonglinpeng/executorch that referenced this pull request Aug 20, 2025
Summary:

**Have to ship this as an intermediate step to unblock 3 workstreams on the stack**

Modify aten tests to ingress FACTO generated testcases.
- Each test gets 30~50 cases with good coverage on
  - Optimized VS unoptimized flows
  - dtype switch cases

Known issues:
- FACTO test class is too big to run on default "heavyweight" CI
  - current skipping the whole target on CI. Will add back once skycastle flow is ready
- some FACTO is creating inputs that kernels does not handle, mainly dtypes
  - will create exception handling for that.
- TODO marks the 2 FACTO doesnt work well on the 2 ops.

Reviewed By: manuelcandales, hsharma35

Differential Revision: D79121474
zonglinpeng added a commit to zonglinpeng/executorch that referenced this pull request Aug 20, 2025
Summary:

**Have to ship this as an intermediate step to unblock 3 workstreams on the stack**

Modify aten tests to ingress FACTO generated testcases.
- Each test gets 30~50 cases with good coverage on
  - Optimized VS unoptimized flows
  - dtype switch cases

Known issues:
- FACTO test class is too big to run on default "heavyweight" CI
  - current skipping the whole target on CI. Will add back once skycastle flow is ready
- some FACTO is creating inputs that kernels does not handle, mainly dtypes
  - will create exception handling for that.
- TODO marks the 2 FACTO doesnt work well on the 2 ops.

Reviewed By: manuelcandales, hsharma35

Differential Revision: D79121474
Summary:

**Have to ship this as an intermediate step to unblock 3 workstreams on the stack**

Modify aten tests to ingress FACTO generated testcases.
- Each test gets 30~50 cases with good coverage on
  - Optimized VS unoptimized flows
  - dtype switch cases

Known issues:
- FACTO test class is too big to run on default "heavyweight" CI
  - current skipping the whole target on CI. Will add back once skycastle flow is ready
- some FACTO is creating inputs that kernels does not handle, mainly dtypes
  - will create exception handling for that.
- TODO marks the 2 FACTO doesnt work well on the 2 ops.

Reviewed By: manuelcandales, hsharma35

Differential Revision: D79121474
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D79121474

zonglinpeng added a commit to zonglinpeng/executorch that referenced this pull request Aug 21, 2025
Summary:

**Have to ship this as an intermediate step to unblock 3 workstreams on the stack**

Modify aten tests to ingress FACTO generated testcases.
- Each test gets 30~50 cases with good coverage on
  - Optimized VS unoptimized flows
  - dtype switch cases

Known issues:
- FACTO test class is too big to run on default "heavyweight" CI
  - current skipping the whole target on CI. Will add back once skycastle flow is ready
- some FACTO is creating inputs that kernels does not handle, mainly dtypes
  - will create exception handling for that.
- TODO marks the 2 FACTO doesnt work well on the 2 ops.

Reviewed By: manuelcandales, hsharma35

Differential Revision: D79121474
@facebook-github-bot facebook-github-bot merged commit 14bf790 into pytorch:main Aug 23, 2025
100 of 106 checks passed
agrima1304 pushed a commit to agrima1304/executorch that referenced this pull request Aug 26, 2025
Differential Revision: D79121474

Pull Request resolved: pytorch#13483
kimishpatel pushed a commit that referenced this pull request Sep 2, 2025
Differential Revision: D79121474

Pull Request resolved: #13483
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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants