public inbox for gentoo-soc@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-soc@lists.gentoo.org
Subject: Re: [gentoo-soc] GSoC 2013: Log collector
Date: Sun, 28 Apr 2013 22:08:34 -0400	[thread overview]
Message-ID: <CAGfcS_m3uqFMU_msf0156f9pvg0zhgVqCvgnnasamy_P9uw==Q@mail.gmail.com> (raw)
In-Reply-To: <CALQr0erRWGqY2iwPENuRiZ0_TAX7ViP17-vdE9oQtxn5x=50BA@mail.gmail.com>

On Sun, Apr 28, 2013 at 9:48 PM, Antanas Uršulis
<antanas.ursulis@gmail.com> wrote:
> --- portage would implement a client which can submit logs to the
> collector, possibly providing information why the package failed

While this isn't exactly necessary for tinderbox purposes, having
portage be able to dump consolidated logs (tarball, etc) might be
really useful for bug reporting purposes in general.  Right now we ask
users to submit a laundry list of useful data that requires several
commands to consolidate.  If a simple command dumped all the useful
info relevant to the last failed build into a tarball suitable for
attachment to a bug, that might be very useful all-around.

This could also be leveraged for a bug reporter as well.  The tarball
might include an xml or text that contains relevant metadata for the
failed build suitable for parsing by the log server.

Just a random thought - not my project...

Rich


  reply	other threads:[~2013-04-29  2:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-22  1:19 [gentoo-soc] GSoC 2013: Log collector Antanas Uršulis
2013-04-22 15:55 ` Diego Elio Pettenò
2013-04-29  1:48   ` Antanas Uršulis
2013-04-29  2:08     ` Rich Freeman [this message]
2013-05-02  4:22       ` Antanas Uršulis
2013-04-29  3:03     ` Brian Dolbec
2013-04-29  7:06       ` Diego Elio Pettenò
2013-04-29  7:28     ` Diego Elio Pettenò
2013-04-30 10:13       ` Antanas Uršulis
2013-05-02  4:17         ` Antanas Uršulis

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='CAGfcS_m3uqFMU_msf0156f9pvg0zhgVqCvgnnasamy_P9uw==Q@mail.gmail.com' \
    --to=rich0@gentoo.org \
    --cc=gentoo-soc@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