GNU bug report logs - #39310
MariaDB reproducibility issue

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 39310 in the body.
You can then email your comments to 39310 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Josh <randomenduser <at> fastmail.com>
To: bug-guix <at> gnu.org
Subject: MariaDB reproducibility issue
Date: Mon, 27 Jan 2020 08:23:09 -0600

[Message part 1 (text/plain, inline)]

Hi Guix,                                                                                 
                                                                                         
I ran into this issue when building mariadb 10.1.38. I've attached the                   
last 300 lines of the log. Thanks

[mariadb-check.log (text/x-log, attachment)]

Message #8 received at 39310 <at> debbugs.gnu.org (full text, mbox):

From: Marius Bakke <mbakke <at> fastmail.com>
To: Josh <randomenduser <at> fastmail.com>, 39310 <at> debbugs.gnu.org
Subject: Re: bug#39310: MariaDB reproducibility issue
Date: Mon, 27 Jan 2020 20:21:33 +0100

[Message part 1 (text/plain, inline)]

Josh <randomenduser <at> fastmail.com> writes:

> Hi Guix,                                                                                 
>                                                                                          
> I ran into this issue when building mariadb 10.1.38. I've attached the                   
> last 300 lines of the log. Thanks

I can reproduce this failure by checking out Guix 1.0.1 in a "time 
machine" and trying to build MariaDB.  The problem is that the failing test
expects the current time to be earlier than 2020-01-21 15:32:22.

This was properly fixed in 10.1.39[0], at least until the year 2038.

Unfortunately there is little we can do about it now.  If you are
hitting this problem while trying to install Guix 1.0.1, I recommend to
either:

1) enable binary substitutes
2) set the system clock to some time last year while building MariaDB
3) install a minimal configuration that does not pull in MariaDB, and
reconfigure with the "full" configuration once you have 'guix pull'd.

Will that work for you?

Thanks for the report, and sorry for the inconvenience!

[0] https://github.com/MariaDB/server/commit/cfe0fe1ad1f7c75102285d445c3ba8167f5b9c44

[signature.asc (application/pgp-signature, inline)]

Message #11 received at 39310 <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: Marius Bakke <mbakke <at> fastmail.com>
Cc: Josh <randomenduser <at> fastmail.com>, 39310 <at> debbugs.gnu.org
Subject: Re: bug#39310: MariaDB reproducibility issue
Date: Sun, 24 Jan 2021 17:12:22 +0100

Hi!

Marius Bakke <mbakke <at> fastmail.com> skribis:

> Josh <randomenduser <at> fastmail.com> writes:
>
>> Hi Guix,                                                                                 
>>                                                                                          
>> I ran into this issue when building mariadb 10.1.38. I've attached the                   
>> last 300 lines of the log. Thanks
>
> I can reproduce this failure by checking out Guix 1.0.1 in a "time 
> machine" and trying to build MariaDB.  The problem is that the failing test
> expects the current time to be earlier than 2020-01-21 15:32:22.

I was trying to run:

  guix time-machine --commit=0791437 -- build mariadb

where commit 0791437f972caa7e48de91ad5cb150a614f617c2 is from Jan. 2019,
and stumbled upon the test failure that Josh reported.

Following your advice on IRC, Marius, I built that derivation,
/gnu/store/p2d7i5258vi0rd9ydbpr9c1vb3sxcz6h-mariadb-10.1.37.drv, on a
machine whose clocked I had switched back to 2018… and it worked!

(I used one of the berlin build machines, so now there are substitutes
for this particular derivation.)

Thanks!

Ludo’.

Message #16 received at 39310-done <at> debbugs.gnu.org (full text, mbox):

From: Christopher Baines <mail <at> cbaines.net>
To: 39310-done <at> debbugs.gnu.org
Subject: Re: bug#39310: MariaDB reproducibility issue
Date: Wed, 01 Nov 2023 09:53:42 +0000

[Message part 1 (text/plain, inline)]

Ludovic Courtès <ludo <at> gnu.org> writes:

> Hi!
>
> Marius Bakke <mbakke <at> fastmail.com> skribis:
>
>> Josh <randomenduser <at> fastmail.com> writes:
>>
>>> Hi Guix,
>>>
>>> I ran into this issue when building mariadb 10.1.38. I've attached the
>>> last 300 lines of the log. Thanks
>>
>> I can reproduce this failure by checking out Guix 1.0.1 in a "time
>> machine" and trying to build MariaDB.  The problem is that the failing test
>> expects the current time to be earlier than 2020-01-21 15:32:22.
>
> I was trying to run:
>
>   guix time-machine --commit=0791437 -- build mariadb
>
> where commit 0791437f972caa7e48de91ad5cb150a614f617c2 is from Jan. 2019,
> and stumbled upon the test failure that Josh reported.
>
> Following your advice on IRC, Marius, I built that derivation,
> /gnu/store/p2d7i5258vi0rd9ydbpr9c1vb3sxcz6h-mariadb-10.1.37.drv, on a
> machine whose clocked I had switched back to 2018… and it worked!
>
> (I used one of the berlin build machines, so now there are substitutes
> for this particular derivation.)

This seems like this issue is addressed at least, and guix challenge
says mariadb is reproducible, so I'm going to mark this as done:

→ guix challenge --diff=simple mariadb

1 store items were analyzed:
  - 1 (100.0%) were identical
  - 0 (0.0%) differed
  - 0 (0.0%) were inconclusive

[signature.asc (application/pgp-signature, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.