I've reverted the default config for now - not sure when I'll get another
chance to tackle it, but hopefully soon. Looks like there is a problem in the
TCP oob where we lose messages every now and then.
On Jun 11, 2012, at 11:44 AM, Jeff Squyres wrote:
> On Jun 11, 2012, at 1:42 PM, Ralph
On Jun 11, 2012, at 1:42 PM, Ralph Castain wrote:
>>> will have to look more at the loop_spawn issue later.
>> The original one I reported, I assume? I see similar stacks on segfaults
>> with a variety of tests. So, I think it's not specific to loop_spawn.
>
> It's a race condition in the
On Jun 11, 2012, at 11:38 AM, Eugene Loh wrote:
> On 6/9/2012 6:49 PM, Ralph Castain wrote:
>>
>> I fixed this one, I believe
> Sorry, I'm confused. You think you fixed the oob:ud:qp_init one you mean?
> Which rev has the fix?
Yes - r26587. MTT tests look pretty good at that point, per this
On 6/9/2012 6:49 PM, Ralph Castain wrote:
I fixed this one, I believe
Sorry, I'm confused. You think you fixed the oob:ud:qp_init one you
mean? Which rev has the fix?
will have to look more at the loop_spawn issue later.
The original one I reported, I assume? I see similar stacks on
