From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?Q?G=C3=A1bor?= Boskovits Subject: bug#22533: Python bytecode reproducibility Date: Tue, 6 Mar 2018 15:57:02 +0100 Message-ID: References: <20160202051544.GA11744@jasmine> <87bmqfu44s.fsf@fastmail.com> <87606c23bq.fsf@elephly.net> <874llw101c.fsf@elephly.net> <871sgz1wg0.fsf@elephly.net> <87h8pu153i.fsf@fastmail.com> <87muzlib8u.fsf@elephly.net> <87ina9i7sw.fsf@elephly.net> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="001a1144a158c35d230566bfa7af" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:40852) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1etE2Y-0006ps-5B for bug-guix@gnu.org; Tue, 06 Mar 2018 09:58:07 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1etE2U-0005zv-4D for bug-guix@gnu.org; Tue, 06 Mar 2018 09:58:06 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:39955) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1etE2T-0005zk-VH for bug-guix@gnu.org; Tue, 06 Mar 2018 09:58:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1etE2T-0002XU-On for bug-guix@gnu.org; Tue, 06 Mar 2018 09:58:01 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <87ina9i7sw.fsf@elephly.net> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Ricardo Wurmus Cc: 22533@debbugs.gnu.org --001a1144a158c35d230566bfa7af Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 2018-03-06 15:43 GMT+01:00 Ricardo Wurmus : > > Ricardo Wurmus writes: > > > Marius Bakke writes: > > > >> I suppose we'll have to set PYTHONHASHSEED somewhere in > >> python-build-system as well. Did you check if that makes a difference > >> for numpy? Perhaps it's enough to set it if we add an auto-compilatio= n > >> step? > > > > Right, I=E2=80=99m going to test this with numpy now. Thanks for the h= int! > > It did help with one file, which is now built reproducibly, namely > > lib/python3.6/site-packages/numpy/testing/nose_tools/__ > pycache__/utils.cpython-36.pyc > > This leaves five files in numpy that shouldn=E2=80=99t be but unfortunate= ly are > different. > > Unfortunately backporting the upstream version is not straightforward at all. There are too many changes. I will have a look at those test failures instead. > -- > Ricardo > > GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC > https://elephly.net > > > --001a1144a158c35d230566bfa7af Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
2018= -03-06 15:43 GMT+01:00 Ricardo Wurmus <rekado@elephly.net>:=

Ricardo Wurmus <rekado@elephly.net= > writes:

> Marius Bakke <mbakke@fastmai= l.com> writes:
>
>> I suppose we'll have to set PYTHONHASHSEED somewhere in
>> python-build-system as well.=C2=A0 Did you check if that makes a d= ifference
>> for numpy?=C2=A0 Perhaps it's enough to set it if we add an au= to-compilation
>> step?
>
> Right, I=E2=80=99m going to test this with numpy now.=C2=A0 Thanks for= the hint!

It did help with one file, which is now built reproducibly, namely
=C2=A0 lib/python3.6/site-packages/numpy/testing/nose_tools/__pyc= ache__/utils.cpython-36.pyc

This leaves five files in numpy that shouldn=E2=80=99t be but unfortunately= are
different.

<= br>
Unfortunately backporting the upstream version is not straigh= tforward at all.
There are too many changes. I will have a look a= t those test failures instead.
=C2=A0
--
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6=C2=A0 2150 197A 5888 235F ACAC
https:= //elephly.net



--001a1144a158c35d230566bfa7af--