Skip to main content


#curl is now officially running more than 200 CI jobs per PR.

Most of them run about 2000 tests each.

Almost 400K test runs in total.

#curl

treefit reshared this.

in reply to daniel:// stenberg://

Why are there so many ? Are there that many different platforms curl can run on or are they mostly different versions of a handful of platform/OSes ?
in reply to Thibault

@thibault platforms, build combinations, different 3rd party libraries, different debug/analyzers/scanners, different build systems
in reply to daniel:// stenberg://

Are those de-duplicated? How are dealing with push vs PR builds?

#SFML is currently getting ~100 builds, but on a PR it's always duplicated because we can't (easily) get GitHub Actions to ignore PR if it also runs for push.

#sfml
in reply to Lukas

@darkcisum they run for every PR and when pushed to master. As they should. What's to dedupe?
in reply to daniel:// stenberg://

So you have push only set up for master? Meaning, if you don't open a PR for a feature branch, no builds are executed?
in reply to Lukas

@darkcisum we don't do feature branches, or rather they don't need to run any tests until they become a PR
in reply to Johan Lindskogen

Most of them complete within 20 minutes, typically all of them within 30 minutes. But we have worked HARD recently to get hem down to this. Used to be multiple hours.
This entry was edited (1 week ago)
in reply to daniel:// stenberg://

That’s really impressive. We’re lucky if our iOS build completes within 45 mins.