You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've noticed cibuildwheel internal CI takes quite long, which makes iterating quickly more difficult and time-consuming. I was curious if we have some ideas to speed some of those jobs up. Currently the jobs that take the longest:
The test matrix job of the GitHub Actions test.yml workflow (~40 to ~45 minutes)
The windows_38 job of the Azure DevOps azure-pipelines.yml (~70 to 90 minutes)
There might be some parallelization or other optimizations possible here to reduce the runtime of these tasks.
For a project like cibuildwheel, I also wouldn't find it the strangest to contact Microsoft to see if there's something possible in more powerful hosted CI runner hardware.
For example, in the macos_38 job of the Azure pipeline, parallelization is already used with --num-processes 2. Can we get runners with more cores on Linux and Windows as well?
Or could we split up the test set into smaller chucks each running on a separate runner?
This discussion was converted from issue #1952 on August 03, 2024 17:46.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I've noticed cibuildwheel internal CI takes quite long, which makes iterating quickly more difficult and time-consuming. I was curious if we have some ideas to speed some of those jobs up. Currently the jobs that take the longest:
test
matrix job of the GitHub Actionstest.yml
workflow (~40 to ~45 minutes)windows_38
job of the Azure DevOpsazure-pipelines.yml
(~70 to 90 minutes)There might be some parallelization or other optimizations possible here to reduce the runtime of these tasks.
For a project like cibuildwheel, I also wouldn't find it the strangest to contact Microsoft to see if there's something possible in more powerful hosted CI runner hardware.
For example, in the
macos_38
job of the Azure pipeline, parallelization is already used with--num-processes 2
. Can we get runners with more cores on Linux and Windows as well?Or could we split up the test set into smaller chucks each running on a separate runner?
Beta Was this translation helpful? Give feedback.
All reactions