While split groups from running PHPUnit in parallel (T50217) have brought many improvements (speed etc), they can be harder to track the status of them. How many were started? How many are still running? How many are done?
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T225730 Reduce runtime of MW shared gate Jenkins jobs to 5 min | |||
| Open | None | T50217 Speed up MediaWiki PHPUnit build by running integration tests in parallel | |||
| Open | None | T404107 Better visibility into PHPUnit split group status in CI |
Event Timeline
Comment Actions
I commented in IRC before seeing this task:
we would eventually get that for free when we switch to paratest (T50217), currently blocked by the same stuff that blocks the PHPUnit 10 update.
I'm not sure if it's worthwhile investing more time and effort into our custom PHPUnit splitter, as opposed to just getting the PHPUnit update done.
Obviously I won't prevent anyone from improving our custom code if they want to :D I just think we should bite the bullet and start doing T328919 instead. I'd be happy to help (of course), but it's a lot more than what a few people could do in their spare time.