-
Couldn't load subscription status.
- Fork 1.8k
[None][fix] disagg ctx pp4 + gen pp4 integ test #6489
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
Signed-off-by: raayandhar <[email protected]>
|
/bot run |
📝 WalkthroughWalkthroughThe disaggregated tests in Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Suggested reviewers
Note ⚡️ Unit Test Generation is now available in beta!Learn more here, or try it out under "Finishing Touches" below. 📜 Recent review detailsConfiguration used: .coderabbit.yaml 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
✨ Finishing Touches🧪 Generate unit tests
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
Documentation and Community
|
|
PR_Github #13562 [ run ] triggered by Bot |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This failure was because TinyLlama has 22 hidden layers, which is not divisible by 4.
Is it a generic limitation of PP for AGG or this limitation only exists for disaggregated serving?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What was the behavior with Tiny Llama? Would it just hang? If so, could we catch this issue and return a clear error message?
Just running the test it would timeout. In the actual output logs, we actually get an output message complaining about how we can't divide the layers into the stages, but I think the timeout comes faster than the error propagation. I can look into seeing if we can return a clearer error message earlier. In the non-pytest case this error returns pretty quickly. |
My understanding is that for N pipeline parallel ranks/stages, the number of layers must be divisible by N in our current implementation for the pipeline parallelism to work. So unless the agg implementation/support is more flexible where we can more freely decide how to split the model layers into sequential stages, I think this is a generic limitation of PP in our current implementation. cc @pcastonguay to confirm? |
Signed-off-by: raayandhar <[email protected]>
It seems like regardless of the root cause error (unless it is pytest related, this is my experience facing a variety of different errors), we will hang and time out with |
Signed-off-by: raayandhar <[email protected]>
|
PR_Github #13562 [ run ] completed with state |
Signed-off-by: raayandhar <[email protected]>
|
/bot run |
|
PR_Github #13708 [ run ] triggered by Bot |
|
PR_Github #13708 [ run ] completed with state |
|
/bot run --disable-fail-fast |
Signed-off-by: Raayan Dhar <[email protected]>
|
/bot kill |
|
/bot run --disable-fail-fast |
|
PR_Github #13720 [ run ] triggered by Bot |
|
PR_Github #14171 [ run ] triggered by Bot |
|
PR_Github #14171 [ run ] completed with state |
Signed-off-by: raayandhar <[email protected]>
|
/bot run |
|
PR_Github #14174 [ run ] triggered by Bot |
|
PR_Github #14174 [ run ] completed with state |
|
/bot run --disable-fail-fast |
|
PR_Github #14182 [ run ] triggered by Bot |
|
PR_Github #14182 [ run ] completed with state |
|
/bot run --disable-fail-fast |
|
PR_Github #14195 [ run ] triggered by Bot |
|
PR_Github #14195 [ run ] completed with state |
|
/bot run |
|
PR_Github #14313 [ run ] triggered by Bot |
|
/bot run --only-multi-gpu-test |
|
PR_Github #14326 [ run ] triggered by Bot |
|
PR_Github #14313 [ run ] completed with state |
|
PR_Github #14326 [ run ] completed with state |
|
/bot run --disable-multi-gpu-test |
|
PR_Github #14357 [ run ] triggered by Bot |
|
PR_Github #14357 [ run ] completed with state |
|
/bot skip --comment "Single and multi gpu tests passed separately" |
|
PR_Github #14472 [ skip ] triggered by Bot |
|
PR_Github #14472 [ skip ] completed with state |
Signed-off-by: raayandhar <[email protected]> Signed-off-by: Raayan Dhar <[email protected]>
Summary by CodeRabbit
Description
Per this PR for disagg PP support on the PyTorch backend, we faced an issue where the ctx pp4 + gen pp4 integration test would fail.
This failure was because TinyLlama has 22 hidden layers, which is not divisible by 4. Switching this to Llama3-8B (has 32 hidden layers) should fix this. The test is registered under H200s, so the increased space needed for the model size should not be an issue.
Test Coverage
n/a
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 [--reuse-test (optional)pipeline-id --disable-fail-fast --skip-test --stage-list "A10-PyTorch-1, xxx" --gpu-type "A30, H100_PCIe" --test-backend "pytorch, cpp" --add-multi-gpu-test --only-multi-gpu-test --disable-multi-gpu-test --post-merge --extra-stage "H100_PCIe-TensorRT-Post-Merge-1, xxx" --detailed-log --debug(experimental)]Launch build/test pipelines. All previously running jobs will be killed.
--reuse-test (optional)pipeline-id(OPTIONAL) : Allow the new pipeline to reuse build artifacts and skip successful test stages from a specified pipeline or the last pipeline if no pipeline-id is indicated. If the Git commit ID has changed, this option will be always ignored. The DEFAULT behavior of the bot is to reuse build artifacts and successful test results from the last pipeline.--disable-reuse-test(OPTIONAL) : Explicitly prevent the pipeline from reusing build artifacts and skipping successful test stages from a previous pipeline. Ensure that all builds and tests are run regardless of previous successes.--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-PyTorch-1, xxx"(OPTIONAL) : Only run the specified test stages. Examples: "A10-PyTorch-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.--test-backend "pytorch, cpp"(OPTIONAL) : Skip test stages which don't match the specified backends. Only support [pytorch, cpp, tensorrt, triton]. Examples: "pytorch, cpp" (does not run test stages with tensorrt or triton backend). Note: Does NOT update GitHub pipeline 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 in addition to running 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-TensorRT-Post-Merge-1, xxx"(OPTIONAL) : Run the ordinary L0 pre-merge pipeline and specified test stages. Examples: --extra-stage "H100_PCIe-TensorRT-Post-Merge-1, xxx".--detailed-log(OPTIONAL) : Enable flushing out all logs to the Jenkins console. This will significantly increase the log volume and may slow down the job.--debug(OPTIONAL) : Experimental feature. Enable access to the CI container for debugging purpose. Note: Specify exactly one stage in thestage-listparameter to access the appropriate container environment. Note: Does NOT update GitHub check status.For guidance on mapping tests to stage names, see
docs/source/reference/ci-overview.mdand the
scripts/test_to_stage_mapping.pyhelper.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.