「view this page in B3 βῆτα server」

Revisions №60801

branch: master 「№60801」
Commited by: Rocco Moretti
GitHub commit link: 「dee179c92af5eb5a」 「№4036」
Difference from previous tested commit:  code diff
Commit date: 2019-06-26 09:38:37
linux.clang linux.gcc linux.srlz mac.clang
debug
release
unit
linux.PyRosetta.unit linux.gcc.python37.PyRosetta4.unit mac.PyRosetta.unit build.clean.debug cppcheck mysql postgres linux.clang.python36.build.debug linux.zeromq.debug mpi mpi.serialization linux.icc.build.debug OpenCL mac.clang.python36.build.debug build.header build.levels ninja graphics static linux.ui mac.ui build.xcode beautification serialization integration.mpi integration.release_debug integration.valgrind integration performance profile release.source linux.clang.score linux.gcc.score mac.clang.score linux.scripts.pyrosetta scripts.rosetta.parse scripts.rosetta.validate scripts.rosetta.verify linux.clang.unit.release linux.gcc.unit.release util.apps

Merge pull request #4036 from RosettaCommons/roccomoretti/integration_python3 Switch the test server to run integration.py with Python3. Use Python3 on the test server (the same one running the benchmark.py script), such that Sergey only has to manage dependencies for one(ish) Python version. While at this point we should be able to run integration.py with either Python2 or Python3, not all of the sub-scripts being run in the command files of the integration tests themselves can do so. To address this, add python2 and python3 substitution variables in the integration test scripts (to go along with the existing python one), for those tests which need a specific version. -- Please continue to use `%(python)s` if it the 2/3 choice doesn't matter - this will be whatever python with which the integration.py script was launched. The interpreter for python2 or python3 may be autodiscovered based on your path, and might not be the one you really want to use. This also updates the integration command files for those scripts which need to use Python2.