[feat] add b200 support via slurm #4709
Conversation
|
/bot run --stage-list "B200-4_GPUs-PyTorch-[Post-Merge]-1" |
|
PR_Github #6673 [ run ] triggered by Bot |
|
PR_Github #6673 [ run ] completed with state |
yuanjingx87
force-pushed
the
user/yuanjingx/add_b200_tests
branch
from
9cfd8ef to
243fa98
Compare
|
/bot run --stage-list "DGX_B200-4_GPUs-PyTorch-[Post-Merge]-1" |
|
PR_Github #6721 [ run ] triggered by Bot |
|
PR_Github #6721 [ run ] completed with state |
|
/bot run --stage-list "DGX_B200-4_GPUs-PyTorch-[Post-Merge]-1" |
|
PR_Github #6785 [ run ] triggered by Bot |
|
PR_Github #6785 [ run ] completed with state |
|
/bot run --stage-list "DGX_B200-4_GPUs-PyTorch-[Post-Merge]-1" |
|
PR_Github #6795 [ run ] triggered by Bot |
|
PR_Github #6795 [ run ] completed with state |
yuanjingx87
force-pushed
the
user/yuanjingx/add_b200_tests
branch
from
243fa98 to
6d054e3
Compare
|
/bot run --stage-list "DGX_B200-4_GPUs-PyTorch-[Post-Merge]-1,GB200-4_GPUs-PyTorch-[Post-Merge]-1" |
|
PR_Github #6809 [ run ] triggered by Bot |
|
PR_Github #6809 [ run ] completed with state |
Signed-off-by: Yuanjing Xue <[email protected]>
Signed-off-by: Yuanjing Xue <[email protected]>
Signed-off-by: Yuanjing Xue <[email protected]>
Signed-off-by: Yuanjing Xue <[email protected]>
yuanjingx87
force-pushed
the
user/yuanjingx/add_b200_tests
branch
from
e95ce13 to
5726ce8
Compare
|
/bot run --stage-list "DGX_B200-4_GPUs-PyTorch-[Post-Merge]-1,GB200-4_GPUs-PyTorch-[Post-Merge]-1" |
|
PR_Github #6852 [ run ] triggered by Bot |
|
PR_Github #6852 [ run ] completed with state |
|
/bot skip --comment "Partial testing is sufficient" |
|
PR_Github #6898 [ skip ] triggered by Bot |
|
PR_Github #6898 [ skip ] completed with state |
|
/bot run --stage-list "DGX_H100-4_GPUs-PyTorch-Others-1" |
|
PR_Github #6944 [ ] completed with state |
Signed-off-by: Yuanjing Xue <[email protected]> Signed-off-by: darraghdog <[email protected]>
5 participants
Description
add b200 testing support in CI via slurm
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.