From: ludo@gnu.org (Ludovic Courtès)
To: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
Cc: guix-devel@gnu.org
Subject: Re: Getting ‘core-updates’ merged
Date: Fri, 23 Nov 2018 14:52:42 +0100 [thread overview]
Message-ID: <87h8g76gut.fsf@gnu.org> (raw)
In-Reply-To: <875zwpcuu0.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Thu, 22 Nov 2018 10:41:59 +0100")
ludo@gnu.org (Ludovic Courtès) skribis:
> There are still failures out there!
>
> https://hydra.gnu.org/eval/110331?full=1#tabs-still-fail
>
> The above list is slightly outdated so I’m restarting an evaluation on
> hydra.gnu.org.
>
> A prominent issue is LibreOffice:
>
> https://lists.gnu.org/archive/html/guix-devel/2018-11/msg00332.html
Another one is Rust 1.22.1, which is a dependency of IceCat:
https://berlin.guixsd.org/log/7i2nmyj2nv0942mi01lz89c4kq22j5rv-rust-1.22.1
Excerpt:
--8<---------------cut here---------------start------------->8---
failures:
---- [run-make] run-make/issue-26092 stdout ----
error: make failed
status: exit code: 2
command: "make"
stdout:
------------------------------------------
LD_LIBRARY_PATH="/tmp/guix-build-rust-1.22.1.drv-0/rustc-1.22.1-src/build/x86_64-unknown-linux-gnu/test/run-make/issue-26092.stage2-x86_64-unknown-linux-gnu:/tmp/guix-build-rust-1.22.1.drv-0/rustc-1.22.1-src/build/x86_64-unknown-linux-gnu/stage2/lib:/tmp/guix-build-rust-1.22.1.drv-0/rustc-1.22.1-src/build/x86_64-unknown-linux-gnu/stage0-tools/x86_64-unknown-linux-gnu/release/deps:/tmp/guix-build-rust-1.22.1.drv-0/rustc-1.22.1-src/build/x86_64-unknown-linux-gnu/stage0-sysroot/lib/rustlib/x86_64-unknown-linux-gnu/lib:" '/tmp/guix-build-rust-1.22.1.drv-0/rustc-1.22.1-src/build/x86_64-unknown-linux-gnu/stage2/bin/rustc' --out-dir /tmp/guix-build-rust-1.22.1.drv-0/rustc-1.22.1-src/build/x86_64-unknown-linux-gnu/test/run-make/issue-26092.stage2-x86_64-unknown-linux-gnu -L /tmp/guix-build-rust-1.22.1.drv-0/rustc-1.22.1-src/build/x86_64-unknown-linux-gnu/test/run-make/issue-26092.stage2-x86_64-unknown-linux-gnu -o "" blank.rs 2>&1 | \
grep -i 'No such file or directory'
------------------------------------------
stderr:
------------------------------------------
make: *** [Makefile:4: all] Error 1
------------------------------------------
thread '[run-make] run-make/issue-26092' panicked at 'explicit panic', src/tools/compiletest/src/runtest.rs:2433:8
note: Run with `RUST_BACKTRACE=1` for a backtrace.
--8<---------------cut here---------------end--------------->8---
Danny, does that ring a bell?
Thanks,
Ludo’.
next prev parent reply other threads:[~2018-11-23 13:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-14 8:28 New release soon? swedebugia
2018-11-14 11:44 ` Ricardo Wurmus
2018-11-14 17:57 ` Marius Bakke
2018-11-16 18:10 ` Ludovic Courtès
2018-11-16 21:15 ` Ricardo Wurmus
2018-11-16 21:20 ` Ludovic Courtès
2018-11-16 22:03 ` Björn Höfling
2018-11-17 0:58 ` Gábor Boskovits
2018-11-17 14:14 ` Getting ‘core-updates’ merged Ludovic Courtès
2018-11-22 9:41 ` Ludovic Courtès
2018-11-22 19:54 ` Björn Höfling
2018-11-23 13:52 ` Ludovic Courtès [this message]
2018-11-23 21:44 ` Julien Lepiller
2018-11-24 9:19 ` Danny Milosavljevic
2018-11-25 15:54 ` Ludovic Courtès
2018-11-26 17:59 ` Danny Milosavljevic
2018-11-26 18:18 ` Danny Milosavljevic
2018-11-28 10:46 ` Ludovic Courtès
2018-11-26 17:54 ` Björn Höfling
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=87h8g76gut.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=bjoern.hoefling@bjoernhoefling.de \
--cc=guix-devel@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).