[gmx-developers] release candidate for 5.1 imminent
hess at kth.se
Tue Jun 30 20:43:18 CEST 2015
This looks like a case where the automation fails. I'll look into it.
On 06/30/2015 08:36 PM, Mark Abraham wrote:
> An unexpected issue came up while running my automated tests of the RC
> tarball. Some newly-merged fatal errors that try to stop people using
> mdrun inefficiently sometimes cause the regressiontests to fail
> because they are defaulting to using too many threads. See
> We do have machinery in regressiontests to automatically re-try the
> test with fewer threads/cores/whatever, but only in response to a set
> of known mdrun error outputs, so we could add this particular error to
> that set.
> But in this case, the note on line 43 suggests we should improve the
> code leading to the fatal error so that we aren't subsequently
> double-crossing ourselves. What do you think, Berk?
> (This didn't come up in per-commit testing because we limit those to
> small numbers of cores because there's normally multiple testing
> instances running simultaneously on the same machine. We can probably
> do a better job of this after 5.1, with a bunch of new hardware
> On Tue, Jun 30, 2015 at 4:28 PM Mark Abraham <mark.j.abraham at gmail.com
> <mailto:mark.j.abraham at gmail.com>> wrote:
> I'll ship release candidate for 5.1 today, once I've sorted out
> release notes and put stuff on servers, etc.
> The last possible behaviour changing patch for 5.1 is
> https://gerrit.gromacs.org/4753, if someone's inspired to make it
> work well. https://gerrit.gromacs.org/4272 is too late, even if
> someone's inspired to split off part of it.
> release-5-1 branch is active on git, gerrit and jenkins. Any
> remaining bug-fix patches on master branch in gerrit may be
> cherry-picked to release-5-1 branch (on gerrit or locally, as needed).
> Business will proceed as usual in release-5-1 - such branches are
> open only for all kinds of bug fixes, addition of docs, addition
> of tests, and in all cases aimed at stability and correctness.
> master branch is open for normal business, but people will
> probably be a bit quiet there for a while ;-)
> We are likely to issue a new 4.6.x some time soon, as we've had a
> number of mdrun issues fixed. (There's one known bug outstanding
> to fix, hopefully Michael has time real soon now.) Then
> release-4-6 branch will be permanently closed. We cannot maintain
> three active release branches and a development branch.
> We'll do a 5.0.x soon also, then change the policy for release-5-0
> to "mdrun correctness bug fixes only" mode.
> Thanks to all for the hard work!
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the gromacs.org_gmx-developers