| 1 |
Ravi Pinjala a écrit : |
| 2 |
> I, for one, would like to be able to control whether or not to run tests |
| 3 |
> that take a huge amount of time to run. Some test suites are |
| 4 |
> ridiculously comprehensive, and if we could have an option to disable |
| 5 |
> only those, or even run a reduced test suite, that'd be pretty neat. |
| 6 |
|
| 7 |
We've already had this discussion before [1] and there is no |
| 8 |
one-size-fits-all solution for tagging tests. |
| 9 |
|
| 10 |
Ryan's plan only proposes to enable/disable tests based on whether they |
| 11 |
can run inside a sandbox. That much is doable. Trying to quantify the |
| 12 |
time a test suite will take to complete is impossible : different |
| 13 |
arches, vastly different CPU clock speeds, same for HDDs sizes and |
| 14 |
speeds, ... is impossible. |
| 15 |
|
| 16 |
Basically, it boils down to "if you're running FEATURES=test, you should |
| 17 |
know what you're doing". |
| 18 |
|
| 19 |
+1 on Ryan's idea |
| 20 |
|
| 21 |
Rémi |
| 22 |
|
| 23 |
[1] http://archives.gentoo.org/gentoo-dev/msg_145157.xml |
| 24 |
-- |
| 25 |
gentoo-dev@g.o mailing list |
Archives