8000 Make python_agnostic cpp extension tests standalone by jbschlosser · Pull Request #153274 · pytorch/pytorch · GitHub
[go: up one dir, main page]

Skip to content

Make python_agnostic cpp extension tests standalone #153274

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: gh/jbschlosser/245/base
Choose a base branch
from

Conversation

jbschlosser
Copy link
Contributor
@jbschlosser jbschlosser commented May 9, 2025

Stack from ghstack (oldest at bottom):

Related: #148920

This PR:

  • Introduces a new file test/cpp_extensions/python_agnostic_extension/test/test_python_agnostic.py with testing that follows the usual python testing patterns
    • This replaces the testing for python_agnostic in test/test_cpp_extensions_aot.py

After this PR, it is now possible to run:

python test/cpp_extensions/python_agnostic_extension/test/test_python_agnostic.py

and the test will build the prerequisite wheel before running the tests.

Copy link
pytorch-bot bot commented May 9, 2025

🔗 Helpful Links

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

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

❌ 1 New Failure

As of commit 18681a5 with merge base 916f6ba (image):

NEW FAILURE - The following job has failed:

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 May 9, 2025
jbschlosser added a commit that referenced this pull request May 9, 2025
ghstack-source-id: a2a474a
Pull Request resolved: #153274
jbschlosser added a commit that referenced this pull request May 9, 2025
ghstack-source-id: 3c8ad67
Pull Request resolved: #153274
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.

very nice! can we also get a link here from CI to make sure this does indeed run?

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.

thank u! <3

Related: #148920

This PR:
* Introduces a new file `test/cpp_extensions/python_agnostic_extension/test/test_python_agnostic.py` with testing that follows the usual python testing patterns
    * This replaces the testing for python_agnostic in `test/test_cpp_extensions_aot.py`

After this PR, it is now possible to run:
```
python test/cpp_extensions/python_agnostic_extension/test/test_python_agnostic.py
```

and the test will build the prerequisite wheel before running the tests.

[ghstack-poisoned]
jbschlosser added a commit that referenced this pull request May 13, 2025
ghstack-source-id: 55e7f48
Pull Request resolved: #153274
@cyyever
Copy link
Collaborator
cyyever commented May 15, 2025

@pytorchmergebot merge -i

@pytorch-bot pytorch-bot bot added the ciflow/trunk Trigger trunk jobs on your pull request label May 15, 2025
@pytorchmergebot
Copy link
Collaborator

Merge started

Your change will be merged while ignoring the following 0 checks:

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
Copy link
Collaborator

Merge failed

Reason: 1 jobs have failed, first few of them are: trunk / win-vs2022-cpu-py3 / test (default, 2, 3, lf.windows.4xlarge.nonephemeral)

Details for Dev Infra team Raised by workflow job

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ciflow/trunk Trigger trunk jobs on your pull request topic: not user facing topic category
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants
0