Piotr Jaroszyński wrote: > Hello, > > There was some discussion about forcing/not forcing tests in EAPI-1, but > there > was clearly no compromise. Imho, tests are very important and thus I want to > discuss them a little more, but in more sensible fashion. > > Firstly each test can be(not all categories are mutually exclusive): > - not existant > - non-functional > - not runnable from ebuild > - useful but unreasonable resource-wise > - useful and reasonable resource-wise > - necessary > - known to partially fail but with a way of skipping failing tests > - known to partially fail but with no easy way of skipping failing tests > Is that list comprehensive?
There are some tests that require root, and thus only fails with userpriv. Kernel modules that attempt to load themselves to make sure there are no problems are an example. I forget the exact package offhand. Otherwise I like where this discussion is going ;) -- [EMAIL PROTECTED] mailing list
