🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR
• 📄 Preview C++ docs built from this PR
• ❓ Need help or want to give feedback on the CI? Visit the bot commands wiki or our office hours

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:

• [PREEMPTIVE] Removal of ephemeral variants on scale-config.yml

❌ 1 New Failure

As of commit 153ea95 with merge base 7243c69 ():

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

Hi @malfet , could you please help to review this PR also which fix a high priority issue about bundled gomp in cpu wheels? The failures seems aren't related to the PR changes

Hi @chuanqi129 what's the test plan for this PR? Or how one expects to verify that something is really fixed?

Hi @chuanqi129 what's the test plan for this PR? Or how one expects to verify that something is really fixed?

Good question. We have verified it in local by @yuchengliu1 with the case from the issue #149422, but I also didn't figure out a good method to test it in CD whl smoke test script. @malfet any suggestion?

Hi @chuanqi129 could you please post log of running the test from #149422 (comment) on the binary downloaded from https://github.com/pytorch/pytorch/actions/runs/14098800119?pr=150084 ?

Update the test results with the latest changes as follows.

Test results with the nightly wheel:

[root@icx-6 ~]# python check_gomp.py
omp_max_threads after loading libgomp.so and libtorch_cpu.so: 1
Traceback (most recent call last):
  File "/root/check_gomp.py", line 74, in <module>
    main()
    ~~~~^^
  File "/root/check_gomp.py", line 68, in main
    raise RuntimeError(
        "omp_max_threads is 1. Check whether libgomp.so is loaded twice."
    )
RuntimeError: omp_max_threads is 1. Check whether libgomp.so is loaded twice.

Test results with the fixed wheel:

[root@icx-6 ~]# python check_gomp.py
omp_max_threads after loading libgomp.so and libtorch_cpu.so: 112

@pytorchbot rebase -b viable/strict

@pytorchbot started a rebase job onto refs/remotes/origin/viable/strict. Check the current status here

Successfully rebased cd_fix_gomp onto refs/remotes/origin/viable/strict, please pull locally before adding more changes (for example, via git checkout cd_fix_gomp && git pull --rebase)

@pytorchmergebot merge -f "all required tests are passing"

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

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

Cherry picking #150084

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

Auto-merging .ci/manywheel/build_common.sh
Auto-merging .circleci/scripts/binary_linux_test.sh
CONFLICT (content): Merge conflict in .circleci/scripts/binary_linux_test.sh
error: could not apply 20dbe644c70... [CD] Fix the libgomp twice load issue (#150084)
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 set advice.mergeConflict false"