From: ludo@gnu.org (Ludovic Courtès)
To: Nikita Karetnikov <nikita@karetnikov.org>
Cc: guix-devel@gnu.org
Subject: Re: core-updates: FAIL: tests/builders.scm; tests/packages.scm; tests/store.scm
Date: Tue, 04 Mar 2014 18:12:33 +0100 [thread overview]
Message-ID: <87ob1lq45a.fsf@gnu.org> (raw)
In-Reply-To: <87a9d6dzd1.fsf@karetnikov.org> (Nikita Karetnikov's message of "Tue, 04 Mar 2014 14:36:42 +0400")
Could you send test-suite.log and tests/{builders,packages,store}.log?
(Note: tests/foo.log is different from foo.log!)
Thanks,
Ludo’.
next prev parent reply other threads:[~2014-03-04 17:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-04 10:36 core-updates: FAIL: tests/builders.scm; tests/packages.scm; tests/store.scm Nikita Karetnikov
2014-03-04 17:12 ` Ludovic Courtès [this message]
2014-03-05 22:12 ` Nikita Karetnikov
2014-03-10 22:03 ` 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=87ob1lq45a.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=nikita@karetnikov.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).