This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author gregory.p.smith
Recipients Mark.Shannon, eric.snow, gregory.p.smith, kumaraditya, lys.nikolaou, pablogsal, terry.reedy, tim.peters, vstinner, xtreak
Date 2022-01-30.08:04:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
If a decent parallelism CI systems are not available from github (they seem stuck at 2-3 threads per, an alternative approach could be to shard across multiple parallel CI tasks. Shard such that each one gets only one of the slow tests.

Unfortunately if each of these were a line item in Github's poor CI UI sharding a single config's tests across 5-10 tasks would be a nightmare to navigate on a PR.  I expect everyone would hate that.

Providing our own runners with decent parallelism could help:

But we're always going to be bound by our longest tail test if we don't fix our test parallelism to be more granular.
Date User Action Args
2022-01-30 08:04:08gregory.p.smithsetrecipients: + gregory.p.smith, tim.peters, terry.reedy, vstinner, Mark.Shannon, eric.snow, lys.nikolaou, pablogsal, xtreak, kumaraditya
2022-01-30 08:04:08gregory.p.smithsetmessageid: <>
2022-01-30 08:04:08gregory.p.smithlinkissue46524 messages
2022-01-30 08:04:08gregory.p.smithcreate