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

Revisions №13641

branch: commits 「№13641」
Commited by: Vikram K. Mulligan
GitHub commit link: 「59bbbc01e9f80046」 「№4221」
Commit date: 2019-09-14 20:03:43

Merge pull request #4221 from RosettaCommons/vmullig/why_the_hell_is_rosetta_still_defaulting_to_leaking_memory_when_every_developer_has_complained_about_this_at_one_point_or_another Switching default for -jd2:delete_old_poses to "true" There isn't really a reason for Rosetta to leak memory by default, to my mind.

Vikram K. Mulligan 9 months
This test is giving me trouble in the vmullig/add_options_to_simple_cycpep_predict_incremental_merge1 branch, and I'm not sure whether it's because of my changes or because of a problem on the test server. I'm re-queueing it for the master branch (where it was running fine before, in 3 hours 1 minute) for comparison.
Test: linux.gcc.cxx11thread.mpi.serialization.scientific.simple_cycpep_predict

 View log


 View log in dialog  View log in log in separate window