Skip to content

Add workflow to export models and upload to S3 - #16733

Closed
kirklandsign wants to merge 3 commits into
mainfrom
export-models
Closed

kirklandsign wants to merge 3 commits into
mainfrom
export-models

Conversation

@kirklandsign

Copy link
Copy Markdown
Contributor

No description provided.

This workflow exports ExecutorTorch models and uploads them to S3 for
easy access. It can be triggered manually from the Actions webpage or
runs automatically on a daily schedule.

Supported models include in-tree models (mv3, mv2, ic4, resnet50, etc.)
and HuggingFace models (Llama, Qwen, SmolLM, OLMo, Gemma).
Properly quote ${{ matrix.config }} and ${{ matrix.model }} in bash
conditional expressions to prevent potential word splitting issues.
@pytorch-bot

pytorch-bot Bot commented Jan 21, 2026 •

Copy link
Copy Markdown

🔗 Helpful Links

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

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

❌ 19 New Failures

As of commit 36e5c29 with merge base c92f03f (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 Jan 21, 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.

Use python module invocation instead of CLI binary to avoid
PATH issues in conda environment.
@github-actions

Copy link
Copy Markdown

Looks like this PR hasn't been updated in a while so we're going to go ahead and mark this as Stale.
Feel free to remove the Stale label if you feel this was a mistake.
If you are unable to remove the Stale label please contact a maintainer in order to do so.
If you want the bot to never mark this PR stale again, add the no-stale label.
Stale pull requests will automatically be closed after 30 days of inactivity.

@github-actions github-actions Bot added the Stale PRs inactive for over 60 days label Mar 23, 2026
@github-actions github-actions Bot closed this Apr 30, 2026
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. Stale PRs inactive for over 60 days

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant