Dear Rosetta Users,
I'm new to Rosetta and fall into some errors when tried to test the installation.
I downloaded version 3.13 for Linux system. Then I did the installation according to the tutorial:
I extracted the binary
tar -xvzf rosetta_bin_linux_3.13_bundle.tgz
cd rosetta_bin_linux_2021.16.61629_bundle/main/source
Since I have 12 cores I did and wanted to have MPI version of Rosetta
./scons.py -j 12 mode=release bin extras=mpi
The installation went smooth and I haven't got any error messages.
Finally, I wanted to check if the installation was proper and I run unit tests according to this tutorial: https://www.rosettacommons.org/docs/latest/development_documentation/test/run-unit-test
So I did
cd osetta_bin_linux_2021.16.61629_bundle/main/source
./scons.py -j 12 mode=debug
./scons.py -j 12 mode=debug cat=test
python test/run.py
and got the following error message
More than one test to run - enabling mute.
Identifying platform...
Platform found: release/linux/4.15/64/x86/gcc/7/default
/bin/sh: 1: build/test/release/linux/4.15/64/x86/gcc/7/default/protocols.test: not found
Could not acquire list of available tests from library protocols.test, request terminated with error:
/bin/sh: 1: build/test/release/linux/4.15/64/x86/gcc/7/default/protocols.test: not found
Terminating...
Some of the unit test suite terminate abnormally!
However, when I used some test data for docking, Rosetta docking module worked well and the results looked reasonable.
Can you help me solve the problem with unit tests?
Thanks for your help!
Karolina
The issue is that it's trying to find the release version of the tests, but you only compiled the debug versions of the tests.
Frankly, the unit tests are primarily for developers who are changing code. As an end user, I probably wouldn't bother with them. (In fact, when compiling Rosetta for production usage myself, I don't run the unit tests.)
If you don't have any complilation errors, and aren't experiencing any odd crashing when you run Rosetta applications, I wouldn't be concerned about the build/running the unit tests.
Oh... Okay then! I won't bother with the tests - thanks! :)