Hi All,
> I think all we need is a cuda cruise control build for amber11-with-
> patches,
> which would have caught this problem. [We currently only test the
> serial
> version of amber11-with-patches.]
Ok, I setup Cruise Control to also do the CUDA serial and parallel builds
for amber11-with-patches. Of course this does NOT work because the
amber11-with-patches tag is for AMBER Tools 1.4 with AMBER 11+patches which
of course uses an incompatible configure script. Suggestions? We can't have
Cruise Control test building CUDA for amber11-with-patches since this is an
invalidated build target since AT1.4 is no longer compatible with AMBER11.
Thus I think we need amber11-with-patches updated to be AMBER 11 + Patches +
AT15 + Patches since this is what we are effectively releasing and is what
needs to be tested.
Any ideas how we do this? - Just apply all the git commits from
AT1.4+bugfixes until AT1.5 release and then the AT1.5 bugfixes to the
amber11-with-patches branch?
All the best
Ross
/\
\/
|\oss Walker
---------------------------------------------------------
| Assistant Research Professor |
| San Diego Supercomputer Center |
| Adjunct Assistant Professor |
| Dept. of Chemistry and Biochemistry |
| University of California San Diego |
| NVIDIA Fellow |
|
http://www.rosswalker.co.uk |
http://www.wmd-lab.org/ |
| Tel: +1 858 822 0854 | EMail:- ross.rosswalker.co.uk |
---------------------------------------------------------
Note: Electronic Mail is not secure, has no guarantee of delivery, may not
be read every day, and should not be used for urgent or sensitive issues.
_______________________________________________
AMBER-Developers mailing list
AMBER-Developers.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber-developers
Received on Sat Nov 26 2011 - 19:00:03 PST
