NotificationsYou must be signed in to change notification settings
Fork32k
Star67.2k

Add CI job to run tests sequentially#133556

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Jump to bottom

Draft

AA-Turner wants to merge3 commits intopython:main

base:main

Choose a base branch

fromAA-Turner:ci-seq

Draft

Add CI job to run tests sequentially#133556

AA-Turner wants to merge3 commits intopython:mainfromAA-Turner:ci-seq

+65 −10

Conversation

Copy link

Member

AA-Turner commentedMay 7, 2025•
edited
Loading

Add a CI job to run all tests sequentially. This takes ~30m, so might be better as a buildbot worker?

Open questions:

How close to therelease-tools check should we make this? Currently I've mirrored it quite closely, but we probably ought to be closer to the other common test configurations.
Should the job be required, if on CI? Currently I don't think it should be.
Should we add amake target for sequential testing?

AA-Turner added2 commits

May 7, 2025 08:31

Add CI job to run tests sequentially

465140c

More similar to release-tools

dc4aac8

AA-Turner added skip issue skip news labels

May 7, 2025

AA-Turner requested review fromhugovk andezio-melotti

May 7, 2025 08:18

Copy link

Member

hugovk commentedMay 7, 2025

Thanks for this! Will take another look after the beta is out :)

This takes ~30m, so might be better as a buildbot worker?

Yeah, maybe. The current slowest job is free-threaded Windows at about 25m, so this new one would become the slowest. And hopefully we can improve the Windows one too.