From: Adrian Bunk <bunk@stusta.de>
To: Grant Coady <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 11:13:27 +0200 [thread overview]
Message-ID: <20050724091327.GQ3160@stusta.de> (raw)
In-Reply-To: <f8b6e1h2t4tlto7ia8gs8aanpib68mhit6@4ax.com>
On Sun, Jul 24, 2005 at 04:28:54PM +1000, Grant Coady wrote:
> Greetings,
Hi Grant,
> 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.
>...
it's generally useful, but the target kernel should be the latest -mm
kernel.
And doing the compilations is really the trivial part of the work, the
main work is to analyze what causes the build failures and sending
patches.
> Grant.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2005-07-24 9:13 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 [this message]
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
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=20050724091327.GQ3160@stusta.de \
--to=bunk@stusta.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox