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

Revisions №60813

branch: master 「№60813」
Commited by: Steven Lewis
GitHub commit link: 「eb89b5cd0a63bf74」 「№3930」
Difference from previous tested commit:  code diff
Commit date: 2019-06-28 15:40:31
linux.clang linux.gcc linux.srlz mac.clang
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 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 util.apps

Merge pull request #3930 from RosettaCommons/smlewis/green-pdb-diag This replaces the pass/fail system for the PDB diagnostic scientific test with a 5% failure threshhold instead of the granular "everything that passed before must continue passing". The previous version is "better" but also eternally red because something always goes wrong, and then we are trained to just ignore it. All the old reporting tools remain in place for fine grained diagnostics and finding bugs to fix: the test will now only turn red if something goes wrong in a big way (thousands of PDBs start failing). The threshold is at 5% failure.