On Thu, 29 May 2014 04:09:22 -0500
Steev Klimaszewski <st...@gentoo.org> wrote:

> On Tue, 2014-05-27 at 10:09 -0400, Ian Stakenvicius wrote:
> > I don't know how much chromium is built and tested on lesser-used
> > arches (ie: arm, hppa, ia64, etc), but if there are dev's that try
> > and maintain these keywords that aren't in the team, it might be a
> > good idea to leave src_test in place, for them. 
> 
> Well, Chromium is the only browser I use on my Chromebook - it takes
> about 5 hours to compile natively, but I don't run the tests on it.
> If it doesn't work... well, it doesn't work...

It gets fun when the scrollbar doesn't work on 5% of the sites or so;
happened to me, because a dependency of a dependency of Chromium was
broken. At which point I really hoped I would've enabled tests on them.

Can be glad that the fix didn't involve recompiling Chromium...

In general it has always worked well after a compile; but, there's every
now and then one or another annoying regression, like recent Chromium
had some font issues or some random tabs crash some versions ago and ...

If a test catches one of these, you can immediately report the problem;
if it is left untested, you'll have to do a debugging adventure instead.

While I don't run tests myself; the need for them is clear, for those
that aim for more production ready systems (eg. university network PCs).

-- 
With kind regards,

Tom Wijsman (TomWij)
Gentoo Developer

E-mail address  : tom...@gentoo.org
GPG Public Key  : 6D34E57D
GPG Fingerprint : C165 AF18 AB4C 400B C3D2  ABF0 95B2 1FCD 6D34 E57D

Attachment: signature.asc
Description: PGP signature

Reply via email to