Skip to content

[Cherry-Pick][CI] Sync parallelism optimization from dev to 2.5 (#7085)#7140

Open
EmmonsCurse wants to merge 2 commits intoPaddlePaddle:release/2.5from
EmmonsCurse:ci_optimize_25_402
Open

[Cherry-Pick][CI] Sync parallelism optimization from dev to 2.5 (#7085)#7140
EmmonsCurse wants to merge 2 commits intoPaddlePaddle:release/2.5from
EmmonsCurse:ci_optimize_25_402

Conversation

@EmmonsCurse
Copy link
Copy Markdown
Collaborator

Cherry-pick of #7085 #7132 #7138 (authored by @EmmonsCurse) to release/2.5.

devPR:#7085 #7132 #7138


Motivation

  • Current unittest execution runs mostly in a sequential manner, leading to low GPU utilization and long CI turnaround time. In addition, when tests fail, logs are scattered and not easy to locate, which increases debugging cost.
  • Removing --ipc=host exposed shared memory related issues (e.g., IPC/SHM allocation failures) and default Docker /dev/shm (64MB) is insufficient for multi-process / multi-GPU tests

Modifications

  • Introduce single-GPU parallel execution by splitting independent tests into multiple shards
  • Classify tests into multi-GPU and single-GPU to ensure correct scheduling
  • Execute multi-GPU tests sequentially to avoid resource conflicts
  • Remove residual console_error.log* files and ensure only failed test cases keep their log directories
  • Package and upload logs for easier debugging and traceability
  • Remove --ipc=host to avoid cross-task interference
  • Add --shm-size=64g to ensure sufficient shared memory for model serving
  • Add --sysctl kernel.msgmax and kernel.msgmnb to support larger IPC message queues
  • Keep container-level isolation while ensuring stability for multi-GPU workloads

Usage or Command

N/A

Accuracy Tests

N/A

Checklist

  • Add at least a tag in the PR title.
  • Tag list: [[FDConfig],[APIServer],[Engine], [Scheduler], [PD Disaggregation], [Executor], [Graph Optimization], [Speculative Decoding], [RL], [Models], [Quantization], [Loader], [OP], [KVCache], [DataProcessor], [BugFix], [Docs], [CI], [Optimization], [Feature], [Benchmark], [Others], [XPU], [HPU], [GCU], [DCU], [Iluvatar], [Metax]]
  • You can add new tags based on the PR content, but the semantics must be clear.
  • Format your code, run pre-commit before commit.
  • Add unit tests. Please write the reason in this PR if no unit tests.
  • Provide accuracy results.
  • If the current PR is submitting to the release branch, make sure the PR has been submitted to the develop branch, then cherry-pick it to the release branch with the [Cherry-Pick] PR tag.

@EmmonsCurse
Copy link
Copy Markdown
Collaborator Author

EmmonsCurse commented Apr 1, 2026

/skip-ci ci_iluvatar
/skip-ci ci_hpu
/skip-ci build_xpu
/skip-ci gpu_4cards_test
/skip-ci pre_ce_test
/skip-ci stable_test

@paddle-bot
Copy link
Copy Markdown

paddle-bot bot commented Apr 1, 2026

Thanks for your contribution!

@codecov-commenter
Copy link
Copy Markdown

codecov-commenter commented Apr 1, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
⚠️ Please upload report for BASE (release/2.5@14676a3). Learn more about missing BASE report.

Additional details and impacted files
@@              Coverage Diff               @@
##             release/2.5    #7140   +/-   ##
==============================================
  Coverage               ?   69.03%           
==============================================
  Files                  ?      390           
  Lines                  ?    54234           
  Branches               ?     8555           
==============================================
  Hits                   ?    37442           
  Misses                 ?    14079           
  Partials               ?     2713           
Flag Coverage Δ
GPU 69.03% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants