[Python-Dev] Failing tests (on a Linux distro) (original) (raw)
Victor Stinner vstinner at redhat.com
Wed Jul 4 08:30:05 EDT 2018
- Previous message (by thread): [Python-Dev] Failing tests (on a Linux distro)
- Next message (by thread): [Python-Dev] Failing tests (on a Linux distro)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Yes, see my issue https://bugs.python.org/issue34022 to discuss how to fix tests.
Victor
2018-07-04 14:05 GMT+02:00 Nick Coghlan <ncoghlan at gmail.com>:
On 4 July 2018 at 22:00, Nick Coghlan <ncoghlan at gmail.com> wrote:
On 2 July 2018 at 17:38, Petr Viktorin <encukou at gmail.com> wrote:
Anyway, the SUSE tests seem to fail on .pyc files. The main change in that area was [PEP 552], try starting there. AFAIK, SUSE is ahead of Fedora in the reproducible builds area; perhaps that's where the difference is.
In particular, if a build system sets SOURCEDATEEPOCH without specifying a pyc format for pycompile or compileall, Python 3.7 will give you checked hashes by default: https://docs.python.org/3/library/pycompile.html?highlight=sourcedateepoch#pycompile.compile Running the following locally fails for me: $ SOURCEDATEEPOCH=
date./python -m test testpycompile testcompileall So my guess would be that this is a test suite error where we're not handling the "running in a reproducible build environment with SOURCEDATEEPOCH already set" case. Cheers, Nick. -- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
Python-Dev mailing list Python-Dev at python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/vstinner%40redhat.com
- Previous message (by thread): [Python-Dev] Failing tests (on a Linux distro)
- Next message (by thread): [Python-Dev] Failing tests (on a Linux distro)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]