The issue was reported to upstream in May [1]. I think until we get a fix, it's best to disable that specific test.
Cheers, Nico [1] https://github.com/trilinos/Trilinos/issues/1332 On Sun, Jul 16, 2017 at 1:51 PM Graham Inggs <gin...@debian.org> wrote: > On 16 July 2017 at 13:12, Drew Parsons <dpars...@debian.org> wrote: > > Testing trilinos build on a porterbox for the mumps 5.1.1 transition. > > > > The following tests FAILED: > > 617 - ML_MLP_NonSym_MPI_4 (Failed) > > 668 - Phalanx_dag_manager_MPI_1 (Failed) > > > > Not sure if it's the new mumps, new openmpi 2.1.1 or something else. > > Full build log attached. > > Reproducible build history shows FTBFS since 2017-07-02: > https://tests.reproducible-builds.org/debian/history/amd64/trilinos.html > > Although with only one test failure: > > The following tests FAILED: > 668 - Phalanx_dag_manager_MPI_1 (Failed) > >
-- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers