Rémi Cardona wrote:
> Ravi Pinjala a écrit :
>> I, for one, would like to be able to control whether or not to run tests
>> that take a huge amount of time to run. Some test suites are
>> ridiculously comprehensive, and if we could have an option to disable
>> only those, or even run a reduced test suite, that'd be pretty neat.
>
> We've already had this discussion before [1] and there is no
> one-size-fits-all solution for tagging tests.
>
> Ryan's plan only proposes to enable/disable tests based on whether they
> can run inside a sandbox. That much is doable. Trying to quantify the
> time a test suite will take to complete is impossible : different
> arches, vastly different CPU clock speeds, same for HDDs sizes and
> speeds, ... is impossible.
I usually disable tests on a per-package basis using /etc/portage/env
entries.
[EMAIL PROTECTED] ~ $ cat /etc/portage/env/sci-libs/fftw
NEWFEATURES=
for f in ${FEATURES}; do
if [[ ! $f == "test" ]]; then
NEWFEATURES="${NEWFEATURES} $f"
fi
done
FEATURES="${NEWFEATURES}"
--
fonts / wxWindows / gcc-porting / treecleaners
EFFD 380E 047A 4B51 D2BD C64F 8AA8 8346 F9A4 0662 (0xF9A40662)
--
[EMAIL PROTECTED] mailing list
