Repository navigation
[None][test] Exclude Inductor subproc threads from integration threadleak check - #20294
Conversation
|
/bot run --disable-fail-fast |
|
PR_Github #77819 [ run ] triggered by Bot. Commit: |
|
PR_Github #77819 [ run ] completed with state
|
|
Automatically added "ci: full pre-merge approved" because this PR has satisfied the required GitHub review approvals. Unresolved review conversations and other required checks remain independent merge requirements. |
cc431c0 to
2c65502
Compare
|
/bot run --stage-list "CPU-Generic-arm-1,A10-PyTorch-1,CPU-Generic-x86-1" |
|
PR_Github #78012 [ run ] triggered by Bot. Commit: |
|
PR_Github #78012 [ run ] completed with state
|
|
/bot run --stage-list "CPU-Generic-arm-1,A10-PyTorch-1,CPU-Generic-x86-1" |
|
PR_Github #78089 [ run ] triggered by Bot. Commit: |
|
PR_Github #78089 [ run ] completed with state
|
…leak check Signed-off-by: HuiGao <huig@nvidia.com>
2c65502 to
1c7a61a
Compare
|
/bot run --disable-fail-fast |
|
PR_Github #78246 [ run ] triggered by Bot. Commit: |
|
PR_Github #78246 [ run ] completed with state
|
|
/bot run |
|
PR_Github #78351 [ run ] triggered by Bot. Commit: |
|
PR_Github #78351 [ run ] completed with state |
…ccuracy test Both parametrizations of test_rebalance_matches_baseline were waived because pytest-threadleak flagged Inductor compile-worker threads that the test's torch.compile'd logprob path starts in-process. NVIDIA#20294 added those thread names to the integration threadleak_exclude, so the test passes again and the waivers can go. Signed-off-by: Thor Johnsen <41591019+thorjohnsen@users.noreply.github.com>
This is a fix for a flaky test failure.
Dev Engineer Review
The pytest configuration now excludes
InductorSubproc,InductorSubprocHealth, andsubproc_worker_timerfrom thread-leak checks. This targets the flaky integration check, but it also means leaks from threads with these names will not be reported. No test results were provided.QA Engineer Review
tests/integration/defs/pytest.inichanged. The update modifies the thread-leak exclusion pattern; it does not add or change test functions, IDs, selectors, or waivers. No test-list change is shown. Coverage verdict: needs follow-up because no test results were provided.Per-File QA Perspective
tests/integration/defs/pytest.ini: The configuration suppresses thread-leak reports for three Inductor-related thread names. Verify that the intended integration test no longer fails and that the exclusions do not hide unrelated thread leaks.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)
If PR introduces API changes, an appropriate PR label is added - either
api-compatibleorapi-breaking. Forapi-breaking, includeBREAKINGin the PR title.Any new dependencies have been scanned for license and vulnerabilities
CODEOWNERS updated if ownership changes
Documentation updated as needed
Update tava architecture diagram if there is a significant design change in PR.
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
To see a list of available CI bot commands, please comment
/bot help.