Hi,
I routinely run all the tests and did not notice a 'thoroughly broken'
state (see below for details on my last run). Digging into the logs
it appears that most problems were in those parts of amber that are
now in submodules. Unfortunately, i am not doing the submodule thing
because i read on the wiki that that requires git version 2.
All the OSC machines have either git version 1.8.3.1 or 1.7.1.
Is there an easy way to git the submodules with those gits ?
thanks,
scott
Sep 07 1:47:07pm owens-rw01.ten.osc.edu 223$ /tmp/amber a gitdesc
git describe --debug --dirty !*
Sep 07 1:47:10pm owens-rw01.ten.osc.edu 224$ /tmp/amber gitdesc
searching to describe HEAD
finished search at 5397706800fde35ddd3b0a86d8437d4ac15b65d4
annotated 34792 v_11
traversed 34793 commits
v_11-34792-gb05b072-dirty
pgf90 17.3-0 64-bit target on x86-64 Linux -tp haswell
Finished serial test suite for Amber 17 at Fri Sep 1 19:56:45 EDT 2017.
130 file comparisons passed
6 file comparisons failed
19 tests experienced errors
Summary of AmberTools serial tests:
1244 file comparisons passed
70 file comparisons failed
5 tests experienced errors
On Wed, Sep 06, 2017 at 12:06:50PM -0400, David Cerutti wrote:
> Sorry! I thought I had restored the execute permissions. This is fixed
> now.
>
>
> On Wed, Sep 6, 2017 at 9:02 AM, Hai Nguyen <nhai.qn.gmail.com> wrote:
>
> > 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.
_______________________________________________
AMBER-Developers mailing list
AMBER-Developers.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber-developers
Received on Thu Sep 07 2017 - 11:30:03 PDT
