<div dir="ltr">The issue was reported to upstream in May [1]. I think until we get a fix, it's best to disable that specific test.<div><br></div><div>Cheers,</div><div>Nico<br><div><br></div><div><br></div><div>[1]Â <a href="https://github.com/trilinos/Trilinos/issues/1332">https://github.com/trilinos/Trilinos/issues/1332</a></div></div></div><br><div class="gmail_quote"><div dir="ltr">On Sun, Jul 16, 2017 at 1:51 PM Graham Inggs <<a href="mailto:ginggs@debian.org">ginggs@debian.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 16 July 2017 at 13:12, Drew Parsons <<a href="mailto:dparsons@debian.org" target="_blank">dparsons@debian.org</a>> wrote:<br>
> Testing trilinos build on a porterbox for the mumps 5.1.1 transition.<br>
><br>
> The following tests FAILED:<br>
>Â Â Â 617 - ML_MLP_NonSym_MPI_4 (Failed)<br>
>Â Â Â 668 - Phalanx_dag_manager_MPI_1 (Failed)<br>
><br>
> Not sure if it's the new mumps, new openmpi 2.1.1 or something else.<br>
> Full build log attached.<br>
<br>
Reproducible build history shows FTBFS since 2017-07-02:<br>
<a href="https://tests.reproducible-builds.org/debian/history/amd64/trilinos.html" rel="noreferrer" target="_blank">https://tests.reproducible-builds.org/debian/history/amd64/trilinos.html</a><br>
<br>
Although with only one test failure:<br>
<br>
The following tests FAILED:<br>
668 - Phalanx_dag_manager_MPI_1 (Failed)<br>
<br>
</blockquote></div>