Ticket #696 (closed bug: fixed)

Opened 4 months ago

Last modified 4 months ago

Possible problem in persistent requests

Reported by: gropp Owned by:
Priority: minor Milestone:
Component: mpich2 Keywords:
Cc:

Description

We routinely fail one of the Fortran tests in the Intel suite when using the Intel compiler - the fortran/persist_request/functional/MPI_Send_init_overtake test. There is a C test with the same name, but it turns out that the Fortran test creates and starts a bunch of requests and then uses MPI_Waitall while the C test creates a request, starts it, and then waits on it.

Now, there is a character variable that is too short in the Fortran version, which I'll fix. It would be good, however, to have a C version of this Fortran test that used the Waitall.

Attachments

Change History

Changed 4 months ago by Rajeev Thakur

I believe the two tests fail with the current version of the Intel
compiler, but not the previous version. We have been ignoring the
failure thinking it is a bug in the test or the compiler.

Rajeev


>  We routinely fail one of the Fortran tests in the Intel
> suite when using  the Intel compiler - the
> fortran/persist_request/functional/MPI_Send_init_overtake
> test.  There is  a C test with the same name, but it turns
> out that the Fortran test  creates and starts a bunch of
> requests and then uses MPI_Waitall while the  C test creates
> a request, starts it, and then waits on it.
>
>  Now, there is a character variable that is too short in the
> Fortran  version, which I'll fix.  It would be good, however,
> to have a C version  of this Fortran test that used the Waitall.

Changed 4 months ago by thakur

  • status changed from new to closed
  • resolution set to fixed

Bill fixed the Intel tests.

WARNING! You need to either login using OpenID here or enter your email address here before you can create or edit tickets. Otherwise the ticket will get treated as spam. More information on creating tickets can be found here.

Don't forget to add your email address to the cc list to make sure that you get updated of the ticket status.

Add/Change #696 (Possible problem in persistent requests)

Author



Change Properties
Action
as closed
Next status will be 'reopened'
 
Note: See TracTickets for help on using tickets.