[MOAB-dev] failed to run parallel test case: moab-5.1.0 with mpich-3.3

[Lorenzo Botti]

Dear Vijay,
I tried to run the test individually last week and some of them hang. I do
not remember exactly which but I can tell you in more detail if you need to
know. Anyway, since something is not working correctly, I'd like to know if
your builds take into account mpich-3.3.
Bests
Lorenzo

On Sun, Jun 9, 2019, 14:59 Vijay S. Mahadevan <vijay.m at gmail.com> wrote:

> Dear Lorenzo,
>
> Sorry about my delayed response. I was on travel this past week and
> couldn't reply to you immediately.
>
> It is puzzling that the tests in parallel folder are getting built as
> expected but "make check" does not run them correctly. I can see that
> mpiexec program was set correctly during configuration and so the next
> logical check here would be to try and launch the test programs
> manually to see whether they succeed.
>
> Can you do the following:
> cd build/test/parallel && mpiexec -n 2 ./parallel_unit_tests &&
> mpiexec -n 2 ./parallel_hdf5_test
>
> Both those tests should run to completion successfully if everything
> is setup correctly. If these succeed, I would be out of ideas until we
> can replicate it locally. Let me know the result with the above
> experiment.
>
> Thanks,
> Vijay
>
> On Sun, Jun 2, 2019 at 6:22 AM Lorenzo Botti <bottilorenzo at gmail.com>
> wrote:
> >
> > > Can you do the following two variations:
> > >
> > > 1) Re-verifying your current approach
> > >   a) Go to test/parallel and do `make clean && make check | tee
> make_check.log`
> > >   b) Send us make_check.log so that we can see if things compile but
> > > do not run or nothing actually happens there.
> > >
> >
> > Please find in attachment the make_check.log... so yes this is the
> > point where it hangs.
> >
> >
> >
> >
> > > 2) Retry out-of-source
> > >   a) Perform `make distclean` in your in-source build
> > >   b) Do: `mkdir build && ../configure <configure arguments> && make
> > > all && make check`
> > >
> > > Let me know if (1) yields something useful and if not, (2) should
> > > resolve the issue. If (2) does work, then we may have a problem with
> > > in-source builds and I can check that on a workstation to replicate
> > > the problem. Hope my instructions above aren't confusing.
> > >
> >
> > I got same behavior with out-of-source, following your instructions,
> > see attached config.log
> >
> > Bests
> > Lorenzo
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/moab-dev/attachments/20190609/d4fba109/attachment.html>