You are here

Error running unit test executable

5 posts / 0 new
Last post
Error running unit test executable
#1

Hello!

I was trying to test my Rosetta installation and at the begining of test I've got an error:

I didn't find any solution on Rosetta Forum. 

server@localhost:~$ python test/run.py
Identifying platform...

Platform found: debug/linux/4.10/64/x86/gcc/6.3/default
Error running unit test executable for protocols.test - not all tests may be availible.

Error running unit test executable for core.test - not all tests may be availible.

Error running unit test executable for basic.test - not all tests may be availible.

Error running unit test executable for numeric.test - not all tests may be availible.

Error running unit test executable for utility.test - not all tests may be availible.

Error running unit test executable for apps.test - not all tests may be availible.

-------- Unit test summary --------
Total number of tests: 0
number tests passed: 0
number tests failed: 0
Success rate: 0%
---------- End of Unit test summary
Done!

Please help me in this issue.

Regards

Category: 
Post Situation: 
Tue, 2017-07-04 22:59
destrudo

I'm guessing you didn't build the unit tests.  They build separately.  

 

scons.py -j# cat=test

 

Note if you only built your libraries in release mode, you'll need to add mode=release to scons and a similar flag (I forget exactly what it is, I think it's --mode=release) to test.py.  Officially the unit tests are supposed to be built and run in debug mode.  In most circumstances the release build is fine too.  (The debug mode has extra checks, so sometimes stuff will pass release that fails debug).

Wed, 2017-07-05 07:49
smlewis

There's also some trajectory changes due to optimization which means that things which pass debug mode will fail in release mode.

IIRC there are a small subset of tests which are known to be failing when run in release mode, but are perfectly fine when run in debug mode. These are not a concern.

Thu, 2017-07-06 12:52
rmoretti

Unfortunately I have the same error. Here is some output:

destrudo@ubuntu:~/rosetta_bin_linux_2017.18.59451_bundle/main/source$ python scons.py -j1 cat=test
scons: Reading SConscript files ...
Running versioning script ... /bin/sh: 1: git: not found
Done. (0.0 seconds)
Number of option files updated: 0
Total 3964 options.
Finished updating ResidueProperty code -- no changes needed
Finished updating VariantType code -- no changes needed
scons: done reading SConscript files.
scons: Building targets ...
scons: `.' is up to date.
scons: done building targets.
 

 

destrudo@ubuntu:~/rosetta_bin_linux_2017.18.59451_bundle/main/source$ python test/run.py  --mode=debug
Identifying platform...

Platform found: debug/linux/4.10/64/x86/gcc/6.3/default
Error running unit test executable for protocols.test - not all tests may be availible.
     
Error running unit test executable for core.test - not all tests may be availible.
     
Error running unit test executable for basic.test - not all tests may be availible.
     
Error running unit test executable for numeric.test - not all tests may be availible.
     
Error running unit test executable for utility.test - not all tests may be availible.
     
Error running unit test executable for apps.test - not all tests may be availible.
     
-------- Unit test summary --------
Total number of tests: 0
  number tests passed: 0
  number tests failed: 0
Success rate: 0%
---------- End of Unit test summary
Done!

Mon, 2017-07-17 04:14
destrudo

Did you compile the Rosetta libraries in debug mode before compiling the unit tests? (e.g. plain 'python scons.py -j1')

Also, what does the directory tree under ~/rosetta_bin_linux_2017.18.59451_bundle//main/source/build/ look like? Is there a src/debug/linux/4.10/64/x86/gcc/6.3/default/ directory, or do you only get part way down the tree?

 

Mon, 2017-07-17 07:53
rmoretti