mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Cliff White <cliffw@osdl.org>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>, smurf@osdl.org
Subject: Re: test suite?
Date: Wed, 22 Jan 2003 08:28:13 -0800	[thread overview]
Message-ID: <200301221628.h0MGSDl29588@mail.osdl.org> (raw)
In-Reply-To: Message from "Robert P. J. Day" <rpjday@mindspring.com>  of "Wed, 22 Jan 2003 08:44:05 EST." <Pine.LNX.4.44.0301220840530.2622-100000@dell>

> 
>   i've noticed references to "test suites" for kernels, but
> is there any one-step convenient way to select every possible
> option for test-compiling a new kernel, just to see if it builds?
> perhaps an "everything" option?
> 
>   and, related to that, should such a kernel theoretically
> work?  as in, are there any options that would be mutually
> exclusive that would cause such a build to fail?
> 
> still thinking about reorganizing the overall option structure,
> rday

The OSDL's patch lifecycle manager (http://www.osdl.org/cgi-bin/plm ) 
does something like this. It does a series of builds include a few that 
select most every option. So you could toss the patch into PLM and look at
the results of those test compiles.  In particular, the 'Desktop' config
turns on a ton of stuff ( and almost always fails ;)
We also do a 'regress' build, where we do 'make defconfig' and 
'make allmodconfig' and count the errors.

I don't think we have any more detailed docs, but the test report does include
the .config files we run.
cliffw

> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 



  parent reply	other threads:[~2003-01-22 16:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-22 13:44 Robert P. J. Day
2003-01-22 15:59 ` Sam Ravnborg
2003-01-22 16:20   ` Robert P. J. Day
2003-01-22 16:28 ` Cliff White [this message]
2003-01-22 17:34 ` Adrian Bunk
     [not found] <1043426077.1620.10.camel@localhost.localdomain>
2003-01-24 17:18 ` Randy.Dunlap
2003-01-25  1:53   ` Randy.Dunlap
2003-01-25 20:22     ` Hugh Dickins
2003-01-25 22:24       ` Randy.Dunlap
2003-01-25 23:23       ` William Lee Irwin III
2003-01-25 23:38         ` Martin J. Bligh

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=200301221628.h0MGSDl29588@mail.osdl.org \
    --to=cliffw@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rpjday@mindspring.com \
    --cc=smurf@osdl.org \
    /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

all inboxes | Powered by JetHome®