From: "Ludovic Courtès" <ludo@gnu.org>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: 36684@debbugs.gnu.org
Subject: bug#36684: "View build log" - but it's empty (at first)!
Date: Wed, 17 Jul 2019 21:57:29 +0200 [thread overview]
Message-ID: <877e8ga0ye.fsf@gnu.org> (raw)
In-Reply-To: <877e8i1nnm.fsf@gmail.com> (Chris Marusich's message of "Mon, 15 Jul 2019 23:47:25 -0700")
Hi Chris,
Chris Marusich <cmmarusich@gmail.com> skribis:
> Whoops, I got my wires crossed. Those build logs are for
> evolution-data-server, not ant-bootstrap. However, the same problem
> holds for evolution-data-server - I built it, it failed, it said I could
> find the logs at
> /var/log/guix/drvs/7f/n896phqyv9r636yhjipa9k4qm7g9ni-evolution-data-server-3.30.2.drv.bz2,
> it was empty at first, but then it became full.
I guess there’s a small window during which the bzip file handle hasn’t
been closed, and so you could see an empty file. However, that window
should be extremely small: as soon as the client disconnects or the
build terminates, the daemon closes the log.
> In fact, it is only partially full, since the file ends unexpectedly:
>
> $ bzcat /var/log/guix/drvs/7f/n896phqyv9r636yhjipa9k4qm7g9ni-evolution-data-server-3.30.2.drv.bz2 > /dev/null
>
> bzcat: Compressed file ends unexpectedly;
> perhaps it is corrupted? *Possible* reason follows.
> bzcat: Success
> Input file = /var/log/guix/drvs/7f/n896phqyv9r636yhjipa9k4qm7g9ni-evolution-data-server-3.30.2.drv.bz2, output file = (stdout)
>
> It is possible that the compressed file(s) have become corrupted.
> You can use the -tvv option to test integrity of such files.
>
> You can use the `bzip2recover' program to attempt to recover
> data from undamaged sections of corrupted files.
So this particular log file remained truncated?
I’ve never experienced it. Is there a scenario that allows you to
reproduce it?
Thanks,
Ludo’.
next prev parent reply other threads:[~2019-07-17 19:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-16 6:41 bug#36684: "View build log" - but it's empty (at first)! Chris Marusich
2019-07-16 6:47 ` Chris Marusich
2019-07-17 19:57 ` Ludovic Courtès [this message]
2019-11-16 23:32 ` Chris Marusich
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=877e8ga0ye.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=36684@debbugs.gnu.org \
--cc=cmmarusich@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).