Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] autobuild: group similar failures
Date: Tue, 15 May 2012 08:32:31 +0200	[thread overview]
Message-ID: <4FB1F87F.5060505@mind.be> (raw)
In-Reply-To: <201205142322.44867.yann.morin.1998@free.fr>

On 05/14/12 23:22, Yann E. MORIN wrote:
> Although successful builds are nice, the interesting logs are those that
> relate to build failures. Having the ability to sort and categorise those
> failed logs would hopefully help in solving the most common build failures.

  +1

> For example, in the recent past, there were two related alsa-libs build
> failures on PowerPC:
>    http://autobuild.buildroot.net/results/a8471598a379e5dbecef539479b968947474ef22/
>    http://autobuild.buildroot.net/results/05b306ee2fa909420e4bc1f9faa7a35d17d786a7/
>
> I did not look in details, but it may well be that there are other similar
> build failures of alsa-libs on PowerPC. Solving the error in one of those
> builds would also solve the other(s).
>
> So, we need a heuristic to detect how similar two failed build logs are, and
> eventually group those failures together. Below is such simple heuristic:
>
>   1- extract the last 100 lines-or-so from two build logs (already done)
>   2- sort each extract
>   3- diffstat the sorted extracts
>   4- the lower the number of different lines, the higher the similarity

  A much simpler heuristic would be to put failures of the same package together.
It's very likely that they're the same.  The diffstat has the disadvantage that
it can still be pretty different if the compiler path is different (for packages
that don't do a quiet make like alsa-libs does).

  Regards,
  Arnout

-- 
Arnout Vandecappelle                               arnout at mind be
Senior Embedded Software Architect                 +32-16-286540
Essensium/Mind                                     http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium                BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

      reply	other threads:[~2012-05-15  6:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-14 21:22 [Buildroot] autobuild: group similar failures Yann E. MORIN
2012-05-15  6:32 ` Arnout Vandecappelle [this message]

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=4FB1F87F.5060505@mind.be \
    --to=arnout@mind.be \
    --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