Add FreeBSD build and test using Cirrus-CI

[emaste]

Feature or enhancement

Add FreeBSD build and test using Cirrus-CI (for pull requests)

Pitch

Cirrus-CI is a hosted CI service that supports FreeBSD, Linux, macOS, and Winodws. Add a .cirrus.yml to provide CI coverage on pull requests for FreeBSD 12.3 and 13.0.

Adding a .cirrus.yml to build + test on FreeBSD will add coverage for pull requests. (The Cirrus-CI application would need to be enabled on the cpython repo.)

Here is an example run from my fork: https://cirrus-ci.com/build/5512210465161216

Previous discussion

Linked PRs

• gh-91960: Add FreeBSD build and test using Cirrus-CI #91961
• gh-91960: Add FreeBSD build and test using Cirrus-CI [DEBUG PR] #108972
• gh-91960: skip test_gdb when built with clang #108993
• gh-91960: Skip test_gdb if gdb cannot retrive Python frames #108999
• [3.12] gh-91960: Skip test_gdb if gdb cannot retrive Python frames (GH-108999) #109010
• [3.11] gh-91960: Skip test_gdb if gdb cannot retrive Python frames (GH-108999) #109011
• gh-91960: FreeBSD Cirrus CI runs configure separately #109127
• gh-91960: Disable Cirrus CI for now #109457
• gh-91960: Remove Cirrus CI configuration #113938

[erlend-aasland]

We've currently got two stable FreeBSD 14.0 buildbots in our "extended" CI:

• https://buildbot.python.org/all/#/builders/172
• https://buildbot.python.org/all/#/builders/483

The buildbots run on every merge to main, and also on PR's where it is explicitly requested by a core dev or triager, so we do get FreeBSD coverage for everything that is merged. Of course, adding FreeBSD 13.0 and 12.3 would be a welcome addition to our buildbot fleet. See these links for more info:

• https://devguide.python.org/buildworker/
• https://github.com/python/buildmaster-config

I don't think we will be adding FreeBSD to our main CI, though, so I suggest closing this issue.

[emaste]

I did this based on @vstinner's comment that there's no pull request CI for FreeBSD and inquiry about whether there's a service that supports it. I'm sure FreeBSD 13.1/12.3 bots could be added instead, but is there a reason having comprehensive pre-merge CI for FreeBSD would be undesirable?

[erlend-aasland]

If Victor is +1 for adding a FreeBSD CI, then I suggest opening a PR :)

[emaste]

It's #91961

I opened this issue because the pull request template told me I needed one - apologies if I missed the appropriate metadata here or in the PR to cross-reference them.

I'd be happy to help out with getting 12.x/13.x buildbot workers attached instead if that's the desired approach, but Cirrus-CI has the nice property of being a hosted service that does not require ongoing maintenance on the workers, and can easily be updated to use any FreeBSD images that are available in GCP.

[sorcio]

We've currently got two stable FreeBSD 14.0 buildbots in our "extended" CI

Hey @erlend-aasland, has the situation changed? The FreeBSD buildbot workers have been offline for a while. Being listed as a tier-3 platform I guess there is supposed to be at least one running buildbot but that hasn't been the case for the last few months. May I ask you or @vstinner to check the current status?

[vstinner]

Please have a look at PR #104574: a change proposes to use GNU make syntax which is not compatible with FreeBSD bsdmake.

[vstinner]

May I ask you or @vstinner to check the current status?

One week ago, the two FreeBSD buildbot were removed: python/buildmaster-config#386

I'm looking for a solution to keep running tests automatically on FreeBSD and get notifications if something breaks. Add a new buildbot worker, add a GitHub Action job, or both!

[sorcio]

Oh, that's unfortunate. I don't have the resources to support a buildbot myself. But let me know if I can do anything to help make an automated job happen. As far as I can see GitHub Actions doesn't support running FreeBSD on their infrastructure, but some projects are running it on a VM. That might work.

Cirrus-CI might be an alternative, apparently, given this issue and relative PR, although I'm not familiar with them. Recently they introduced a limit to free usage which Python would likely exceed. So someone would have to get in touch and ask for additional resources for Python.

[vstinner]

Oh, that's unfortunate. I don't have the resources to support a buildbot myself. But let me know if I can do anything to help make an automated job happen.

I contact some FreeBSD developers who are interesed to set up new FreeBSD buildbot workers, especially Kurt Jaeger. Ping me in private if you want me to get in touch with them.

[vstinner]

Also, the Cirrus-CI approach is happening, see the PR of this issue: PR #91961.