unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: ng0 <ng0@infotropique.org>
Cc: 28087@debbugs.gnu.org
Subject: bug#28087: "guix build: error: no build log for gnu-store-pathto.drv" with previously offloaded successful build
Date: Fri, 08 Sep 2017 10:32:56 +0200	[thread overview]
Message-ID: <87mv65k2tj.fsf@gnu.org> (raw)
In-Reply-To: <20170814175108.j4gm3x5vjtglr2xx@abyayala> (ng0@infotropique.org's message of "Mon, 14 Aug 2017 17:51:08 +0000")

Hi ng0,

Sorry for the late reply.

ng0 <ng0@infotropique.org> skribis:

> I offload my builds by default.
> The build in question succeeded. Now I wanted to read the log of the successful build to check
> the configure options.
> I thought I'd just do:
>
> guix build --log-file --no-grafts --check --no-build-hook --rounds=2 --verbosity=5 mate-session-manager

Note: don’t use “--log-file” along with “--check”; these are two
different things.

> Verbosity was just added later, and so was --check and --no-grafts and --rounds.
> The only time I did not get was when the build was grafted, which got me a log
> file with the content of the graft locationA -> locationB in it.
>
> Every other try just gives me:
> guix build: error: no build log for '/gnu/store/l5cznxxdnbf803mkjavmg9kajicy7751-mate-session-manager-1.18.1.drv'
>
> Is this a bug or just a mistake of where I put "--log-file"?

Can you still reproduce this?

If so, can you manually check whether the log file you’re looking for is
actually in /var/log/guix/drvs on your machine?

TIA,
Ludo’.

  reply	other threads:[~2017-09-08  8:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-14 17:51 bug#28087: "guix build: error: no build log for gnu-store-pathto.drv" with previously offloaded successful build ng0
2017-09-08  8:32 ` Ludovic Courtès [this message]
2018-01-08 14:36   ` Ludovic Courtès
2020-09-14 16:14     ` zimoun

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=87mv65k2tj.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=28087@debbugs.gnu.org \
    --cc=ng0@infotropique.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).