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

Revisions №60666

branch: master 「№60666」
Commited by: Vikram K. Mulligan
GitHub commit link: 「cfb2bc97fd8fa647」 「№3867」
Difference from previous tested commit:  code diff
Commit date: 2019-03-22 01:00:29
linux.clang linux.gcc linux.srlz mac.clang
linux.PyRosetta.unit linux.gcc.python36.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 mac.clang.static.build.release linux.ui mac.ui build.xcode beautification code_quality.clang_analysis serialization integration.mpi integration.release_debug integration.tutorials integration.ubsan integration performance profile release.PyRosetta4.Debug ubuntu.clang.python27.release.PyRosetta4.MinSizeRel ubuntu.clang.python35.release.PyRosetta4.MinSizeRel 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 unit.addsan linux.clang.unit.release linux.gcc.unit.release

Merge pull request #3867 from RosettaCommons/vmullig/fix_motifgraftmover Fixing uninitialized variable error that's bothering gcc 8.2 The recent changes to the MotifGraftMover left gcc 8.2 complaining about an unintialized variable. Technically, the value would never be used uninitialized, but it would have been hard for the compiler to know that (and anyways, it was fragile -- a small change to the code would result in the variable being used uninitialized). This initializes the relevant variable.

Test: linux.gcc.mpi.serialization.integration.mpi

Failed sub-tests (click for more details):
Test: linux.clang.integration.tutorials

Failed sub-tests (click for more details):
Test: linux.clang.performance

Failed sub-tests (click for more details):