Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add option to upload Nova artifacts to S3 directly #5668

Merged
merged 6 commits into from
Sep 14, 2024

Conversation

huydhn
Copy link
Contributor

@huydhn huydhn commented Sep 14, 2024

For the context, Nova jobs upload the artifacts to GitHub because this works on all runners including non-AWS ones like GitHub runners. However, there is a scale issue when trying to upload large artifacts (GB in size) to GitHub that the files are too big, so the upload could either:

To address this, I add the option to upload to S3 gha-artifacts bucket here which is direct and more efficient.

Copy link

vercel bot commented Sep 14, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Skipped Deployment
Name Status Preview Comments Updated (UTC)
torchci ⬜️ Ignored (Inspect) Visit Preview Sep 14, 2024 3:31pm

@facebook-github-bot facebook-github-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 Sep 14, 2024
Copy link
Contributor

@atalman atalman left a comment

Choose a reason for hiding this comment

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

lgtm. Maybe consider naming input variable something more descriptive:
upload-artifact-s3

when reading yml that uses this workflow, may not be evident right away what use-s3 is for

@huydhn huydhn merged commit ac26b29 into main Sep 14, 2024
30 of 36 checks passed
facebook-github-bot pushed a commit to pytorch/executorch that referenced this pull request Sep 14, 2024
Summary:
This uses the new `use-s3` input from pytorch/test-infra#5668 to upload exported models and Android artifacts directly to S3.  iOS artifacts need to be built on GH runner with Xcode, so they will still need to go through GH before being uploaded to S3.

This helps address scaling issue when upload large files to GitHub, for example:

* Timing out https://github.com/pytorch/executorch/actions/runs/10858058150/job/30136354800
* or just fail in the middle of the upload https://github.com/pytorch/executorch/actions/runs/10856291106/job/30132545832

Pull Request resolved: #5375

Reviewed By: kirklandsign

Differential Revision: D62680104

Pulled By: huydhn

fbshipit-source-id: 4f82317526770b49c0ad2a555638ddb5dfa6316b
huydhn added a commit to huydhn/test-infra that referenced this pull request Sep 24, 2024
For the context, Nova jobs upload the artifacts to GitHub because this
works on all runners including non-AWS ones like GitHub runners.
However, there is a scale issue when trying to upload large artifacts
(GB in size) to GitHub that the files are too big, so the upload could
either:

* Timing out
https://github.com/pytorch/executorch/actions/runs/10858058150/job/30136354800
* or just fail in the middle of the upload
https://github.com/pytorch/executorch/actions/runs/10856291106/job/30132545832

To address this, I add the option to upload to S3 gha-artifacts bucket
here which is direct and more efficient.
kit1980 pushed a commit that referenced this pull request Sep 24, 2024
For the context, Nova jobs upload the artifacts to GitHub because this
works on all runners including non-AWS ones like GitHub runners.
However, there is a scale issue when trying to upload large artifacts
(GB in size) to GitHub that the files are too big, so the upload could
either:

* Timing out
https://github.com/pytorch/executorch/actions/runs/10858058150/job/30136354800
* or just fail in the middle of the upload
https://github.com/pytorch/executorch/actions/runs/10856291106/job/30132545832

To address this, I add the option to upload to S3 gha-artifacts bucket
here which is direct and more efficient.
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.

4 participants