[None][chore] Increase operations-per-run to 1000 for stale action #8162

karljang · 2025-10-06T21:12:30Z

I noticed that the stale action was completing too early, without processing older issues. To address this, I’m increasing operations-per-run to 1000 for now. We can reduce it later once the backlog of older issues has been sufficiently processed.

Log from https://github.com/NVIDIA/TensorRT-LLM/actions/runs/18269012961/job/52008217348

Warning: No more operations left! Exiting...
Warning: If you think that not enough issues were processed you could try to increase the quantity related to the  operations-per-run (https://github.com/actions/stale#operations-per-run)  option which is currently set to  30
Statistics:
Processed items: 880
├── Processed issues: 517
└── Processed PRs   : 363
Fetched items: 900
Fetched items events: 11
Fetched items comments: 11
Operations performed: 31
Github API rate used: 31
Github API rate remaining: 14956; reset at: Mon Oct 06 2025 03:25:40 GMT+0000 (Coordinated Universal Time)
state: persisting info about 880 issue(s)

Summary by CodeRabbit

Chores
- Increased the operations-per-run limit to 1000 in the stale-issue automation workflow.
- Enhances throughput for processing inactive issues per run, reducing backlogs and accelerating cleanup.
- No changes to rules or behavior of the stale/close logic; only capacity improved.

Description

Test Coverage

PR Checklist

Please review the following before submitting your PR:

PR description clearly explains what and why. If using CodeRabbit's summary, please make sure it makes sense.
PR Follows TRT-LLM CODING GUIDELINES to the best of your knowledge.
Test cases are provided for new code paths (see test instructions)
Any new dependencies have been scanned for license and vulnerabilities
CODEOWNERS updated if ownership changes
Documentation updated as needed
The reviewers assigned automatically/manually are appropriate for the PR.
Please check this after reviewing the above items as appropriate for this PR.

GitHub Bot Help

/bot [-h] ['run', 'kill', 'skip', 'reuse-pipeline'] ...

Provide a user friendly way for developers to interact with a Jenkins server.

Run /bot [-h|--help] to print this help message.

See details below for each supported subcommand.

run [--reuse-test (optional)pipeline-id --disable-fail-fast --skip-test --stage-list "A10-PyTorch-1, xxx" --gpu-type "A30, H100_PCIe" --test-backend "pytorch, cpp" --add-multi-gpu-test --only-multi-gpu-test --disable-multi-gpu-test --post-merge --extra-stage "H100_PCIe-TensorRT-Post-Merge-1, xxx" --detailed-log --debug(experimental)]

Launch build/test pipelines. All previously running jobs will be killed.

--reuse-test (optional)pipeline-id (OPTIONAL) : Allow the new pipeline to reuse build artifacts and skip successful test stages from a specified pipeline or the last pipeline if no pipeline-id is indicated. If the Git commit ID has changed, this option will be always ignored. The DEFAULT behavior of the bot is to reuse build artifacts and successful test results from the last pipeline.

--disable-reuse-test (OPTIONAL) : Explicitly prevent the pipeline from reusing build artifacts and skipping successful test stages from a previous pipeline. Ensure that all builds and tests are run regardless of previous successes.

--disable-fail-fast (OPTIONAL) : Disable fail fast on build/tests/infra failures.

--skip-test (OPTIONAL) : Skip all test stages, but still run build stages, package stages and sanity check stages. Note: Does NOT update GitHub check status.

--stage-list "A10-PyTorch-1, xxx" (OPTIONAL) : Only run the specified test stages. Examples: "A10-PyTorch-1, xxx". Note: Does NOT update GitHub check status.

--gpu-type "A30, H100_PCIe" (OPTIONAL) : Only run the test stages on the specified GPU types. Examples: "A30, H100_PCIe". Note: Does NOT update GitHub check status.

--test-backend "pytorch, cpp" (OPTIONAL) : Skip test stages which don't match the specified backends. Only support [pytorch, cpp, tensorrt, triton]. Examples: "pytorch, cpp" (does not run test stages with tensorrt or triton backend). Note: Does NOT update GitHub pipeline status.

--only-multi-gpu-test (OPTIONAL) : Only run the multi-GPU tests. Note: Does NOT update GitHub check status.

--disable-multi-gpu-test (OPTIONAL) : Disable the multi-GPU tests. Note: Does NOT update GitHub check status.

--add-multi-gpu-test (OPTIONAL) : Force run the multi-GPU tests in addition to running L0 pre-merge pipeline.

--post-merge (OPTIONAL) : Run the L0 post-merge pipeline instead of the ordinary L0 pre-merge pipeline.

--extra-stage "H100_PCIe-TensorRT-Post-Merge-1, xxx" (OPTIONAL) : Run the ordinary L0 pre-merge pipeline and specified test stages. Examples: --extra-stage "H100_PCIe-TensorRT-Post-Merge-1, xxx".

--detailed-log (OPTIONAL) : Enable flushing out all logs to the Jenkins console. This will significantly increase the log volume and may slow down the job.

--debug (OPTIONAL) : Experimental feature. Enable access to the CI container for debugging purpose. Note: Specify exactly one stage in the stage-list parameter to access the appropriate container environment. Note: Does NOT update GitHub check status.

For guidance on mapping tests to stage names, see docs/source/reference/ci-overview.md
and the scripts/test_to_stage_mapping.py helper.

kill

kill

Kill all running builds associated with pull request.

skip

skip --comment COMMENT

Skip testing for latest commit on pull request. --comment "Reason for skipping build/test" is required. IMPORTANT NOTE: This is dangerous since lack of user care and validation can cause top of tree to break.

reuse-pipeline

reuse-pipeline

Reuse a previous pipeline to validate current commit. This action will also kill all currently running builds associated with the pull request. IMPORTANT NOTE: This is dangerous since lack of user care and validation can cause top of tree to break.

Signed-off-by: Kanghwan Jang <[email protected]>

karljang · 2025-10-06T21:14:47Z

/bot run --skip-test --comment "Changing a setting of GitHub action only"

tensorrt-cicd · 2025-10-06T21:20:06Z

PR_Github #20687 Bot args parsing error: usage: /bot [-h]
{run,kill,skip,submit,reviewers,reuse-pipeline,reuse-review} ...
/bot: error: unrecognized arguments: --comment Changing a setting of GitHub action only

coderabbitai · 2025-10-06T21:25:11Z

📝 Walkthrough

Walkthrough

The GitHub Actions workflow .github/workflows/auto-close-inactive-issues.yml was updated to add operations-per-run: 1000 to the actions/stale step. No other behavioral or error-handling changes were made.

Changes

Cohort / File(s)	Summary
GitHub Actions workflow config `.github/workflows/auto-close-inactive-issues.yml`	Add `operations-per-run: 1000` to the `actions/stale` step; no other changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description Check	⚠️ Warning	While the PR includes useful context and a log excerpt, the structured “## Description” and “## Test Coverage” sections from the repository’s template remain empty placeholders rather than containing the author’s summary and test details, meaning the required template fields are incomplete.	Please move the free-form summary into the “## Description” section to explain the issue and solution, and populate the “## Test Coverage” section with relevant test cases or coverage details to demonstrate how the change is verified.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The title “[None][chore] Increase operations-per-run to 1000 for stale action” succinctly follows the repository’s naming conventions and clearly summarizes the primary change, specifying the chore type and the exact configuration update to the stale action.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests (beta)

Create PR with unit tests
Post copyable unit tests in a comment

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 27a5091 and e482867.

📒 Files selected for processing (1)

.github/workflows/auto-close-inactive-issues.yml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

GitHub Check: Pre-commit Check

🔇 Additional comments (1)

.github/workflows/auto-close-inactive-issues.yml (1)

31-31: Increase looks appropriate to clear the backlog.

Bumping operations-per-run to 1000 aligns with the run logs showing we were hitting the old cap, and we still have generous rate-limit headroom. Thanks for documenting that it’s a temporary boost so we can dial it back later if needed.

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

karljang · 2025-10-06T21:27:36Z

/bot skip --comment "Changing a setting of GitHub action only"

tensorrt-cicd · 2025-10-06T21:33:30Z

PR_Github #20688 [ skip ] triggered by Bot

tensorrt-cicd · 2025-10-06T22:02:40Z

PR_Github #20688 [ skip ] completed with state SUCCESS
Skipping testing for commit e482867

…VIDIA#8162) Signed-off-by: Kanghwan Jang <[email protected]>

Increase operations-per-run to 1000 for stale action

e482867

Signed-off-by: Kanghwan Jang <[email protected]>

karljang requested review from a team as code owners October 6, 2025 21:12

karljang requested review from venkywonka and yuanjingx87 October 6, 2025 21:12

karljang enabled auto-merge (squash) October 6, 2025 21:28

venkywonka approved these changes Oct 6, 2025

View reviewed changes

karljang merged commit 2b8722b into NVIDIA:main Oct 6, 2025
8 of 9 checks passed

dominicshanshan pushed a commit to dominicshanshan/TensorRT-LLM that referenced this pull request Nov 1, 2025

[None][chore] Increase operations-per-run to 1000 for stale action (N…

4158b7d

…VIDIA#8162) Signed-off-by: Kanghwan Jang <[email protected]>

dominicshanshan pushed a commit to dominicshanshan/TensorRT-LLM that referenced this pull request Nov 3, 2025

[None][chore] Increase operations-per-run to 1000 for stale action (N…

96d0ac2

…VIDIA#8162) Signed-off-by: Kanghwan Jang <[email protected]>

dominicshanshan pushed a commit to dominicshanshan/TensorRT-LLM that referenced this pull request Nov 3, 2025

[None][chore] Increase operations-per-run to 1000 for stale action (N…

decf926

…VIDIA#8162) Signed-off-by: Kanghwan Jang <[email protected]>

dominicshanshan pushed a commit to dominicshanshan/TensorRT-LLM that referenced this pull request Nov 3, 2025

[None][chore] Increase operations-per-run to 1000 for stale action (N…

fc4b804

…VIDIA#8162) Signed-off-by: Kanghwan Jang <[email protected]>

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

[None][chore] Increase operations-per-run to 1000 for stale action #8162

[None][chore] Increase operations-per-run to 1000 for stale action #8162

Uh oh!

karljang commented Oct 6, 2025 •

edited by coderabbitai bot

Loading

Uh oh!

karljang commented Oct 6, 2025

Uh oh!

tensorrt-cicd commented Oct 6, 2025

Uh oh!

coderabbitai bot commented Oct 6, 2025

Walkthrough

Changes

Estimated code review effort

Uh oh!

karljang commented Oct 6, 2025

Uh oh!

tensorrt-cicd commented Oct 6, 2025

Uh oh!

tensorrt-cicd commented Oct 6, 2025

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

[None][chore] Increase operations-per-run to 1000 for stale action #8162

[None][chore] Increase operations-per-run to 1000 for stale action #8162

Uh oh!

Conversation

karljang commented Oct 6, 2025 • edited by coderabbitai bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary by CodeRabbit

Description

Test Coverage

PR Checklist

GitHub Bot Help

kill

skip

reuse-pipeline

Uh oh!

karljang commented Oct 6, 2025

Uh oh!

tensorrt-cicd commented Oct 6, 2025

Uh oh!

coderabbitai bot commented Oct 6, 2025

Walkthrough

Changes

Estimated code review effort

Pre-merge checks and finishing touches

Uh oh!

karljang commented Oct 6, 2025

Uh oh!

tensorrt-cicd commented Oct 6, 2025

Uh oh!

tensorrt-cicd commented Oct 6, 2025

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

karljang commented Oct 6, 2025 •

edited by coderabbitai bot

Loading