Thanks.
Btw, I saw the update for submodules. Can you double check if your commit
the correct? For example pytraj was not updated for a while but still
seeing in your log
Summary of changes:
AmberTools/src/ambertools-binary-build | 2 +-
AmberTools/src/cphstats | 2 +-
AmberTools/src/cpptraj | 2 +-
AmberTools/src/parmed | 2 +-
AmberTools/src/pytraj | 2 +-
cmake
E.g:
cd Ambertools/src/pytraj
git diff origin/master
(On train now so I can not check)
Hai
On Wed, Sep 6, 2017 at 2:44 AM David Cerutti <dscerutti.gmail.com> wrote:
> Hey AmberDevs,
>
> So it appears that for some time the test cases have been thoroughly broken
> (Ross, we were better off with your hawkish prodding on this). The problem
> has been traced, and I have devised some workarounds. All executables
> referenced by the test cases will now read ${AMBERHOME}/bin/<name>. This
> has been done for what I THINK are all the test cases in the main suite,
> and I will get to AmberTools soon. Having verified that the test cases now
> pass for me once again, I am committing these edits directly to the master
> branch. Please let me know if you experience any problems--it SHOULD be a
> giant improvement over recent behavior, but there is such a diversity of
> test cases, file names, and conventions that I may have missed something.
>
> Cheers,
>
> Dave
> _______________________________________________
> AMBER-Developers mailing list
> AMBER-Developers.ambermd.org
> http://lists.ambermd.org/mailman/listinfo/amber-developers
>
_______________________________________________
AMBER-Developers mailing list
AMBER-Developers.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber-developers
Received on Wed Sep 06 2017 - 06:30:04 PDT
