GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Add FreeBSD build and test using Cirrus-CI · Issue #91960 · python/cpython

Add FreeBSD build and test using Cirrus-CI #91960

New issue
Copy link
New issue
Copy link
Closed
Closed
Add FreeBSD build and test using Cirrus-CI#91960
Copy link
Labels
buildThe build process and cross-buildThe build process and cross-buildtype-featureA feature request or enhancementA feature request or enhancement

Description

@emaste
emaste
opened on Apr 26, 2022
Issue body actions

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

Activity

Next
  1. emaste
    added
    type-featureA feature request or enhancementA feature request or enhancement
    on Apr 26, 2022
  2. erlend-aasland commented on May 16, 2022

    @erlend-aasland
    erlend-aasland
    on May 16, 2022
    Contributor
    More actions

    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.

  3. erlend-aasland
    added
    buildThe build process and cross-buildThe build process and cross-build
    pendingThe issue will be closed if no feedback is providedThe issue will be closed if no feedback is provided
    on May 16, 2022
  4. emaste commented on May 17, 2022

    @emaste
    emaste
    on May 17, 2022
    ContributorAuthor
    More actions

    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?

  5. erlend-aasland
    removed
    pendingThe issue will be closed if no feedback is providedThe issue will be closed if no feedback is provided
    on May 17, 2022
  6. erlend-aasland commented on May 17, 2022

    @erlend-aasland
    erlend-aasland
    on May 17, 2022
    Contributor
    More actions

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

  7. emaste commented on May 17, 2022

    @emaste
    emaste
    on May 17, 2022
    ContributorAuthor
    More actions

    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.

    Reacted by Erlend E. Aasland
  8. sorcio commented on Sep 5, 2023

    @sorcio
    sorcio
    on Sep 5, 2023
    Contributor
    More actions

    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?

  9. vstinner commented on Sep 5, 2023

    @vstinner
    vstinner
    on Sep 5, 2023
    Member
    More actions

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

    Reacted by Davide Rizzo
  10. vstinner commented on Sep 5, 2023

    @vstinner
    vstinner
    on Sep 5, 2023
    Member
    More actions

    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!

    Reacted by Davide Rizzo
  11. sorcio commented on Sep 5, 2023

    @sorcio
    sorcio
    on Sep 5, 2023
    Contributor
    More actions

    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.

  12. vstinner commented on Sep 5, 2023

    @vstinner
    vstinner
    on Sep 5, 2023
    Member
    More actions

    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.

  13. vstinner commented on Sep 5, 2023

    @vstinner
    vstinner
    on Sep 5, 2023
    Member
    More actions

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

  14. vstinner
    added a commit that references this issue on Sep 6, 2023

    pythongh-91960: Add FreeBSD build and test using Cirrus-CI

    ca50385
  15. 9 remaining items

  16. vstinner
    added a commit that references this issue on Sep 6, 2023

    [3.11] gh-91960: Skip test_gdb if gdb cannot retrive Python frames (G…

    d61b8f9
  17. vstinner
    closed this as completedon Sep 6, 2023
  18. vstinner
    added 2 commits that reference this issue on Sep 8, 2023

    pythongh-91960: Cirrus CI runs configure in a separate step

    7169f22

    pythongh-91960: FreeBSD Cirrus CI runs configure separately

    9213522
  19. Yhg1s
    added a commit that references this issue on Sep 8, 2023

    [3.12] gh-91960: Skip test_gdb if gdb cannot retrive Python frames (G…

    4b749ba
  20. vstinner
    added 3 commits that reference this issue on Sep 8, 2023

    gh-91960: FreeBSD Cirrus CI runs configure separately (#109127)

    15d659f

    pythongh-91960: Disable Cirrus CI for now

    c0d3ce3

    pythongh-91960: Disable Cirrus CI for now

    a8eabf5
  21. vstinner commented on Sep 15, 2023

    @vstinner
    vstinner
    on Sep 15, 2023
    Member
    More actions

    I wrote PR #109457 to disable the job: Python is out of free credit and so all jobs are reported as failure.

  22. vstinner
    added a commit that references this issue on Sep 15, 2023

    gh-91960: Disable Cirrus CI for now (#109457)

    8ea4ad4
  23. vstinner
    added 2 commits that reference this issue on Jan 11, 2024

    pythongh-91960: Remove Cirrus CI configuration

    57efc94

    gh-91960: Remove Cirrus CI configuration (#113938)

    7ed76fc
  24. kulikjak
    added a commit that references this issue on Jan 22, 2024

    pythongh-91960: Remove Cirrus CI configuration (python#113938)

    4a0b2c2
  25. aisk
    added a commit that references this issue on Feb 11, 2024

    pythongh-91960: Remove Cirrus CI configuration (python#113938)

    67a56c2
  26. Glyphack
    added a commit that references this issue on Sep 2, 2024

    pythongh-91960: Remove Cirrus CI configuration (python#113938)

    ad05e32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    buildThe build process and cross-buildThe build process and cross-buildtype-featureA feature request or enhancementA feature request or enhancement

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      You are visitor 01402503 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.