Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] autobuild statistics graph
Date: Wed, 28 Aug 2013 09:10:36 +0200	[thread overview]
Message-ID: <20130828091036.1a91b786@skate> (raw)
In-Reply-To: <CAAXf6LW8axKFZpiQFjmqWcFXTEqaHoD3uX=hk5ZSQbmz_7BabA@mail.gmail.com>

Dear Thomas De Schampheleire,

On Wed, 28 Aug 2013 08:46:50 +0200, Thomas De Schampheleire wrote:

> The autobuild statistics shows a graph with the number of
> failed/successful/total builds at:
> http://autobuild.buildroot.org/stats.php
> 
> However, given that the total number of builds executed each day is
> varying, it is difficult to visually draw conclusions from the graph.

Yeah, now you realize that I was sleeping during all those statistics
courses at the university :)

> I would like to propose adding another graph (or replacing the current
> one) that plots the percentages of successful/failed builds. Hence,
> the reference will always be 100%, and a 'success' line going up means
> improvement.
> In fact, in this case it makes little sense to plot both the success
> and failure lines, so we can choose either one.
> 
> What do you think?

Sounds sane. How would you compute what the reference is? Look at the
build results of the last 30 days (i.e the ones that appear on the
plot) ?

> Is this difficult to realize?
> If you give me some source code of how the graph is generated, I'm
> willing to look into this.

The code that generates the graph is available at
http://git.buildroot.net/buildroot-test/tree/web/graph.php. Warning:
ugly PHP code inside!

Thanks!

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2013-08-28  7:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-28  6:46 [Buildroot] autobuild statistics graph Thomas De Schampheleire
2013-08-28  7:10 ` Thomas Petazzoni [this message]
2013-08-28  7:42   ` Thomas De Schampheleire
2013-08-28  7:48     ` Thomas Petazzoni
2013-08-28  8:02       ` Thomas De Schampheleire
2013-08-29  7:40         ` Thomas De Schampheleire
2013-08-29  8:15           ` Thomas Petazzoni
2013-08-29  8:40             ` Thomas De Schampheleire
2013-08-29 15:59               ` Arnout Vandecappelle
2013-08-30  7:47                 ` Thomas Petazzoni
2013-09-08 13:57           ` Thomas Petazzoni
2013-09-08 14:27             ` Thomas De Schampheleire

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=20130828091036.1a91b786@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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