Merge pull request #4440 from RosettaCommons/roccomoretti/fix_scriptvar_test
Don't overwrite log file in job_definition_script_vars integration test
This should fix the valgrind test.
notify author
notify list [rosetta-logs@googlegroups.com]
Merge pull request #4412 from RosettaCommons/roccomoretti/submodule_update
Update (merge) the top-level submodules to their most recent master
(These were all fast forward merges.)
notify author
notify list [rosetta-logs@googlegroups.com]
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.
notify author
notify list [rosetta-logs@googlegroups.com]
Merge pull request #4320 from RosettaCommons/danpf/make_frags_bm
make_fragments scientific test
Vikram K. Mulligan 5 years Daniel: I think the unit test failure here can be safely ignored. These tests have occasionally been timing out, and this is almost certainly unrelated to your changes. I'm going to re-queue the test.
notify author
notify list [rosetta-logs@googlegroups.com]
Merge pull request #4427 from RosettaCommons/BobbyLangan/rosettamp_bugfix
Change to membrane/util.cc to allow 'center' or 'normal' vectors to parse as floats
notify author
notify list [rosetta-logs@googlegroups.com]
Merge pull request #4428 from RosettaCommons/aleaverfay/jd3_bug_writing_output_if_last_job_fails
Fix bug where jd3::MPIjobdist was not outputting
In particular, if the last job in a particular stage
did not result in a success, then the job distributor
wouldn't ask the job queen if there were any jobs to
output. This is problematic as the job queen waits
until all jobs for a stage have completed before telling
the job distributor what jobs should be output.
Therefore, if the last job fails, the job distributor
will never get any jobs from the job queen to output!
Thanks Odessa @odaunc for bringing this bug to my attention!
New unit test fails with the old code and works with the new code.
notify author
notify list [rosetta-logs@googlegroups.com]
Merge pull request #4430 from RosettaCommons/benchmark
Testing scripts update. Updating headers and levels tests to use new directory layout. Updating build.clean.* test to use HTTPS instead of SSH for submodule cloning.
notify author
notify list [rosetta-logs@googlegroups.com]