[TRTLLM-4886][infra]Try another timeout opt to exit test thread directly instead of gracefully

[EmmaQiaoCh]

PR title

Please write the PR title by following template:

[JIRA ticket link/nvbug link/github issue link][fix/feat/doc/infra/...] <summary of this PR>

For example, assume I have a PR hope to support a new feature about cache manager of Jira TRTLLM-1000 ticket, it would be like

[TRTLLM-1000][feat] Support a new feature about cache manager

Description

Please explain the issue and the solution in short.

Test Coverage

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 [--disable-fail-fast --skip-test --stage-list "A10-1, xxx" --gpu-type "A30, H100_PCIe" --add-multi-gpu-test --only-multi-gpu-test --disable-multi-gpu-test --post-merge --extra-stage "H100_PCIe-[Post-Merge]-1, xxx"]

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

--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-1, xxx" (OPTIONAL) : Only run the specified test stages. Examples: "A10-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.

--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. Will also run 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-[Post-Merge]-1, xxx" (OPTIONAL) : Run the ordinary L0 pre-merge pipeline and specified test stages. Examples: --extra-stage "H100_PCIe-[Post-Merge]-1, xxx".

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.

[EmmaQiaoCh]

/bot run --stage-list "DGX_H100-4_GPUs-PyTorch-Others-1"

[tensorrt-cicd]

PR_Github #5237 [ run ] triggered by Bot

[tensorrt-cicd]

PR_Github #5237 [ run ] completed with state FAILURE
/LLM/main/L0_MergeRequest_PR pipeline #3825 (Partly Tested) completed with status: 'FAILURE'

[EmmaQiaoCh]

/bot run --stage-list "DGX_H100-4_GPUs-PyTorch-Others-1"

[tensorrt-cicd]

PR_Github #5287 [ run ] triggered by Bot

[tensorrt-cicd]

PR_Github #5287 [ run ] completed with state FAILURE
/LLM/main/L0_MergeRequest_PR pipeline #3863 (Partly Tested) completed with status: 'FAILURE'

[EmmaQiaoCh]

/bot run --stage-list "DGX_H100-4_GPUs-PyTorch-Others-1"

[tensorrt-cicd]

PR_Github #5342 [ run ] triggered by Bot

[EmmaQiaoCh]

/bot run --post-merge --disable-fail-fast

[tensorrt-cicd]

PR_Github #5357 [ run ] triggered by Bot

[tensorrt-cicd]

PR_Github #5342 [ run ] completed with state ABORTED

[chzblych]

/bot kill

[tensorrt-cicd]

PR_Github #5369 [ kill ] triggered by Bot

[tensorrt-cicd]

PR_Github #5357 [ run ] completed with state ABORTED

[tensorrt-cicd]

PR_Github #5369 [ kill ] completed with state SUCCESS
Successfully killed previous jobs for commit eadc0a2

[chzblych]

/bot run --skip-test

[tensorrt-cicd]

PR_Github #5449 [ run ] triggered by Bot

[tensorrt-cicd]

PR_Github #5449 [ run ] completed with state SUCCESS
/LLM/main/L0_MergeRequest_PR pipeline #3976 (Partly Tested) completed with status: 'SUCCESS'

[EmmaQiaoCh]

/bot skip --comments "Tested the scenario in previous CIs"

[EmmaQiaoCh]

/bot skip --comment "Tested the scenario in previous CIs"

[tensorrt-cicd]

PR_Github #5499 Bot args parsing error: usage: /bot skip --comment COMMENT
/bot skip: error: the following arguments are required: --comment

[tensorrt-cicd]

PR_Github #5500 [ skip ] triggered by Bot

[EmmaQiaoCh]

We now set the '--timeout-method=thread' both when launch pytest in CI but also in unittests call sub pytest cases.
And we tested below scenario:

• If the hang occurred in sub unittests, the sub pytest thread will exit with timeout directly, but it won't impact the following cases in outside pytest list;(refer job: https://prod.blsm.nvidia.com/sw-tensorrt-top-1/blue/organizations/jenkins/LLM%2Fmain%2FL0_Test-x86_64/detail/L0_Test-x86_64/11134/pipeline/)
• If the hang occurred in normal tests, the hang case thread will exit with timeout directly, the test stage failed and no test report genertated; (Like this job: https://prod.blsm.nvidia.com/sw-tensorrt-top-1/blue/organizations/jenkins/LLM%2Fmain%2FL0_Test-x86_64/detail/L0_Test-x86_64/11021/pipeline/159/)

[tensorrt-cicd]

PR_Github #5500 [ skip ] completed with state SUCCESS
Skipping testing for commit cb2bf5e