[CI] Remove Jenkins PR linter step#19798
Merged
Merged
Conversation
The Jenkins PR title/body linter is comparatively heavy and can report false positives before the normal CI signal is available. This removes the check_pr step from the Jenkins prepare flow and drops the now-unused script-level test coverage.
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Code Review
This pull request removes the PR title and body linting checks from the CI pipeline. This includes deleting the check_pr.py script, removing the check_pr helper function and its invocations from the Jenkinsfiles and templates, and deleting the corresponding unit tests in tests/python/ci/test_ci.py. I have no further feedback to provide as there are no review comments.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
guan404ming
approved these changes
Jun 16, 2026
NVRTC does not reliably define the private __uint32_t typedef used by the FP8 vector helper casts. This updates the generated CUDA helper sources to use the public uint32_t spelling already used elsewhere in TVM CUDA code.
MasterJH5574
pushed a commit
to MasterJH5574/tvm
that referenced
this pull request
Jun 16, 2026
The Jenkins PR title/body linter is comparatively heavy and can report false positives before the normal CI signal is available. This removes the check_pr step from the Jenkins prepare flow and drops the now-unused script-level test coverage.
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
2 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 Jenkins PR title/body linter is comparatively heavy and can report false positives before the normal CI signal is available.
This removes the check_pr step from the Jenkins prepare flow and drops the now-unused script-level test coverage.