From: Ricardo Wurmus <rekado@elephly.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 36747@debbugs.gnu.org
Subject: bug#36747: Official MesCC bootstrap binaries differ from my locally built ones
Date: Thu, 29 Aug 2019 07:46:50 +0200 [thread overview]
Message-ID: <87blw8h6b9.fsf@elephly.net> (raw)
In-Reply-To: <87d0gpdjmi.fsf@gnu.org>
Ludovic Courtès <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
>
> Excerpt:
>
> --8<---------------cut here---------------start------------->8---
> make[1]: Entering directory '/tmp/guix-build-bison-3.4.1.drv-0/bison-3.4.1'
> make[1]: Entering directory '/tmp/guix-build-bison-3.4.1.drv-0/bison-3.4.1'
> rm -f examples/c/reccalc/scan.stamp examples/c/reccalc/scan.stamp.tmp
> rm -f examples/c/reccalc/scan.stamp examples/c/reccalc/scan.stamp.tmp
> /gnu/store/7fimyv3n4jn7nbyl5f5bzdhnm25qmk3m-bootstrap-binaries-0/bin/mkdir -p examples/c/reccalc
> /gnu/store/7fimyv3n4jn7nbyl5f5bzdhnm25qmk3m-bootstrap-binaries-0/bin/mkdir -p examples/c/reccalc
> touch examples/c/reccalc/scan.stamp.tmp
> touch examples/c/reccalc/scan.stamp.tmp
> : -oexamples/c/reccalc/scan.c --header-file=examples/c/reccalc/scan.h ./examples/c/reccalc/scan.l
> : -oexamples/c/reccalc/scan.c --header-file=examples/c/reccalc/scan.h ./examples/c/reccalc/scan.l
> mv examples/c/reccalc/scan.stamp.tmp examples/c/reccalc/scan.stamp
> mv examples/c/reccalc/scan.stamp.tmp examples/c/reccalc/scan.stamp
> make[1]: Leaving directory '/tmp/guix-build-bison-3.4.1.drv-0/bison-3.4.1'
> mv: cannot stat 'examples/c/reccalc/scan.stamp.tmp': No such file or directory
> make[1]: *** [Makefile:6855: examples/c/reccalc/scan.stamp] Error 1
> make[1]: Leaving directory '/tmp/guix-build-bison-3.4.1.drv-0/bison-3.4.1'
> make: *** [Makefile:6847: examples/c/reccalc/scan.h] Error 2
> command "make" "-j" "8" "ARFLAGS=crD" "RANLIB=ranlib" "V=1" failed with status 2
> builder for `/gnu/store/wwysm0mdkbvpyp3n4im5pfwcf2brc23p-bison-3.4.1.drv' failed with exit code 1
> @ build-failed /gnu/store/wwysm0mdkbvpyp3n4im5pfwcf2brc23p-bison-3.4.1.drv - 1 builder for `/gnu/store/wwysm0mdkbvpyp3n4im5pfwcf2brc23p-bison-3.4.1.drv' failed with exit code 1
> --8<---------------cut here---------------end--------------->8---
>
> I’ve addressed it by a hack in c55fae452032aa4b1b63406983e9abdf70adc957.
>
>> The second URL above returns "500 Internal Server Error".
>
> Bah, that’s another thing in Cuirass that we kind of fixed in Git but we
> still need to reconfigure I guess. Ricardo, is that correct?
We use a very slightly modified Cuirass at commit
6cf84a43bb6160e11ede96820a8bc563aa7461ef on berlin.
I confirm that visiting this URL still results in an error:
https://ci.guix.gnu.org/eval/7008
(Looks like the cuirass-web service still writes to the same log file,
so I can’t actually see the message amidst all the build logs…)
--
Ricardo
next prev parent reply other threads:[~2019-08-29 5:48 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-20 22:43 bug#36747: Official MesCC bootstrap binaries differ from my locally built ones Mark H Weaver
2019-07-21 13:34 ` Jan Nieuwenhuizen
2019-07-22 0:56 ` Mark H Weaver
2019-07-22 6:18 ` Jan Nieuwenhuizen
2019-07-22 6:26 ` Jan Nieuwenhuizen
2019-07-22 8:26 ` Jan Nieuwenhuizen
2019-07-22 8:31 ` Mark H Weaver
2019-07-22 17:41 ` Jan Nieuwenhuizen
2019-07-23 5:42 ` Mark H Weaver
2019-07-23 6:28 ` Jan Nieuwenhuizen
2019-08-12 0:21 ` Mark H Weaver
2019-08-12 4:11 ` Mark H Weaver
2019-07-23 10:03 ` Ludovic Courtès
2019-08-12 7:08 ` Mark H Weaver
2019-08-12 9:01 ` Jan Nieuwenhuizen
2019-08-13 6:42 ` Mark H Weaver
2019-08-13 10:17 ` Jan Nieuwenhuizen
2019-08-14 15:03 ` Marius Bakke
2019-08-14 17:29 ` Marius Bakke
2019-08-14 18:35 ` Mark H Weaver
2019-08-14 18:43 ` Mark H Weaver
2019-08-14 19:56 ` Marius Bakke
2019-08-14 20:43 ` Mark H Weaver
2019-08-15 19:44 ` Mark H Weaver
2019-08-15 21:19 ` Marius Bakke
2019-08-15 23:16 ` Mark H Weaver
2019-08-15 20:56 ` Mark H Weaver
2019-08-16 7:42 ` Mark H Weaver
2019-08-17 16:49 ` Mark H Weaver
2019-08-16 10:49 ` Ludovic Courtès
2019-08-16 16:59 ` Mark H Weaver
2019-08-17 21:38 ` Ludovic Courtès
2019-08-18 1:17 ` Mark H Weaver
2019-08-18 9:26 ` Ludovic Courtès
2019-08-20 18:40 ` Mark H Weaver
2019-08-21 20:15 ` Mark H Weaver
2019-08-21 21:38 ` Ludovic Courtès
2019-08-21 22:57 ` Mark H Weaver
2019-08-22 10:09 ` Ludovic Courtès
2019-08-24 13:31 ` Ludovic Courtès
2019-08-24 20:34 ` Mark H Weaver
2019-08-26 8:25 ` Ludovic Courtès
2019-08-26 18:36 ` Mark H Weaver
2019-08-27 9:38 ` Ludovic Courtès
2019-08-29 22:28 ` Bengt Richter
2019-08-27 3:58 ` Mark H Weaver
2019-08-27 9:40 ` Ludovic Courtès
2019-08-27 14:27 ` Mark H Weaver
2019-08-27 16:04 ` Ludovic Courtès
2019-08-27 16:46 ` Mark H Weaver
2019-08-28 0:55 ` Mark H Weaver
2019-08-28 22:12 ` Ludovic Courtès
2019-08-29 5:46 ` Ricardo Wurmus [this message]
2019-08-29 6:32 ` Ricardo Wurmus
2019-08-29 19:28 ` Mark H Weaver
2019-08-29 23:23 ` Ludovic Courtès
2019-08-30 19:52 ` Mark H Weaver
2019-08-31 12:44 ` Ludovic Courtès
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=87blw8h6b9.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=36747@debbugs.gnu.org \
--cc=ludo@gnu.org \
/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).