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

Revisions №61094

branch: master 「№61094」
Commited by: Rocco Moretti
GitHub commit link: 「e56969d9778b6c99」 「№4413」
Difference from previous tested commit:  code diff
Commit date: 2020-01-09 19:36:10
linux.clang linux.gcc linux.srlz mac.clang
PyRosetta4.notebook gcc-9.gcc.python37.PyRosetta4.unit linux.clang.cxx11thread.serialization.python37.PyRosetta4.unit linux.gcc.python36.PyRosetta4.unit mac.PyRosetta.unit build.clean.debug cppcheck alpine.gcc.build.debug gcc-9.gcc.build.debug 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 build.ninja_debug graphics static linux.ui mac.ui build.xcode beautification code_quality.clang_analysis serialization code_quality.submodule_regression integration.mpi integration.release_debug integration.tensorflow integration.thread integration performance profile release.PyRosetta4.Release 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 gcc-9.gcc.unit util.apps

Merge pull request #4413 from RosettaCommons/roccomoretti/submodule_update_test An initial attempt at a submodule up-to-date test. The way it works is to look at the versions of the submodule for the current commit at the merge point. If there's a regression (that is, if master has submodule commits which the new commit doesn't), then the test will fail with a magenta-failure subtest for that module. (This is special cased for tests on master itself, which looks to make sure we haven't regressed on either of the parent commits of the master merge.) I've also added a check to see if we're up-to-date with the most recent version of the submodule's master. That's not an error, though, it's just reported in the test log.