Skip to content

Split libtorch agnostic tests by feature version#167803

Closed
mikaylagawarecki wants to merge 6 commits intogh/mikaylagawarecki/377/basefrom
gh/mikaylagawarecki/377/head
Closed

Split libtorch agnostic tests by feature version#167803
mikaylagawarecki wants to merge 6 commits intogh/mikaylagawarecki/377/basefrom
gh/mikaylagawarecki/377/head

Conversation

@mikaylagawarecki
Copy link
Contributor

@mikaylagawarecki mikaylagawarecki commented Nov 14, 2025

@pytorch-bot
Copy link

pytorch-bot bot commented Nov 14, 2025

🔗 Helpful Links

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

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

✅ No Failures

As of commit 4679f51 with merge base 1c04a43 (image):
💚 Looks good so far! There are no failures yet. 💚

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

Copy link
Contributor

@janeyx99 janeyx99 left a comment

Choose a reason for hiding this comment

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

I'm understanding this is a draft PR for now but I have a q: is it right to expect the diff between 2_9 and 2_10 is 2_9 will have fewer kernels that are not dependent on 2_10?

Copy link
Contributor

@janeyx99 janeyx99 left a comment

Choose a reason for hiding this comment

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

skimmed, looks fine to me

"cxx": ["-fdiagnostics-color=always"],
"cxx": [
"-fdiagnostics-color=always",
"-DTORCH_STABLE_ONLY",
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
"-DTORCH_STABLE_ONLY",

we expect users to only need one flag definition

extra_compile_args = {
"cxx": [
"-fdiagnostics-color=always",
"-DTORCH_STABLE_ONLY",
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
"-DTORCH_STABLE_ONLY",

Khanaksahu pushed a commit to Khanaksahu/pytorch that referenced this pull request Nov 17, 2025
Tests are split into libtorch_agnostic_2_9_extension and libtorch_agnostic_2_10_extension depending on the minimum version they should compile+run in




[ghstack-poisoned]
@pytorchmergebot
Copy link
Collaborator

Starting merge as part of PR stack under #167962

pytorchmergebot pushed a commit that referenced this pull request Nov 18, 2025
…rsion (#167804)

Adds a CI workflow that tests the wheel built on current main targeting 2.9 with a 2.9 runtime

Pull Request resolved: #167804
Approved by: https://github.com/janeyx99
ghstack dependencies: #168025, #167802, #167803
pytorchmergebot pushed a commit that referenced this pull request Nov 18, 2025
Splits each torch library registration in the 2.10 folder into its own file -- I had a script that parsed kernel.cpp to do this but I felt like forcing this responsibility on the user might be less error prone

Compiles each file targetting 2.9 and asserts that compilation fails. (There are 2 2.9 kernels we use as negative tests where compilation is expected to succeed)

Pull Request resolved: #167962
Approved by: https://github.com/janeyx99
ghstack dependencies: #168025, #167802, #167803, #167804
jeffdaily added a commit to ROCm/pytorch that referenced this pull request Nov 18, 2025
Unclear which PR in the ghstack caused the ROCm failure.
Stack was (oldest at bottom):
 - pytorch#167962
 - pytorch#167804
 - pytorch#167803
 - pytorch#167802
 - pytorch#168025
pytorchmergebot pushed a commit that referenced this pull request Nov 19, 2025
Unclear which PR in the ghstack caused the ROCm failure. Stack was (oldest at bottom):
 - #167962
 - #167804
 - #167803
 - #167802
 - #168025

Fixes the following test:

PYTORCH_TEST_WITH_ROCM=1 python test/cpp_extensions/libtorch_agnostic_2_10_extension/test_version_compatibility.py FunctionVersionCompatibilityTest.test_mv_tensor_accessor_cuda_works_with_2_9

Pull Request resolved: #168087
Approved by: https://github.com/jeffdaily, https://github.com/janeyx99

Co-authored-by: Jeff Daily <jeff.daily@amd.com>
Co-authored-by: Jane (Yuan) Xu <31798555+janeyx99@users.noreply.github.com>
pytorchmergebot pushed a commit that referenced this pull request Nov 20, 2025
~This PR does change the semantics of the >> operator by using STD_TORCH_CHECK to throw the error instead of TORCH_CHECK. Jane (who is writing this message) thinks it is okay because it is the error case when an invalid MemoryFormat or Layout is getting passed into >>, so the UX benefits of TORCH_CHECK over STD_TORCH_CHECK there are not significant enough to warrant making a new copy of Layout and MemoryFormat's >> APIs.~

Never mind! We shouldn't change TORCH_CHECK to STD_TORCH_CHECK for core usage ever, cuz the traceback info and c10::Error is very much desired!! So the solution is to not migrate the >>s. I pushed new commits to the stack to remove the >> code, but for reference, 8a30179 has all the code that I ended up deleting.

Pull Request resolved: #168034
Approved by: https://github.com/janeyx99
ghstack dependencies: #168025, #167802, #167803, #167804, #167962

Co-authored-by: Jane Xu <janeyx@meta.com>
JacobSzwejbka pushed a commit that referenced this pull request Dec 8, 2025
~This PR does change the semantics of the >> operator by using STD_TORCH_CHECK to throw the error instead of TORCH_CHECK. Jane (who is writing this message) thinks it is okay because it is the error case when an invalid MemoryFormat or Layout is getting passed into >>, so the UX benefits of TORCH_CHECK over STD_TORCH_CHECK there are not significant enough to warrant making a new copy of Layout and MemoryFormat's >> APIs.~

Never mind! We shouldn't change TORCH_CHECK to STD_TORCH_CHECK for core usage ever, cuz the traceback info and c10::Error is very much desired!! So the solution is to not migrate the >>s. I pushed new commits to the stack to remove the >> code, but for reference, 8a30179 has all the code that I ended up deleting.

Pull Request resolved: #168034
Approved by: https://github.com/janeyx99
ghstack dependencies: #168025, #167802, #167803, #167804, #167962

Co-authored-by: Jane Xu <janeyx@meta.com>
tiendatngcs pushed a commit to tiendatngcs/pytorch-Dec25 that referenced this pull request Dec 9, 2025
@github-actions github-actions bot deleted the gh/mikaylagawarecki/377/head branch December 19, 2025 02:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants