Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 29 Dec 2010 02:46:26 -0800
From:      Garrett Cooper <gcooper@FreeBSD.org>
To:        Alexander Leidinger <Alexander@leidinger.net>
Cc:        mdf@freebsd.org, Robert Watson <rwatson@freebsd.org>, Erik Cederstrand <erik@cederstrand.dk>, freebsd-arch@freebsd.org
Subject:   Re: Schedule for releases
Message-ID:  <AANLkTike91a4sk0xeR0kz=zdVRggZVoL0FRcxcDKzGCr@mail.gmail.com>
In-Reply-To: <20101229000412.000049ee@unknown>
References:  <AANLkTi=_mHDz3LZ1SAuCsz6kmvqCdZBx3Q5ZTyQQO1%2BP@mail.gmail.com> <201012211500.16131.jhb@freebsd.org> <alpine.BSF.2.00.1012212215320.36028@fledge.watson.org> <DB4D8AC7-25D6-4901-BBF9-77BEB956840B@cederstrand.dk> <20101229000412.000049ee@unknown>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Dec 28, 2010 at 3:04 PM, Alexander Leidinger
<Alexander@leidinger.net> wrote:
> On Wed, 22 Dec 2010 08:21:56 +0100 Erik Cederstrand
> <erik@cederstrand.dk> wrote:
>
>> Den 21/12/2010 kl. 23.28 skrev Robert Watson:
>>
>> >
>> > Looking at 7.x, I'm struck by how much it has slowed down. =A0There's
>> > a significant user community, but not a significant developer
>> > community.
>>
>> Which pretty much sums up a dilemma in the development of FreeBSD, I
>> think. Developers want users to try out their new shiny stuff, but
>> users don't want to spend time upgrading.
>>
>> I think one of many things that would be great to do is to improve
>> the usability and coverage of the regression tests. This would take
>> at least some of the burden off developers who want to MFC their
>> work. We already have the tinderboxes, Coverity and Clang Static
>> Analyzer, but apart from pho's stress tests we don't have any
>> automated runtime testing (as far as I know).
>
> Your benchmark suite can not be used for something like this? With the
> regression tests as the benchmarks? BTW: real benchmarks are also some
> kind of regression tests,

    Sometimes, but we are lacking in the functional tests department
in areas and that's something in coverage that needs to be filled out.
Stress tests/benchmarks can exercise a lot or a little code and can
create unnecessary results variance depending on how they're written,
as I'm sure everyone posting on the list to this topic is aware.
Thanks,
-Garrett



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTike91a4sk0xeR0kz=zdVRggZVoL0FRcxcDKzGCr>