From: Tim Prins (tprins_at_[hidden])
Date: 2007-04-01 23:15:47
I'm not an MTT developer, but I'll answer #1...
MTT only looks at the return codes from the test programs that are ran. This
is all well and good, but the problem is that some Intel tests return a
meaningful value, and some don't. A while ago I went through and fixed all
the c tests so that they return a meaningful value. But I don't know Fortran,
so I did not even look at the Fortran versions of the tests. It appears that
they are not returning a meaningful value, and that somebody needs to fix
them.
Tim
On Sunday 01 April 2007 09:25 pm, Tim Mattox wrote:
> Hi All,
> I just checked the recent nightly MTT results and found two things of note,
> one for the MTT community, the other for the OMPI developers.
>
> For both, see http://www.open-mpi.org/mtt/reporter.php?do_redir=143
> for details of the failed MTT tests with the OMPI trunk at r14180.
>
> 1) For MTT developers:
> The MTT intel test suite is incorrectly seeing a failed MPI_Allgatherv_f
> test as passed, yet is correctly detecting that the MPI_Allgatherv_c
> test is failing.
> The STDOUT from "passed" MPI_Allgatherv_f seems to indicate that the tests
> actually failed in a similar way to the _c version, but MTT thinks it
> passed. I've not had time to diagnose why MTT is missing this... anyone
> else have some spare cycles to look at this?
>
> 2) For OMPI developers:
> The MPI_Allgatherv_* tests are failing as of r14180 in all test conditions
> on the IU machines, and others, yet this passed the night before on r14172.
>
> Looking at the svn log for r#'s r14173 thru r14180, I can narrow it down to
> one of these changes as the culprit:
> https://svn.open-mpi.org/trac/ompi/changeset/14180
> https://svn.open-mpi.org/trac/ompi/changeset/14179
> https://svn.open-mpi.org/trac/ompi/changeset/14174 (Not likely)
>
> My money is on the much larger r14180 changeset.
> The other r#'s aren't culprits for obvious reasons.