[Intel GPU] Upgrade OneDNN XPU Tag to v3.9.1

[LuFinch]

cc @gujinghui @PenghuiCheng @XiaobingSuper @jianyuh @jgong5 @mingfeima @sanchitintel @ashokei @jingxu10 @min-jean-cho @yanbing-j @Guobing-Chen @Xia-Weiwen @snadampal

[pytorch-bot]

🔗 Helpful Links

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

• 📄 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

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

✅ You can merge normally! (2 Unrelated Failures)

As of commit 13a721e with merge base f8ffa91 ():

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

• xpu / linux-jammy-xpu-n-py3.10 / test (default, 1, 8, linux.idc.xpu) (gh) (disabled by #162140)
  inductor/test_max_autotune.py::TestMaxAutotune::test_max_autotune_addmm_persistent_tma_a_transposed_False_b_transposed_False_dynamic_True
• xpu / linux-jammy-xpu-n-py3.10 / test (default, 5, 8, linux.idc.xpu) (gh) (disabled by #162141)
  dynamo/test_aot_autograd_cache.py::AOTAutogradCacheBundledTests::test_autograd_inductor_guards_device_xpu_float16_requires_grad_True

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

[LuFinch]

@guangyey Could you help re-trigger CI?

[guangyey]

Done.

[LuFinch]

@pytorchbot rebase

[pytorchmergebot]

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

[pytorchmergebot]

Tried to rebase and push PR #161932, but it was already up to date. Try rebasing against main by issuing:
@pytorchbot rebase -b main

[LuFinch]

@pytorchbot rebase -b main

[pytorchmergebot]

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

[pytorchmergebot]

Successfully rebased lfq/update_onednn3.9 onto refs/remotes/origin/main, please pull locally before adding more changes (for example, via git checkout lfq/update_onednn3.9 && git pull --rebase)

[LuFinch]

@pytorchbot merge

[pytorch-bot]

Pull workflow has not been scheduled for the PR yet. It could be because author doesn't have permissions to run those or skip-checks keywords were added to PR/commits, aborting merge. Please get/give approval for the workflows and/or remove skip ci decorators before next merge attempt. If you think this is a mistake, please contact PyTorch Dev Infra.

[LuFinch]

@guangyey Please help trigger CI again..

[LuFinch]

@pytorchbot merge

[pytorchmergebot]

Merge started

Your change will be merged once all checks pass (ETA 0-4 Hours).

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