Skip to content

Conversation

@atalman
Copy link
Contributor

@atalman atalman commented Oct 21, 2024

Since cuda 12.4 binaries are default binaries on pypi now. The pytorch_extra_install_requirements need to use 12.4.
This would need to be cherry-picked to release 2.5 branch to avoid injecting these versions into metadata during pypi promotion.

@atalman atalman requested a review from a team as a code owner October 21, 2024 13:24
@pytorch-bot
Copy link

pytorch-bot bot commented Oct 21, 2024

🔗 Helpful Links

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

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

❌ 5 New Failures, 4 Unrelated Failures

As of commit 1707dfd with merge base 8f3efb8 (image):

NEW FAILURES - The following jobs have failed:

FLAKY - The following jobs failed but were likely due to flakiness present on trunk:

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@pytorch-bot pytorch-bot bot added the topic: not user facing topic category label Oct 21, 2024
Copy link
Collaborator

@albanD albanD left a comment

Choose a reason for hiding this comment

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

The fact that this changes the AMD and macos binary sounds wrong!

@atalman
Copy link
Contributor Author

atalman commented Oct 21, 2024

Hi @albanD this is related to poetry issue where we want to have same metadata for all wheels. Hence this is changing windows, macos, amd wheels to have same metadata as the linux wheels we publish to pypi.

@atalman atalman added the ciflow/binaries_wheel Trigger binary build and upload jobs for wheel on the PR label Oct 21, 2024
@atalman
Copy link
Contributor Author

atalman commented Oct 21, 2024

@pytorchmergebot merge -f "XPU failures are not related"

@pytorchmergebot
Copy link
Collaborator

Merge started

Your change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Please use -f as last resort and instead consider -i/--ignore-current to continue the merge ignoring current failures. This will allow currently pending tests to finish and report signal before the merge.

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Advanced Debugging
Check the merge workflow status
here

@atalman
Copy link
Contributor Author

atalman commented Oct 21, 2024

@pytorchbot cherry-pick -c critical --onto release/2.5

@pytorchbot
Copy link
Collaborator

Cherry picking #138458

Command git -C /home/runner/work/pytorch/pytorch cherry-pick -x 60081c29ecaa594e2bf942de0e52a1932348374b returned non-zero exit code 1

Auto-merging .github/scripts/generate_binary_build_matrix.py
CONFLICT (content): Merge conflict in .github/scripts/generate_binary_build_matrix.py
Auto-merging .github/workflows/generated-linux-aarch64-binary-manywheel-nightly.yml
Auto-merging .github/workflows/generated-linux-s390x-binary-manywheel-nightly.yml
Auto-merging .github/workflows/generated-macos-arm64-binary-wheel-nightly.yml
CONFLICT (content): Merge conflict in .github/workflows/generated-macos-arm64-binary-wheel-nightly.yml
Auto-merging .github/workflows/generated-windows-binary-wheel-nightly.yml
error: could not apply 60081c29ec... Use cuda 12.4 pytorch_extra_install_requirements as default (#138458)
hint: After resolving the conflicts, mark them with
hint: "git add/rm <pathspec>", then run
hint: "git cherry-pick --continue".
hint: You can instead skip this commit with "git cherry-pick --skip".
hint: To abort and get back to the state before "git cherry-pick",
hint: run "git cherry-pick --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Details for Dev Infra team Raised by workflow job

malfet pushed a commit that referenced this pull request Oct 22, 2024
…ault (#138526)

Cherry-Picks #138458
Need to do it manually due to conflict with generated files.
SamGinzburg pushed a commit that referenced this pull request Oct 28, 2024
Since cuda 12.4 binaries are default binaries on pypi now. The pytorch_extra_install_requirements need to use 12.4.
This would need to be cherry-picked to release 2.5 branch to avoid injecting these versions into metadata during pypi promotion.

Pull Request resolved: #138458
Approved by: https://github.com/malfet
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ciflow/binaries_wheel Trigger binary build and upload jobs for wheel on the PR Merged topic: not user facing topic category

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants