Handle triton kernel import exception #29062
Merged
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 PR at #25319 introduced an
ImportErrorcatch to prevent failures when importingtriton. However, after upgrading vLLM from 0.11.0 to 0.11.1 via:Running vllm serve Qwen/Qwen3-8B results in the following error:
This suggests a compatibility issue between the upgraded triton version and triton-kernels, where constexpr_function was either removed or renamed.
While the original PR handled ImportError, this case involves an AttributeError due to API changes in triton.language. Adding a guard for AttributeError (in addition to ImportError) could help gracefully handle such mismatches and improve robustness during dependency upgrades.
This change proposes catching AttributeError when accessing tl.constexpr_function to prevent breakage in environments where triton and triton-kernels are mismatched.