Skip to content

Use flavor-specific artifact names to avoid S3 upload collision#18581

Merged
manuelcandales merged 1 commit intorelease/1.2from
cherry-pick-18578-by-pytorch_bot_bot_
Mar 30, 2026
Merged

Use flavor-specific artifact names to avoid S3 upload collision#18581
manuelcandales merged 1 commit intorelease/1.2from
cherry-pick-18578-by-pytorch_bot_bot_

Conversation

@pytorchbot
Copy link
Copy Markdown
Collaborator

When android-release-on-tag calls this workflow for multiple flavors, they share the same run_id and S3 prefix. Naming the intermediate artifact executorch-${FLAVOR}.aar prevents the second and third uploads from failing with "file already exists".

When android-release-on-tag calls this workflow for multiple flavors,
they share the same run_id and S3 prefix. Naming the intermediate
artifact executorch-${FLAVOR}.aar prevents the second and third uploads
from failing with "file already exists".

(cherry picked from commit 330a567)
@pytorch-bot
Copy link
Copy Markdown

pytorch-bot Bot commented Mar 30, 2026

🔗 Helpful Links

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

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

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 Mar 30, 2026
@manuelcandales manuelcandales merged commit 853fc86 into release/1.2 Mar 30, 2026
178 of 184 checks passed
@manuelcandales manuelcandales deleted the cherry-pick-18578-by-pytorch_bot_bot_ branch March 30, 2026 15:13
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