Skip to content

Qualcomm AI Engine Direct - Remove AIHub Example Scripts#19144

Open
winskuo-quic wants to merge 2 commits intopytorch:mainfrom
CodeLinaro:dev1/winskuo/gh_/aihub_remove_code
Open

Qualcomm AI Engine Direct - Remove AIHub Example Scripts#19144
winskuo-quic wants to merge 2 commits intopytorch:mainfrom
CodeLinaro:dev1/winskuo/gh_/aihub_remove_code

Conversation

@winskuo-quic
Copy link
Copy Markdown
Collaborator

@winskuo-quic winskuo-quic commented Apr 27, 2026

Summary

We will remove AIHUB sample code for now as it is hard to maintain since each released version has different IO's for context binary, and it is hard to create a runner for each version.
This PR removes all python, c++, and CMAKE files
We will still keep logic in backends/qualcomm for aihub in case this feature is needed again in the future.

GH stack:

Test plan

Ensure PR does not break existing internal and external CI

… aihub info under backends/qualcomm/README.md
@pytorch-bot
Copy link
Copy Markdown

pytorch-bot Bot commented Apr 27, 2026

🔗 Helpful Links

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

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:

❌ 3 New Failures, 2 Unrelated Failures

As of commit cdea7fb with merge base bf64fa1 (image):

NEW FAILURES - The following jobs have failed:

BROKEN TRUNK - The following jobs 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 Apr 27, 2026
@winskuo-quic winskuo-quic changed the title Dev1/winskuo/gh /aihub remove code Qualcomm AI Engine Direct - Remove AIHub Example Scripts Apr 27, 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.

@abhinaykukkadapu
Copy link
Copy Markdown
Contributor

@winskuo-quic can you give a bit of context when and why this was introduced, why are we thinking to deprecate, i understand that we need to customize the runner per version and model, but i like the idea of something readily available for our users to get started, may be we can think about the optimum-et (qnn recipe) approach?

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