This web mail archive is frozen.
This page is part of a frozen web archive of this mailing list.
You can still navigate around this archive, but know that no new mails
have been added to it since July of 2016.
Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.
This is a bit strange, so I thought I'd ping the group before digging
The onesided test 't_win' is failing for us (specifically the
'FENCE_EPOCH' part). It is only failing when we are NOT using openib.
But here is where it gets strange. The test is run twice: once where the
window memory is allocated using MPI_Alloc_mem, and once where it is
allocated using malloc. When we use MPI_Alloc_mem, it fails. Using
malloc, it works just fine all the time.
That is, I do
"mpirun -np 1 -mca btl <btls> ./t_win" and get:
btls | Using MPI_Alloc_mem | using malloc
self | Fail | Pass
openib,self | Pass | Pass
sm,self | Fail | Pass
tcp,self | Fail | Pass
But we are only using one proc, so the only transport ever used should
be 'self'. So this makes me think something is going on with the mpool
or related part of the code.
Any ideas as to what is going on here?