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: Thu, 29 Aug 2013 10:15:13 +0200	[thread overview]
Message-ID: <20130829101513.60e3eb48@skate> (raw)
In-Reply-To: <CAAXf6LVPQVzQpfCdeVrm2yNzEad8j2GS9pnna7YiKVnhTb=MQg@mail.gmail.com>

Dear Thomas De Schampheleire,

On Thu, 29 Aug 2013 09:40:41 +0200, Thomas De Schampheleire wrote:

> > That looks good, yes, thanks for testing so quickly.
> > One consideration: although the table doesn't have to be larger, the
> > 30 days for the graph is somewhat limited. If we want to see a trend,
> > then I think a few months can be more interesting. So what about
> > changing the SQL query to, say, 180 days (6 months) ?
> 
> It seems you already made this change, thanks.
> 
> The x axis is now a bit crowded, below untested patch should make it a
> bit more readable, could you check?

Yeah, I did some experiment, but as you say the X axis was crowded, and
I didn't had the time to investigate.

> diff --git a/web/graph.php b/web/graph.php
> index 7ac37d8..5585ee5 100644
> --- a/web/graph.php
> +++ b/web/graph.php
> @@ -50,7 +50,7 @@
> $myPicture->setFontProperties(array("FontName"=>"../externals/pchart/fonts/verda
>  /* Define the boundaries of the graph area */
>  $myPicture->setGraphArea(70,50,650,400);
> 
> -$myPicture->drawScale(array("LabelRotation" => 90));
> +$myPicture->drawScale(array("LabelRotation" => 90, "LabelSkip" => 10));
> 
>  $myPicture->drawLegend(20,20,array("Style"=>LEGEND_NOBORDER,"Mode"=>LEGEND_HORIZONTAL));

I'll definitely try this out, thanks!

Another great thing would be to draw some thin vertical lines at the
dates of the various releases (-rc1, -rc2, final and so on), so we can
see if the rate of failures/success correlate with releases or not.
It'd be fun, but I'm not sure it's really worth the effort because
besides the releases themselves, another major thing causes big
variations in the rate of success/failure: when I had a new toolchain
for a new architecture, or a new configuration type (eg. static
builds). I believe those changes in the configuration of the
autobuilders are causing more variations in the results than the
release cycles themselves.

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-29  8:15 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
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 [this message]
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=20130829101513.60e3eb48@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