unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: ng0 <ng0@libertad.pw>
Cc: guix-devel@gnu.org
Subject: Re: Idea: "guix log"
Date: Sun, 15 Jan 2017 23:37:52 +0100	[thread overview]
Message-ID: <878tqcdk5b.fsf@gnu.org> (raw)
In-Reply-To: <87bmv8krxe.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me> (ng0@libertad.pw's message of "Sun, 15 Jan 2017 20:07:57 +0000")

Hi!

ng0 <ng0@libertad.pw> skribis:

> Next tool, next idea (the guix log family): A log viewer. Gentoo
> has more than one. The way we currently save logs could be more
> human friendly. It doesn't need a restructuring of the folders
> (yes I know about the switch for logfiles) but we could have
> something similar to https://github.com/gentoo/elogv which
> provides an easy way to read thelogs (nothing more). In addition
> to that, our log reader could extract the log and save it if
> requested to do so.

‘guix-build-log-mode’ in Emacs does that and it’s awesome.  We could
have a log colorizing & navigation tool outside of Emacs, though that’s
probably quite a bit of work.

> Furthermore, a log parser which can tell you how long a build
> took, on average/every time. This is similar to
> https://wiki.gentoo.org/wiki/Genlop
> (https://gitweb.gentoo.org/repo/gentoo.git/tree/app-portage/genlop/genlop-0.30.10-r1.ebuild).
> You don't want to query hydra via emacs or your webbrowser every
> time (at least I don't do this), so a small programm to read out
> the start and finish time of a log would be great.

We could provide a bunch of procedures to extract this info from build
logs.

My 2¢,
Ludo’.

  reply	other threads:[~2017-01-15 22:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-15 20:07 Idea: "guix log" ng0
2017-01-15 22:37 ` Ludovic Courtès [this message]
2017-01-17 14:50   ` Ricardo Wurmus

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=878tqcdk5b.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=ng0@libertad.pw \
    /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).