On 6/4/10 5:35 PM, Jesus Rivero (Neurogeek) wrote: > I've been thinking about this for a while. Some packages have tests > that are meant only for upstream in certain conditions > and are not meant to be ran during installing.
I think that in extreme cases src_test should not call such tests. > As we have ARCH teams, > couldn't we think a way in which TEST teams can > be created? I mean, a bunch of devs only focused on making tests work > or just restrict them? I don't think that would be effective. Making the tests work is hard, especially for packages like gcc, or python. Having FEATURES="test" is intended to make developers catch these failures before checking in. However, with many packages failing tests, people started running FEATURES="-test" or just stopped (or never used) the developer profile. With FEATURES="test test-fail-continue" we should get best of both worlds: run tests always, but don't frustrate people by making build fail "in the middle of long emerge". Paweł
signature.asc
Description: OpenPGP digital signature
