In job config, we'll need to tell CI to take advantage of the new PHPUNIT_PARALLEL_GROUP_COUNT variable.
Ideas from Release-Engineering-Team team meeting:
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| WIP: Parallel runs: Add a group count | integration/quibble | master | +28 -1 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | brennen | T383254 Jenkins: In the integration project in WMCS, test out larger workers for CI | |||
| Open | brennen | T384517 Jenkins PHP Unit jobs split job groups based on PHPUNIT_PARALLEL_GROUP_COUNT |
Change #1200415 had a related patch set uploaded (by Brennen Bearnes; author: Brennen Bearnes):
[integration/quibble@master] WIP: Parallel runs: Add a group count
PHPUNIT_PARALLEL_GROUP_COUNT=cpus / (executers / 2) (gives us 8 for most instance, 16 for our bigger instance)
So this is wrong. I think as it stands, most instances have 8 cores, which is the current default for PHPUNIT_PARALLEL_GROUP_COUNT anyway. Most also have multiple (3) executors. I'm not sure if that's already leading to resource contention that we should worry about, but presumably someone has given this a fair amount of thought.
See above patch for a simple test proposal for the one bigger instance with a single executor.
Change #1200415 abandoned by Brennen Bearnes:
[integration/quibble@master] WIP: Parallel runs: Add a group count
Reason:
Seems like this can just be done in Jenkins directly in web UI.