unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Marius Bakke <mbakke@fastmail.com>
Cc: Josh <randomenduser@fastmail.com>, 39310@debbugs.gnu.org
Subject: bug#39310: MariaDB reproducibility issue
Date: Sun, 24 Jan 2021 17:12:22 +0100	[thread overview]
Message-ID: <87k0s271qx.fsf@gnu.org> (raw)
In-Reply-To: <87pnf4so1u.fsf@devup.no> (Marius Bakke's message of "Mon, 27 Jan 2020 20:21:33 +0100")

Hi!

Marius Bakke <mbakke@fastmail.com> skribis:

> Josh <randomenduser@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’.




  reply	other threads:[~2021-01-24 16:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-27 14:23 bug#39310: MariaDB reproducibility issue Josh
2020-01-27 19:21 ` Marius Bakke
2021-01-24 16:12   ` Ludovic Courtès [this message]
2023-11-01  9:53     ` Christopher Baines

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87k0s271qx.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=39310@debbugs.gnu.org \
    --cc=mbakke@fastmail.com \
    --cc=randomenduser@fastmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).