Cool, and helpful! One comment, though, in text below
On Thu, Nov 29, 2012 at 11:14 PM, Ross Walker <ross.rosswalker.co.uk> wrote:
> Hi All,
>
> I just wanted to let all the developers know about the Cruise Control
> system we have setup for automatic compilation and testing of the AMBER
> Git tree. You can find it here:
>
> http://cc.ambermd.org/dashboard/tab/dashboard
>
> This runs a series of builds and also runs the full test suite whenever
> there are new commits to the git tree. I would encourage you to all keep
> an eye on this. It is a very useful and automated way to find out if
> something you committed broke the build. It also runs all the test cases
> (although failures in the test suite will not result in cruise control
> reporting the build as being broken). We are still ironing out the kinks,
> especially with regards to the automated testing but it does work
> reasonably well.
One thing worth handling explicitly in the test cases is an infinite hang
(which is made routine by MPI). This happened prior to the Amber 12
release with the NEB tests due to a presumed bug in the OpenMPI/GNU
compiler combo. I'm not sure how to handle this, though, and can't offer
any ideas :).
All the best,
Jason
--
Jason M. Swails
Quantum Theory Project,
University of Florida
Ph.D. Candidate
352-392-4032
_______________________________________________
AMBER-Developers mailing list
AMBER-Developers.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber-developers
Received on Fri Nov 30 2012 - 04:30:03 PST
