From: ludo@gnu.org (Ludovic Courtès)
To: Drashne <drashne@protonmail.com>
Cc: "28610@debbugs.gnu.org" <28610@debbugs.gnu.org>
Subject: bug#28610: tcsh 6.20.00 testsuite: 68 failed
Date: Sun, 01 Oct 2017 23:58:02 +0200 [thread overview]
Message-ID: <87vajypm39.fsf@gnu.org> (raw)
In-Reply-To: <qf4BXZQBPRXNft3iLkodLCY9-beCgHy5rDKAH2KAsgCLyvCXp685YSVwL4LLdi6yoaM7EtNqKAaRbwtppStmTJBOvDK-MICv0FUagz71HXw=@protonmail.com> (drashne@protonmail.com's message of "Fri, 29 Sep 2017 13:22:40 -0400")
Hello Drashne,
Drashne <drashne@protonmail.com> skribis:
> I had set up my guix-daemon startup script to start it as "/usr/bin/nice /usr/bin/ionice -c3 /root/.guix-profile/bin/guix-daemon --build-users-group=guixbuild --no-substitutes" but when troubleshooting this I blindly looked right through the "/usr/bin/nice /usr/bin/ionice -c3" part and just focused on the guix-daemon and its arguments.
>
> After noticing this, I tried running guix-daemon without nicing or ionicing it, and rerunning "guix package -i glibc-locales" which now successfully built and tested tcsh, and is currently continuing to build other packages necessary for the installation of glibc-locales.
Great, thanks for testing!
It’s one of these rare cases where details about the host system leak
into the build environment, and picky test suites immediately notice.
Ludo’.
prev parent reply other threads:[~2017-10-01 21:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-26 14:18 bug#28610: tcsh 6.20.00 testsuite: 68 failed Drashne
2017-09-28 14:17 ` Ludovic Courtès
2017-09-29 2:27 ` Drashne
2017-09-29 7:55 ` Ludovic Courtès
2017-09-29 17:22 ` Drashne
2017-10-01 21:58 ` Ludovic Courtès [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vajypm39.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=28610@debbugs.gnu.org \
--cc=drashne@protonmail.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.