From mboxrd@z Thu Jan  1 00:00:00 1970
From: Mark H Weaver <mhw@netris.org>
Subject: bug#36747: Official MesCC bootstrap binaries differ from my locally
 built ones
Date: Thu, 29 Aug 2019 15:28:29 -0400
Message-ID: <87lfvblqiv.fsf@netris.org>
References: <875znwcoo9.fsf@netris.org> <87lfwpqpb7.fsf@netris.org>
 <875znt2hlc.fsf@gnu.org> <87zhke97xj.fsf@netris.org>
 <87h86mdaex.fsf@gnu.org> <8736i5a7mb.fsf@netris.org>
 <87mugdbc9r.fsf@gnu.org> <8736i3iyas.fsf@devup.no>
 <87zhkbhd07.fsf@devup.no> <87v9uz4msh.fsf@netris.org>
 <87woffh66h.fsf@devup.no> <874l26y9j0.fsf@gnu.org>
 <87d0guuwt4.fsf@netris.org> <87zhjw1gfm.fsf@gnu.org>
 <87a7bvnts4.fsf@netris.org> <87y2zfq746.fsf@gnu.org>
 <874l22of8l.fsf@netris.org> <87zhjuoarz.fsf@gnu.org>
 <87zhjumu88.fsf@netris.org> <87k1aym7kf.fsf@netris.org>
 <87d0gpdjmi.fsf@gnu.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:470:142:3::10]:55179)
 by lists.gnu.org with esmtp (Exim 4.90_1)
 (envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1i3Q7Q-00072r-G3
 for bug-guix@gnu.org; Thu, 29 Aug 2019 15:30:05 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
 (envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1i3Q7P-0000iS-AI
 for bug-guix@gnu.org; Thu, 29 Aug 2019 15:30:04 -0400
Received: from debbugs.gnu.org ([209.51.188.43]:44111)
 by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
 (Exim 4.71) (envelope-from <Debian-debbugs@debbugs.gnu.org>)
 id 1i3Q7P-0000hW-5j
 for bug-guix@gnu.org; Thu, 29 Aug 2019 15:30:03 -0400
Sender: "Debbugs-submit" <debbugs-submit-bounces@debbugs.gnu.org>
Resent-Message-ID: <handler.36747.B36747.15671069547324@debbugs.gnu.org>
In-Reply-To: <87d0gpdjmi.fsf@gnu.org> ("Ludovic
 \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\=
 \=\?utf-8\?Q\?s\?\= message of "Thu, 29 Aug 2019 00:12:53 +0200")
List-Id: Bug reports for GNU Guix <bug-guix.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/bug-guix>,
 <mailto:bug-guix-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/bug-guix>
List-Post: <mailto:bug-guix@gnu.org>
List-Help: <mailto:bug-guix-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/bug-guix>,
 <mailto:bug-guix-request@gnu.org?subject=subscribe>
Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org
Sender: "bug-Guix" <bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org>
To: Ludovic =?UTF-8?Q?Court=C3=A8s?= <ludo@gnu.org>, Ricardo Wurmus <rekado@elephly.net>
Cc: 36747@debbugs.gnu.org

Hi Ludovic and Ricardo,

Ludovic Court=C3=A8s <ludo@gnu.org> writes:

> Mark H Weaver <mhw@netris.org> skribis:
>
>> I pushed the revised commits to 'core-updates', but something seems to
>> have gone wrong with the new evaluation on Berlin:
>>
>>   https://ci.guix.gnu.org/jobset/core-updates-core-updates
>>   https://ci.guix.gnu.org/eval/7008
>>
>> The first URL above shows a big "X" in the "Success" column for
>> evaluation 7008, which corresponds to the new commits I just pushed, to
>> switch to the new bootstrap tarballs.
>
> We had a Bison build failure:
>
>   https://ci.guix.gnu.org/log/4rvzs59q3smm4kwyfnf7m58a48rql0fs-bison-3.4.1
[...]
> I=E2=80=99ve addressed it by a hack in c55fae452032aa4b1b63406983e9abdf70=
adc957.

Thanks.  The next evaluation got further, but eventually failed.  Again,
there seems no way to get any details on what went wrong from the web
interface:

  https://ci.guix.gnu.org/jobset/core-updates-core-updates
  https://ci.guix.gnu.org/eval/7029

The second URL works this time, but it shows no results: 0 scheduled
builds, 0 succeeded builds, 0 failed builds, and it says "No elements
here."

Can you see what happened?

      Thanks,
        Mark