[Q-e-developers] test suite verbosity and output redirection

[Michael Banck]

Hi,

since the test-suite was overhauled, it no longer outputs anything while
it runs.  This should in principle be resolved in 6.0 as it runs
testcode.py --verbose, however for some reason the Debian build system
still does not output anything:

(cd test-suite; /usr/bin/make run-tests)
make[2]: Entering directory
'/<<BUILDDIR>>/espresso-6.0.0~r13008+dfsg/test-suite'
### wget or curl not found: will not be able to download missing PP ###
### wget or curl not found: will not be able to download missing PP ###
env QE_USE_MPI=0
/<<BUILDDIR>>/espresso-6.0.0~r13008+dfsg/test-suite/..//test-suite/testcode/bin/testcode.py
--verbose --category=cp_all
[no more output]

This is a problem because Debian autobuilders are configured to abort
builds if there is no output for 3+ hours (default timeout) under the
assumption that the build is stuck. So on slower hardware, it might make
the build abort before the test suite finishes.

I have the feeling the Debian build system (which runs in a chroot,
besides others) is doing some weird redirection here or something, but
I've never seen this problem before.

Anybody have an idea what could be going on here?


Thanks,

Michael