unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: Leo Barge <puppetistas@gmail.com>
Cc: 37867@debbugs.gnu.org
Subject: bug#37867: bug on x86_64-linux AMD box
Date: Wed, 23 Oct 2019 13:53:36 +0200	[thread overview]
Message-ID: <20191023115336.v4dxrg7b5jyc6iwc@pelzflorian.localdomain> (raw)
In-Reply-To: <6c0d8b35-08f8-882f-57c1-73110bf5beb0@gmail.com>

On Tue, Oct 22, 2019 at 05:48:09AM -0700, Leo Barge wrote:
> 
> I found a bug.
> […]
> At hour 0437 on date 22 OCT 2019, a ten-hour long guix pull that I ran ended
> with the following message, in a summary of operation:
> 
> 
> Full log written to
> /tmp/guix-build-glib-2.60.6.drv-0/build/meson-logs/testlog.txt
> @ build-log 3297 65
> command "meson" "test" "--no-suite" "flaky" failed with status 1
> […]

Thank you for reporting.  This is strange.  Your guix version is
recent.  Glib builds fine for me though (on a Macbook using
“./pre-inst-env guix build glib --check --no-grafts”).



> I immediately went looking for the full log but failed to find it at the
> reported location in /tmp.

You would need to add -K to the guix pull command (“guix pull -K”) to
get the full log because the log is generated not by Guix itself and
Guix deletes build directories by default.

Regards,
Florian

  reply	other threads:[~2019-10-23 11:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-22 12:48 bug#37867: bug on x86_64-linux AMD box Leo Barge
2019-10-23 11:53 ` pelzflorian (Florian Pelz) [this message]
2019-10-24  5:03 ` ison
2020-10-13  4:10 ` Maxim Cournoyer

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=20191023115336.v4dxrg7b5jyc6iwc@pelzflorian.localdomain \
    --to=pelzflorian@pelzflorian.de \
    --cc=37867@debbugs.gnu.org \
    --cc=puppetistas@gmail.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 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).