Opened 3 days ago

Closed 43 hours ago

Last modified 37 hours ago

#36216 closed Uncategorized (invalid)

djangoci PR builds using outdated Python versions

Reported by: Mike Edmunds Owned by:
Component: Packaging Version: dev
Severity: Normal Keywords:
Cc: Mariusz Felisiak, Markus Holtermann Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no
Pull Requests:How to create a pull request

Description

The Jenkins PR builds are using outdated Python versions: 3.12.2, 3.12.7, 3.13.0.rc3, and 3.13.0. The latest releases are 3.12.9 and 3.13.2 (both 2025-02-04).

Since "We highly recommend and only officially support the latest release of each series," it seems like tests should be running on them. (Or at least, not on prereleases. And 3.12.2 is over a year old.)

To verify:

  1. Choose any recent PR at https://github.com/django/django/pulls. (I can't link to specific PR builds here, because Jenkins logs are purged very quickly.)
  2. Scroll down to the "All checks have passed" or "Some checks were not successful" block in the PR.
  3. In the checks list, click into any of the djangoci jobs (identified by a Django logo—e.g., pr-mariadb, pull-requests-focal, etc.).
  4. On the Jenkins page, click "Console Output." If there's a "Full log" link above the output, click it to expand the setup logs.
  5. Search the log for "created virtual environment" and note the Python version.

Results:

  • CPython3.12.2.final.0-64 (e.g., pull-requests-focal/database=mysql,label=focal-pr,python=python3.12)
  • CPython3.12.7.final.0-64 (e.g., pull-requests-focal/database=postgres,label=focal-pr,python=python3.12)
  • CPython3.13.0.candidate.3-64 (e.g., pull-requests-focal/database=sqlite3,label=focal-pr,python=python3.13)
  • CPython3.13.0.final.0-64 (e.g., pr-mariadb/database=mysql,label=mariadb,python=python3.13)

[Apologies if this is the wrong place to report djangoci configuration issues. I did try asking in the forum.]

Change History (4)

comment:2 by Sarah Boyce, 43 hours ago

Cc: Mariusz Felisiak Markus Holtermann added

This is the question on the forum.

This is what I know, which isn't much.

I will cc some ops team members and they can decide if they want to keep this ticket, or have a GitHub issue on jenkins-ansible.

comment:3 by Mariusz Felisiak, 43 hours ago

Trac is not a place for things related with our infrastructure. I will bump Python version in the coming days.

We highly recommend and only officially support the latest release of each series.

We use this to protect us from tickets related with bugs in older minor Python releases.

comment:4 by Mariusz Felisiak, 43 hours ago

Resolution: invalid
Status: newclosed

in reply to:  2 comment:5 by Mike Edmunds, 42 hours ago

Thanks all, I appreciate the info and followup.

Incidentally, the jenkins-ansible repo is not public. I'm sure there are good reasons for that, but it wouldn't have been possible for me to report the problem there.

Note: See TracTickets for help on using tickets.
Back to Top