[SDPA] Fix warning message

[drisspg]

Stack from ghstack (oldest at bottom):

• -> [SDPA] Fix warning message #138278

[pytorch-bot]

🔗 Helpful Links

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

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

❌ 5 New Failures

As of commit 4969874 with merge base d531bd5 ():

NEW FAILURES - The following jobs have failed:

• linux-binary-libtorch-cxx11-abi / libtorch-cpu-shared-with-deps-cxx11-abi-build / build (gh)
  bash: /builder/libtorch/build.sh: No such file or directory
• linux-binary-libtorch-pre-cxx11 / libtorch-cpu-shared-with-deps-pre-cxx11-build / build (gh)
  bash: /builder/libtorch/build.sh: No such file or directory
• linux-binary-manywheel / manywheel-py3_9-cuda11_8-build / build (gh)
  bash: /builder/manywheel/build.sh: No such file or directory
• linux-binary-manywheel / manywheel-py3_9-cuda12_1-build / build (gh)
  bash: /builder/manywheel/build.sh: No such file or directory
• linux-binary-manywheel / manywheel-py3_9-cuda12_4-build / build (gh)
  bash: /builder/manywheel/build.sh: No such file or directory

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

[drisspg]

@pytorchbot merge

[drisspg]

@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

[pytorchmergebot]

Merge failed

Reason: 1 jobs have failed, first few of them are: linux-binary-libtorch-pre-cxx11 / libtorch-cpu-shared-with-deps-pre-cxx11-build / build

Details for Dev Infra team

Raised by workflow job

[cyyever]

@pytorchbot merge -f "Unrelated failures"

[pytorchmergebot]

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