Remove CentOS 7 build#8191
Merged
Jokeren merged 1 commit intotriton-lang:mainfrom Oct 9, 2025
Merged
Conversation
Contributor
|
cc @atalman |
neildhar
force-pushed
the
remove_centos_build
branch
from
2b3c326 to
0105edb
Compare
7 tasks
Contributor
|
@neildhar can you please resolve the conflicts? |
The CentOS 7 build was added back to support the release of PyTorch 2.6 (triton-lang#5158). However, PyTorch has since dropped support for manylinux2014 and the pre-C++11 ABI: https://dev-discuss.pytorch.org/t/pytorch-linux-wheels-switching-to-new-wheel-build-platform-manylinux-2-28-on-november-12-2024/2581 Given that the AlmaLinux 8 build already supports a relatively old version of glibc, it is unlikely that the CentOS 7 build is being used often. In addition, the CentOS build is tricky to use since the libraries are built with the pre-C++11 ABI, which would need to be propagated to the Triton build for it to link successfully.
neildhar
force-pushed
the
remove_centos_build
branch
from
0105edb to
f32e679
Compare
Collaborator
Author
|
@Jokeren Done |
yangshuxin
pushed a commit
to yangshuxin/triton
that referenced
this pull request
Oct 9, 2025
The CentOS 7 build was added back to support the release of PyTorch 2.6 (triton-lang#5158). However, PyTorch has since dropped support for manylinux2014 and the pre-C++11 ABI: https://dev-discuss.pytorch.org/t/pytorch-linux-wheels-switching-to-new-wheel-build-platform-manylinux-2-28-on-november-12-2024/2581 Given that the AlmaLinux 8 build already supports a relatively old version of glibc, it is unlikely that the CentOS 7 build is being used often. In addition, the CentOS build is tricky to use since the libraries are built with the pre-C++11 ABI, which would need to be propagated to the Triton build for it to link successfully. # New contributor declaration - [x] I am not making a trivial change, such as fixing a typo in a comment. - [x] I have written a PR description following these [rules](https://cbea.ms/git-commit/#why-not-how). - [x] I have run `pre-commit run --from-ref origin/main --to-ref HEAD`. - Select one of the following. - [ ] I have added tests. - `/test` for `lit` tests - `/unittest` for C++ tests - `/python/test` for end-to-end tests - [x] This PR does not need a test because it is a CI change. - Select one of the following. - [x] I have not added any `lit` tests. - [ ] The `lit` tests I have added follow these [best practices](https://mlir.llvm.org/getting_started/TestingGuide/#filecheck-best-practices), including the "tests should be minimal" section. (Usually running Python code and using the instructions it generates is not minimal.)
Jokeren
pushed a commit
that referenced
this pull request
Oct 10, 2025
The CentOS 7 build was added back to support the release of PyTorch 2.6 (#5158). However, PyTorch has since dropped support for manylinux2014 and the pre-C++11 ABI: https://dev-discuss.pytorch.org/t/pytorch-linux-wheels-switching-to-new-wheel-build-platform-manylinux-2-28-on-november-12-2024/2581 Given that the AlmaLinux 8 build already supports a relatively old version of glibc, it is unlikely that the CentOS 7 build is being used often. In addition, the CentOS build is tricky to use since the libraries are built with the pre-C++11 ABI, which would need to be propagated to the Triton build for it to link successfully. # New contributor declaration - [x] I am not making a trivial change, such as fixing a typo in a comment. - [x] I have written a PR description following these [rules](https://cbea.ms/git-commit/#why-not-how). - [x] I have run `pre-commit run --from-ref origin/main --to-ref HEAD`. - Select one of the following. - [ ] I have added tests. - `/test` for `lit` tests - `/unittest` for C++ tests - `/python/test` for end-to-end tests - [x] This PR does not need a test because it is a CI change. - Select one of the following. - [x] I have not added any `lit` tests. - [ ] The `lit` tests I have added follow these [best practices](https://mlir.llvm.org/getting_started/TestingGuide/#filecheck-best-practices), including the "tests should be minimal" section. (Usually running Python code and using the instructions it generates is not minimal.)
ita9naiwa
pushed a commit
to ita9naiwa/triton
that referenced
this pull request
Oct 12, 2025
The CentOS 7 build was added back to support the release of PyTorch 2.6 (triton-lang#5158). However, PyTorch has since dropped support for manylinux2014 and the pre-C++11 ABI: https://dev-discuss.pytorch.org/t/pytorch-linux-wheels-switching-to-new-wheel-build-platform-manylinux-2-28-on-november-12-2024/2581 Given that the AlmaLinux 8 build already supports a relatively old version of glibc, it is unlikely that the CentOS 7 build is being used often. In addition, the CentOS build is tricky to use since the libraries are built with the pre-C++11 ABI, which would need to be propagated to the Triton build for it to link successfully. # New contributor declaration - [x] I am not making a trivial change, such as fixing a typo in a comment. - [x] I have written a PR description following these [rules](https://cbea.ms/git-commit/#why-not-how). - [x] I have run `pre-commit run --from-ref origin/main --to-ref HEAD`. - Select one of the following. - [ ] I have added tests. - `/test` for `lit` tests - `/unittest` for C++ tests - `/python/test` for end-to-end tests - [x] This PR does not need a test because it is a CI change. - Select one of the following. - [x] I have not added any `lit` tests. - [ ] The `lit` tests I have added follow these [best practices](https://mlir.llvm.org/getting_started/TestingGuide/#filecheck-best-practices), including the "tests should be minimal" section. (Usually running Python code and using the instructions it generates is not minimal.)
tmoreau89
pushed a commit
to tmoreau89/triton
that referenced
this pull request
Dec 1, 2025
The CentOS 7 build was added back to support the release of PyTorch 2.6 (triton-lang#5158). However, PyTorch has since dropped support for manylinux2014 and the pre-C++11 ABI: https://dev-discuss.pytorch.org/t/pytorch-linux-wheels-switching-to-new-wheel-build-platform-manylinux-2-28-on-november-12-2024/2581 Given that the AlmaLinux 8 build already supports a relatively old version of glibc, it is unlikely that the CentOS 7 build is being used often. In addition, the CentOS build is tricky to use since the libraries are built with the pre-C++11 ABI, which would need to be propagated to the Triton build for it to link successfully. # New contributor declaration - [x] I am not making a trivial change, such as fixing a typo in a comment. - [x] I have written a PR description following these [rules](https://cbea.ms/git-commit/#why-not-how). - [x] I have run `pre-commit run --from-ref origin/main --to-ref HEAD`. - Select one of the following. - [ ] I have added tests. - `/test` for `lit` tests - `/unittest` for C++ tests - `/python/test` for end-to-end tests - [x] This PR does not need a test because it is a CI change. - Select one of the following. - [x] I have not added any `lit` tests. - [ ] The `lit` tests I have added follow these [best practices](https://mlir.llvm.org/getting_started/TestingGuide/#filecheck-best-practices), including the "tests should be minimal" section. (Usually running Python code and using the instructions it generates is not minimal.)
meta-codesync Bot
pushed a commit
to facebookexperimental/triton
that referenced
this pull request
Mar 24, 2026
Summary: This is a cherry-pick of an upstream PR: triton-lang/triton#8191 Upstream commit message: ``` > Remove CentOS 7 build (#8191) ``` ***Do not remove the following line from this commit*** Reactor Cherry-pick Revision: 0b45587 --- This diff was generated by running: ``` buck run fbcode//triton/tools/reactor:reactor -- cherrypick --num-commits 1 --no-submit ``` Diff Comparison: https://www.internalfb.com/intern/paste/P2245278607/ Reviewed By: stashuk-olek Differential Revision: D97523419 fbshipit-source-id: 3489b138d903739a45edc53ab37f3c256f45a880
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The CentOS 7 build was added back to support the release of PyTorch 2.6 (#5158). However, PyTorch has since dropped support for manylinux2014 and the pre-C++11 ABI:
https://dev-discuss.pytorch.org/t/pytorch-linux-wheels-switching-to-new-wheel-build-platform-manylinux-2-28-on-november-12-2024/2581
Given that the AlmaLinux 8 build already supports a relatively old version of glibc, it is unlikely that the CentOS 7 build is being used often. In addition, the CentOS build is tricky to use since the libraries are built with the pre-C++11 ABI, which would need to be propagated to the Triton build for it to link successfully.
New contributor declaration
I am not making a trivial change, such as fixing a typo in a comment.
I have written a PR description following these
rules.
I have run
pre-commit run --from-ref origin/main --to-ref HEAD.Select one of the following.
/testforlittests/unittestfor C++ tests/python/testfor end-to-end testsSelect one of the following.
littests.littests I have added follow these best practices,including the "tests should be minimal" section. (Usually running Python code
and using the instructions it generates is not minimal.)