Skip to content

Android/iOS buildbot should run python -m test.pythoninfo #146410

Description

@vstinner

Currently, "aarch64 Android 3.x" buildbot worker "only" runs the test suite: https://buildbot.python.org/#/builders/1594/builds/4352. It doesn't run the "python -m test.pythoninfo" step.

pythoninfo is useful to debug test failures and collect build information. For example, I wanted to check if Android defines the __STDC_IEC_559__ C macro: I looked for iec_60559 in sys.float_info, but Android lacks pythoninfo data.

I had a look at Android/android.py and it seems like launching a single Python process is quite heavy. It unpack the Python package, launches "gradle" which download stuff, setup a logger, etc. So it seems like launching a second Python process just for python -m test.pythoninfo would be inefficient.

Instead, I propose adding a --pythoninfo option to python -m test so we can dump build information and run the test suite in a single command.

Linked PRs

Activity

  1. added a commit that references this issue on Mar 25, 2026
  2. freakboy3742 commented on Mar 26, 2026

    @freakboy3742
    Contributor

    Agreed this is a good idea; the iOS builds would benefit from this as well.

  3. added 2 commits that reference this issue on Mar 26, 2026
  4. vstinner commented on Mar 26, 2026

    @vstinner
    MemberAuthor

    Agreed this is a good idea; the iOS builds would benefit from this as well.

    I wrote #146457 to run also tests with with --pythoninfo on iOS.

  5. added a commit that references this issue on Mar 26, 2026
  6. changed the title [-]Android buildbot should run `python -m test.pythoninfo`[/-] [+]Android/iOS buildbot should run `python -m test.pythoninfo`[/+] on Mar 26, 2026
  7. vstinner commented on Mar 26, 2026

    @vstinner
    MemberAuthor

    Ok, Android and iOS now dump the Python build information at the start of the test suite output. It works as expected. I close the issue.

  8. added 2 commits that reference this issue on Mar 26, 2026
  9. added 3 commits that reference this issue on Apr 16, 2026
  10. added 3 commits that reference this issue on Apr 25, 2026
  11. added a commit that references this issue on Oct 5, 2026
  12. added a commit that references this issue on Oct 9, 2026
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

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions