- 
                Notifications
    
You must be signed in to change notification settings  - Fork 1.8k
 
Add MTP support for Online EPLB #5213
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
| 
           /bot run  | 
    
| 
           PR_Github #8888 [ run ] triggered by Bot  | 
    
| 
           PR_Github #8888 [ run ] completed with state   | 
    
| 
           /bot run --post-merge  | 
    
| 
           PR_Github #8911 [ run ] triggered by Bot  | 
    
| 
           PR_Github #8911 [ run ] completed with state   | 
    
| 
           /bot run --post-merge  | 
    
| 
           PR_Github #8931 [ run ] triggered by Bot  | 
    
| 
           PR_Github #8931 [ run ] completed with state   | 
    
| 
           /bot run --post-merge --only-multi-gpu-test  | 
    
| 
           PR_Github #8951 [ run ] triggered by Bot  | 
    
| 
           PR_Github #8951 [ run ] completed with state   | 
    
f49d6d1    to
    08874f1      
    Compare
  
    | 
           /bot run --disable-fail-fast  | 
    
| 
           PR_Github #8971 [ run ] triggered by Bot  | 
    
| 
           PR_Github #8971 [ run ] completed with state   | 
    
08874f1    to
    3f48be5      
    Compare
  
    | 
           /bot run --disable-fail-fast  | 
    
| 
           PR_Github #9030 [ run ] triggered by Bot  | 
    
| 
           PR_Github #9030 [ run ] completed with state   | 
    
3f48be5    to
    234ed8b      
    Compare
  
    | 
           /bot run --disable-fail-fast  | 
    
| 
           PR_Github #9285 [ run ] triggered by Bot  | 
    
| 
           PR_Github #9285 [ run ] completed with state   | 
    
| 
           /bot run --post-merge --only-multi-gpu-test  | 
    
| 
           PR_Github #9322 [ run ] triggered by Bot  | 
    
| 
           PR_Github #9322 [ run ] completed with state   | 
    
| 
           /bot run  | 
    
| 
           PR_Github #9422 [ run ] triggered by Bot  | 
    
| 
           PR_Github #9422 [ run ] completed with state   | 
    
| 
           /bot run --disable-fail-fast  | 
    
eebbc79    to
    89c4ea6      
    Compare
  
    | 
           /bot run --disable-fail-fast  | 
    
| 
           PR_Github #9547 [ run ] triggered by Bot  | 
    
| 
           PR_Github #9547 [ run ] completed with state   | 
    
| 
           /bot run --disable-fail-fast  | 
    
89c4ea6    to
    01eb5ee      
    Compare
  
    | 
           /bot run --disable-fail-fast  | 
    
| 
           PR_Github #9551 [ run ] triggered by Bot  | 
    
| 
           PR_Github #9551 [ run ] completed with state   | 
    
Signed-off-by: Dongxu Yang <[email protected]>
Signed-off-by: Dongxu Yang <[email protected]>
Signed-off-by: Dongxu Yang <[email protected]>
01eb5ee    to
    d093c63      
    Compare
  
    | 
           /bot run --disable-fail-fast  | 
    
| 
           PR_Github #9558 [ run ] triggered by Bot  | 
    
| 
           PR_Github #9558 [ run ] completed with state   | 
    
Signed-off-by: Dongxu Yang <[email protected]>
Signed-off-by: Dongxu Yang <[email protected]>
Signed-off-by: Dongxu Yang <[email protected]>
Signed-off-by: Dongxu Yang <[email protected]>
Signed-off-by: Dongxu Yang <[email protected]>
Signed-off-by: Dongxu Yang <[email protected]>
Signed-off-by: Dongxu Yang <[email protected]>
Signed-off-by: Dongxu Yang <[email protected]>
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".For guidance on mapping tests to stage names, see
docs/source/reference/ci-overview.md.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.