Sitelet https://github.com/python/cpython/issues/122544#top
Skip to content

Change base OS image to Ubuntu-24.04 in CI testing #122544

Activity

  1. Eclips4 commented on Aug 1, 2024

    @Eclips4
    Member
  2. changed the title [-]Change base OS image to Ubuntu-24.04 in ci.yaml[/-] [+]Change base OS image to Ubuntu-24.04 in CI testing[/+] on Aug 1, 2024
  3. hugovk commented on Aug 1, 2024

    @hugovk
    Member

    Thanks for the report, we're using ubuntu-22.04 in Read the Docs, Azure Pipelines and GitHub Actions:

    ❯ rg ubuntu-22.04
    .readthedocs.yml
    11:  os: ubuntu-22.04
    
    .azure-pipelines/ci.yml
    8:    vmImage: ubuntu-22.04
    
    .azure-pipelines/pr.yml
    8:    vmImage: ubuntu-22.04
    20:    vmImage: ubuntu-22.04
    
    .github/workflows/build.yml
    47:    runs-on: ubuntu-22.04
    198:    runs-on: ubuntu-22.04
    264:    runs-on: ubuntu-22.04
    378:    runs-on: ubuntu-22.04
    
    .github/workflows/reusable-wasi.yml
    12:    runs-on: ubuntu-22.04
    
    .github/workflows/reusable-tsan.yml
    22:    runs-on: ubuntu-22.04
    
    .github/workflows/reusable-ubuntu.yml
    17:    runs-on: ubuntu-22.04

    Yes, let's upgrade, assuming all the dependencies and everything installs fine.

    Would you like to open some PRs? I suggest a separate PR for each of Read the Docs, Azure Pipelines and GitHub Actions.

  4. Damien-Chen commented on Aug 1, 2024

    @Damien-Chen
    ContributorAuthor

    Sure!, Of course, I'd love to contribute to this, let me first investigate if it would affect the result of CI testing if just simply change ubuntu-22.04 to ubuntu-24.04.

  5. picnixz commented on Aug 1, 2024

    @picnixz
    Member

    We are also using Ubuntu 22.04 for generating the configure script in the Docker image but I don't think we should change this one. This is in Tools/build/regen-configure.sh (I don't know whether the CI/CD is using its own packages or whether is using the docker script to check the configuration scripts)

  6. hugovk commented on Aug 1, 2024

    @hugovk
    Member

    The comment at the top says they should match:

    # The check_generated_files job of .github/workflows/build.yml must kept in
    # sync with this script. Use the same container image than the job so the job
    # doesn't need to run autoreconf in a container.
    IMAGE="ubuntu:22.04"

    Which should be the same as this one:

    check_generated_files:
    name: 'Check if generated files are up to date'
    # Don't use ubuntu-latest but a specific version to make the job
    # reproducible: to get the same tools versions (autoconf, aclocal, ...)
    runs-on: ubuntu-22.04

  7. picnixz commented on Aug 1, 2024

    @picnixz
    Member

    The comment at the top says they should match:

    Oh then we should update both of them then! (and I'll need to update my PR in the devguide as well)

  8. Damien-Chen commented on Aug 2, 2024

    @Damien-Chen
    ContributorAuthor

    Some other yml file based on ubunut-latest, for exmaple: in jit.yml. based on
    https://github.com/actions/runner-images description, ubuntu-latest is actually ubuntu-22.04, should those file mentioned ubuntu-latest need to upgrade ubuntu version ?

         architecture: x86_64
    
            runner: ubuntu-latest
            compiler: gcc
          - target: x86_64-unknown-linux-gnu/clang
            architecture: x86_64
            runner: ubuntu-latest
            compiler: clang
          - target: aarch64-unknown-linux-gnu/gcc
            architecture: aarch64
            runner: ubuntu-latest
            compiler: gcc
          - target: aarch64-unknown-linux-gnu/clang
            architecture: aarch64
            runner: ubuntu-latest
            compiler: clang
    
  9. hugovk commented on Aug 2, 2024

    @hugovk
    Member

    No, let's not change any ubuntu-latest.

    In fact, https://github.com/actions/runner-images?tab=readme-ov-file#available-images says ubuntu-24.04 is still beta, maybe we should wait until it is in GA (General Availability)?

    Do you know when GA is planned?

  10. Damien-Chen commented on Aug 2, 2024

    @Damien-Chen
    ContributorAuthor

    According to there discussion in
    actions/runner-images#9691
    The GA will be somewhere in August-2024, I think it should be soon.

    I think we can move all CI-testing step-by-step.
    First change trivial CI testiing(like readthedocs) to ubuntu-24.04 to make sure everything works correctly.
    If everthing goes well, then we can wait its GA and move core part(like checking JIT) to ubuntu-24.04 gradually

  11. added a commit that references this issue on Aug 2, 2024
  12. added 2 commits that reference this issue on Aug 2, 2024
  13. added a commit that references this issue on Aug 2, 2024
  14. 20 remaining items

  15. added 2 commits that reference this issue on Nov 9, 2024
  16. added a commit that references this issue on Nov 22, 2024
  17. luapun commented on Nov 25, 2024

    @luapun
  18. luapun commented on Nov 25, 2024

    @luapun
  19. added 2 commits that reference this issue on Dec 8, 2024
  20. added a commit that references this issue on Jan 11, 2025
  21. added 2 commits that reference this issue on Jan 12, 2025
  22. added a commit that references this issue on Feb 18, 2025
  23. added a commit that references this issue on Feb 18, 2025
  24. added a commit that references this issue on Feb 19, 2025
  25. added 2 commits that reference this issue on Feb 19, 2025
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

    infraCI, GitHub Actions, buildbots, Dependabot, etc.type-featureA feature request or enhancement

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions