[OpenAFS] buildbot and packages

[David Boyes]

> -----Original Message-----
> From: Simon Wilkinson [mailto:sxw@your-file-system.com]

> On 17 Sep 2012, at 17:25, David Boyes wrote:
> >>  'make check' on a single machine will never give you useful testing
> results other than to find packaging or "smoke test" errors, which aren't=
 all
> that helpful overall.
>=20
> I agree with you with regards to crowd sourced testing, but I just wanted=
 to
> call out this statement, as I think make check can actually be hugely hel=
pful.
> [snip - bunch of good points about pre-build and commit-time sanity check=
ing]

Good point.  I was considering more of the post-build QA portion of the pro=
blem, but addressing the issue of build failure at the input end of the pro=
blem makes sense as well.=20

> Applying 'make check' as a commit requirement, and improving its coverage
> will hugely help with this problem. I see it more as a developer tool tha=
n a
> general QA solution.

Agreed. I think it'd be even more effective if the build sequence was less =
convoluted, but it's certainly better than nothing.

> What its not going to do is replace large scale test harnesses and detail=
ed
> test plans. We still need the ability to generate large numbers of client=
s
> hammering a server to expose particular problems.=20

Amen. I have a couple ideas on how that could be done, but all require a bi=
t more baking before tossing them into public view.=20