public inbox for gentoo-soc@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Antanas Uršulis" <antanas.ursulis@gmail.com>
To: gentoo-soc@lists.gentoo.org
Subject: [gentoo-soc] Log collection and analysis: report for 6.17-24
Date: Tue, 25 Jun 2013 17:00:24 +0100	[thread overview]
Message-ID: <CALQr0eoR6DuFt3Jm+W3BJx1zdLbk1fs_ocX81KiyGUVAzP1X5g@mail.gmail.com> (raw)

Hello everyone,

I'm working on the "Log collection and analysis for the tinderbox"
project. It aims to create a replacement for the current solution,
which, in short, collects build logs (and other info) from the
tinderbox, finds out which of these logs come from builds that failed,
and displays them, along with lines indicating errors/warnings/etc. to
the tinderbox runner, so that the issue can be investigated, bugs
filed, and so on.

There is a wiki page [1] which currently contains a copy of the
original proposal and code will be placed in [2].

---------

I did not anticipate that I would need to run so many errands after
exams in university, so the progress has been a bit slow.
Nevertheless, here is what I've done over the past week or more:
* set up a Gentoo VM that I will use later when I develop Portage
integration (in order to keep my main system functional)
* started building a skeleton of the server-side components: an HTTP
based server

Being relatively on schedule, my plans for the next few days are:
* finish the server so that it treats requests as file uploads, and
stores the files in directories based on the client's hostname
* write a simple file submission client

Good luck to everyone,
Antanas

[1] https://wiki.gentoo.org/wiki/Tinderbox_log_collection_and_analysis
[2] https://git.overlays.gentoo.org/gitweb/?p=proj/log-analysis.git;a=summary


                 reply	other threads:[~2013-06-25 16:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CALQr0eoR6DuFt3Jm+W3BJx1zdLbk1fs_ocX81KiyGUVAzP1X5g@mail.gmail.com \
    --to=antanas.ursulis@gmail.com \
    --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