Skip to content

Conversation

@mikaylagawarecki
Copy link
Contributor

@mikaylagawarecki mikaylagawarecki commented Sep 26, 2025

@pytorch-bot
Copy link

pytorch-bot bot commented Sep 26, 2025

🔗 Helpful Links

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

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:

⏳ 2 Pending, 1 Unrelated Failure

As of commit a704132 with merge base e901866 (image):

FLAKY - The following job failed but was likely due to flakiness present on trunk:

UNSTABLE - The following jobs are marked as unstable, possibly due to flakiness on trunk:

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

mikaylagawarecki added a commit that referenced this pull request Sep 26, 2025
ghstack-source-id: 45ae7e0
Pull Request resolved: #163991
mikaylagawarecki added a commit that referenced this pull request Oct 1, 2025
ghstack-source-id: 51f3609
Pull Request resolved: #163991
@mikaylagawarecki mikaylagawarecki marked this pull request as ready for review October 1, 2025 19:00
[MAJ ][ MIN ][PATCH ][ ABI TAG ]
```

In the present phase of development, APIs in the C-shim will be versioned based on major.minor.patch release that they are first introduced in, with 2.10 being the first release where this will be enforced. The ABI tag is reserved for future use.
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
In the present phase of development, APIs in the C-shim will be versioned based on major.minor.patch release that they are first introduced in, with 2.10 being the first release where this will be enforced. The ABI tag is reserved for future use.
In the present phase of development, APIs in the C-shim will be versioned based on the major.minor.patch release that they are first introduced in, with 2.10 being the first release where this will be enforced. The ABI tag is reserved for internal use.

no promises

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I think this might indeed by future rather than internal (I'm thinking we will use it if we want to allow users to depend on nightlies and bump the version more frequently than each release when the ABI becomes more mature).

mikaylagawarecki added a commit that referenced this pull request Oct 1, 2025
ghstack-source-id: b29f8e9
Pull Request resolved: #163991
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.

For aoti_torch_call_dispatcher_v2, I'm okay with keeping the docs here still but warning that we don't make any guarantees on the underlying ops changing.

@pytorch-bot pytorch-bot bot added ciflow/b200 ciflow/h100 ciflow/rocm Trigger "default" config CI on ROCm labels Oct 29, 2025
mikaylagawarecki added a commit that referenced this pull request Oct 29, 2025
ghstack-source-id: 73b102a
Pull Request resolved: #163991
@mikaylagawarecki
Copy link
Contributor Author

@pytorchbot merge

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

This PR updates submodules third_party/fbgemm, third_party/kleidiai, third_party/cudnn_frontend, third_party/kineto

If those updates are intentional, please add "submodule" keyword to PR title/description.

mikaylagawarecki added a commit that referenced this pull request Oct 29, 2025
ghstack-source-id: 8929fdf
Pull Request resolved: #163991
@mikaylagawarecki
Copy link
Contributor Author

@pytorchbot merge

@pytorchmergebot
Copy link
Collaborator

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

Merge failed

Reason: 1 jobs have failed, first few of them are: trunk / libtorch-linux-jammy-cuda12.8-py3.10-gcc11-debug / build

Details for Dev Infra team Raised by workflow job

@mikaylagawarecki
Copy link
Contributor Author

Build failure is unrelated to docs change

@mikaylagawarecki
Copy link
Contributor Author

@pytorchbot merge -i

@pytorchmergebot
Copy link
Collaborator

Merge started

Your change will be merged while ignoring the following 2 checks: pull / linux-jammy-py3.10-gcc11 / test (distributed, 2, 2, linux.2xlarge), trunk / libtorch-linux-jammy-cuda12.8-py3.10-gcc11-debug / build

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

@github-actions github-actions bot deleted the gh/mikaylagawarecki/344/head branch November 29, 2025 02:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ciflow/b200 ciflow/h100 ciflow/rocm Trigger "default" config CI on ROCm ciflow/trunk Trigger trunk jobs on your pull request Merged topic: not user facing topic category

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants