| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Ryan Hill wrote: |
| 5 |
> There are several packages in portage (and even in base-system) that fail |
| 6 |
> in src_test when userpriv/usersandbox is enabled or disabled. That is, some |
| 7 |
> testsuites fail when run as root and some fail if not run as root. |
| 8 |
> |
| 9 |
> I'd like a simple consistent way to mark or handle these packages without |
| 10 |
> disabling tests altogether (RESTRICT=test). As mentioned recently, checking |
| 11 |
> ${FEATURES} in an ebuild is frowned upon, and it doesn't seem right to handle |
| 12 |
> this on a per-ebuild basis. How would something like this best be implemented? |
| 13 |
> A split up RESTRICT (test_userpriv/test_nouserpriv)? test.eclass? Something |
| 14 |
> else? Looking at the bigger picture, are there any other situations where |
| 15 |
> finer-grained control over the test system would be helpful? |
| 16 |
> |
| 17 |
> While I'm on the subject, I also thought it would be cool to have the option to |
| 18 |
> not die on a src_test failure, but instead to dump the log file and continue |
| 19 |
> on to the install phase. I know this can be done per-ebuild, but it'd be |
| 20 |
> a useful global option. |
| 21 |
> |
| 22 |
|
| 23 |
I, for one, would like to be able to control whether or not to run tests |
| 24 |
that take a huge amount of time to run. Some test suites are |
| 25 |
ridiculously comprehensive, and if we could have an option to disable |
| 26 |
only those, or even run a reduced test suite, that'd be pretty neat. |
| 27 |
|
| 28 |
- --Ravi |
| 29 |
|
| 30 |
-----BEGIN PGP SIGNATURE----- |
| 31 |
Version: GnuPG v2.0.7 (GNU/Linux) |
| 32 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org |
| 33 |
|
| 34 |
iD8DBQFHBI2JsDgfoknqAqMRAj7+AKDY1wJYClm13wmxMWxgGxCfqzlfOwCgl2tT |
| 35 |
qXwJ8Cz5HL+W1ois4IRzvOw= |
| 36 |
=CjAo |
| 37 |
-----END PGP SIGNATURE----- |
| 38 |
-- |
| 39 |
gentoo-dev@g.o mailing list |
Archives