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
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 insys.float_info, but Android lackspythoninfodata.I had a look at
Android/android.pyand 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 forpython -m test.pythoninfowould be inefficient.Instead, I propose adding a
--pythoninfooption topython -m testso we can dump build information and run the test suite in a single command.Linked PRs