Unwaive disaggregated serving accuracy tests #5095
Conversation
|
/bot run --stage-list "DGX_H200-8_GPUs-PyTorch-[Post-Merge]-1" |
|
PR_Github #8313 [ run ] triggered by Bot |
|
PR_Github #8313 [ run ] completed with state |
Tabrizian
force-pushed
the
user/imant/removewaived2
branch
from
dfcc42d to
7430405
Compare
|
/bot run --stage-list "DGX_H200-8_GPUs-PyTorch-[Post-Merge]-1" |
|
PR_Github #8504 [ run ] triggered by Bot |
|
PR_Github #8504 [ run ] completed with state |
|
/bot run --stage-list "DGX_H200-8_GPUs-PyTorch-[Post-Merge]-1" |
|
PR_Github #8527 [ run ] triggered by Bot |
|
PR_Github #8527 [ run ] completed with state |
|
/bot run --stage-list "DGX_H200-8_GPUs-PyTorch-[Post-Merge]-1" |
|
PR_Github #8697 [ run ] triggered by Bot |
|
PR_Github #8697 [ run ] completed with state |
|
/bot run --stage-list "DGX_H200-8_GPUs-PyTorch-[Post-Merge]-1" |
|
PR_Github #8828 [ run ] triggered by Bot |
|
PR_Github #8828 [ run ] completed with state |
|
/bot run --stage-list "DGX_H200-8_GPUs-PyTorch-[Post-Merge]-1" |
|
PR_Github #8845 [ run ] triggered by Bot |
|
PR_Github #8845 [ run ] completed with state |
|
/bot run --stage-list "DGX_H200-8_GPUs-PyTorch-[Post-Merge]-1" |
|
PR_Github #9249 [ run ] triggered by Bot |
|
PR_Github #9249 [ run ] completed with state |
Tabrizian
force-pushed
the
user/imant/removewaived2
branch
2 times, most recently
from
6c03cb8 to
4c8dfd3
Compare
|
/bot run --stage-list "DGX_H200-8_GPUs-PyTorch-[Post-Merge]-1" |
|
PR_Github #9310 [ run ] triggered by Bot |
|
PR_Github #9310 [ run ] completed with state |
|
Hi @Tabrizian, I fixed this test in #5303, but got a thread leak error. Can you help take a look? |
Ah, I saw your new changes. Closing #5303. |
Tabrizian
force-pushed
the
user/imant/removewaived2
branch
2 times, most recently
from
4ca34bc to
8bde37e
Compare
|
/bot run --stage-list "DGX_H200-8_GPUs-PyTorch-[Post-Merge]-1" |
|
PR_Github #9397 [ run ] triggered by Bot |
|
PR_Github #9397 [ run ] completed with state |
Signed-off-by: Iman Tabrizian <[email protected]>
Tabrizian
force-pushed
the
user/imant/removewaived2
branch
from
8bde37e to
4e24b6a
Compare
|
/bot reuse-pipeline |
|
PR_Github #9406 [ reuse-pipeline ] triggered by Bot |
|
PR_Github #9406 [ reuse-pipeline ] completed with state |
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
killKill all running builds associated with pull request.
skip
skip --comment COMMENTSkip 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-pipelineReuse 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.