From: Mark H Weaver <mhw@netris.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 30024-done@debbugs.gnu.org
Subject: bug#30024: [PATCH] core-updates: librsvg: Disable more failing tests
Date: Mon, 08 Jan 2018 11:50:33 -0500 [thread overview]
Message-ID: <87incce1ly.fsf@netris.org> (raw)
In-Reply-To: <87k1wsfng7.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Mon, 08 Jan 2018 15:13:28 +0100")
Hi Ludovic,
ludo@gnu.org (Ludovic Courtès) writes:
> Mark H Weaver <mhw@netris.org> skribis:
>
>> [*] GNU tar's handling of sparse files is broken on btrfs filesystems
>> and thus fails its test suite on my system, and the test suite of
>> guile-2.2.3 hung up (no output or CPU usage for 30 minutes with a
>> defunct guile process) on my x86_64 GuixSD system.
>
> Many file system related tests fail on Btrfs. :-/
I've resumed an old discussion about the GNU Tar issue here:
https://lists.gnu.org/archive/html/bug-tar/2018-01/msg00002.html
The good news is that Paul Eggert, a GNU Tar maintainer, is open to
letting me fix this bug properly.
> As for the Guile failure, it’s weird. Could you gather more info if it
> happens again?
I just filed a report with the information I gathered, here:
https://bugs.gnu.org/30027
I neglected to mention it, but I also saved the failed build directory,
and the complete build log.
Mark
prev parent reply other threads:[~2018-01-08 16:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-08 7:08 bug#30024: [PATCH] core-updates: librsvg: Disable more failing tests Mark H Weaver
2018-01-08 14:13 ` Ludovic Courtès
2018-01-08 16:50 ` Mark H Weaver [this message]
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=87incce1ly.fsf@netris.org \
--to=mhw@netris.org \
--cc=30024-done@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).