The (long) Docker test case, instead of running hex, triggers the Hex GUI popping up with an error message:
*Error* A maximum of 3 PDB files can be given on the command line
The test case then reports a failure:
FAILED: urfin 1A2P_1-1A19_2_hex
Job details:
Command: //usr/local/lib/hex/bin/hex -ncpu 2 -nice 0 -noexec < /tmp/tmphWPHoZ_test_docker_1008/1A2P_1-1A19_2_hex.mac > /tmp/tmphWPHoZ_test_docker_1008/1A2P_1-1A19_2_hex.mac.log
input: /tmp/tmphWPHoZ_test_docker_1008/1A2P_1-1A19_2_hex.mac
Hex log: 1
Hex out: /tmp/tmphWPHoZ_test_docker_1008/1A2P_1-1A19_2_hex.out
<type 'exceptions.IOError'> in Docker.py line 475:
(2, 'No such file or directory').
But then continues and finishes (falsely) as "OK".
python Biskit/Dock/Docker.py
* Suse 10.2 AMD64 and
* Ubuntu 7.04 32bit
None.
The fact that the same test case did work earlier on, means that this must be related to more recent changes in the code.
Fixed in revision 925
The Hex command line had changed and didn't any longer accept the input script at STDIN.
Moreover, hex now opens the GUI by default unless wrapped by a ssh call.
Tested with Hex 4.5