public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Bryan Gardiner <bog@khumba.net>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Tailing compressed build logs
Date: Mon, 6 Mar 2023 20:35:59 -0800	[thread overview]
Message-ID: <20230306203559.5e1d6e9d@khumba.net> (raw)

Hi folks,

How can I follow Portage's compressed build logs in real time as they
are generated?

I keep build logs and use FEATURES=compress-build-logs so that they
don't get too large.  I can peek at how a build is going with zless on
build.log.gz, which doesn't update (understandably), but I would
really like to be able to watch a log with some "tail -f" equivalent.
I get streaming output with

    tail -c +1 -f build.log.gz | od -t x1

but the following hangs with no output:

    tail -c +1 -f build.log.gz | gunzip

even with a build log that is 72KB compressed (2.4MB uncompressed),
which should be larger than any pipe buffers...  Any idea why gunzip
can't handle this, or what I should I should be doing instead?

Thanks,
Bryan


             reply	other threads:[~2023-03-07  4:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-07  4:35 Bryan Gardiner [this message]
2023-03-07  7:52 ` [gentoo-user] Tailing compressed build logs Mickaël Bucas
2023-03-07  9:01   ` Michael
2023-03-09  7:43     ` Bryan Gardiner
2023-03-08 13:13 ` Andreas Stiasny
2023-03-09  7:46   ` Bryan Gardiner
2023-03-09 14:31     ` Andreas Stiasny
2023-03-09 15:49       ` Peter Humphrey
2023-03-09 15:57         ` Matt Connell
2023-03-09 16:01         ` Dale
2023-03-09 17:07           ` Peter Humphrey
2023-03-10  4:13           ` Bryan Gardiner

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=20230306203559.5e1d6e9d@khumba.net \
    --to=bog@khumba.net \
    --cc=gentoo-user@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox