From: Jesper Juhl <jesper.juhl@gmail.com>
To: lkml@dodo.com.au
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.13-rc3 test: finding compile errors with make randconfig
Date: Sun, 24 Jul 2005 15:01:22 +0200 [thread overview]
Message-ID: <9a8748490507240601ec7a940@mail.gmail.com> (raw)
In-Reply-To: <f8b6e1h2t4tlto7ia8gs8aanpib68mhit6@4ax.com>
On 7/24/05, Grant Coady <lkml@dodo.com.au> wrote:
> Greetings,
>
> Few days ago I compiled 241 random configurations of 2.6.13-rc3, today
> I finally got around to parsing the results, top 40, sorted by name.
> Percentage is error_builds / total_builds.
>
> build script similar to:
> count=0
> while [ $((++count)) -le $limit ]; do
> trial=$(printf %003d $count)
> make randconfig
> cp .config "$store/$trial-config"
> make clean
> make -j2 2> "$store/$trial-error"
> done
>
> Curious whether this is worth doing, I'm about to start a run for 2.6.12.3,
> any interesting errors I can find the particular config + error to recover
> context. Deliberately simplistic for traceability at the moment, truncated
> error length for this post.
>
If you could put the data online somewhere I'd be interrested in
taking a look at it.
An easy way to look at the build log and grab the matching .config for
any given run would be great.
--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
next prev parent reply other threads:[~2005-07-24 13:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-24 6:28 2.6.13-rc3 test: finding compile errors with make randconfig Grant Coady
2005-07-24 9:13 ` Adrian Bunk
2005-07-24 19:42 ` Grant Coady
2005-07-24 20:14 ` Jesper Juhl
2005-07-24 20:39 ` Adrian Bunk
2005-07-24 21:13 ` Grant Coady
2005-07-24 21:27 ` Adrian Bunk
2005-07-24 21:49 ` Grant Coady
2005-07-26 1:26 ` Grant Coady
2005-07-26 9:55 ` Adrian Bunk
2005-07-24 13:01 ` Jesper Juhl [this message]
2005-07-24 19:23 ` Grant Coady
2005-07-24 19:30 ` Jesper Juhl
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=9a8748490507240601ec7a940@mail.gmail.com \
--to=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@dodo.com.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.