Hi,
On Tue, May 28, 2013 at 3:26 PM, <dcerutti.rci.rutgers.edu> wrote:
> This is why I
> added the idea that each commit trigger one GNU compilation only, for
> serial and parallel builds. This, I think, will catch 90% of the problems
But developers should be doing this anyway before committing (as well
as running the tests), especially with GNU compilers since everyone
has access to them. Then the dashboard can catch other issues (like if
the compile breaks with a compiler you don't have access to). One
thing I like to do when I've made relatively large changes is I have a
separate GIT directory (i.e. separate from the one I commit from) that
I will update after I've made my changes and compile/test from there;
this catches things that don't necessarily show up in the other
directory (like if I forgot to 'git add' a file).
-Dan
--
-------------------------
Daniel R. Roe, PhD
Department of Medicinal Chemistry
University of Utah
30 South 2000 East, Room 201
Salt Lake City, UT 84112-5820
http://home.chpc.utah.edu/~cheatham/
(801) 587-9652
(801) 585-9119 (Fax)
_______________________________________________
AMBER-Developers mailing list
AMBER-Developers.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber-developers
Received on Tue May 28 2013 - 15:00:02 PDT
