Yeah, I found that as well. In both the cases, I get fi_getname error. Checking
for the fix now-
fi_getname(): simple/scalable_ep.c:284, ret=-258 (Operation not permitted in
current state)
fi_getname(): simple/msg_sockets.c:126, ret=-258 (Operation not permitted in
current state)
getnameinfo: ai_family not supported
[error] fabtests:simple/msg_sockets.c:132: Unable to get ep_addr as string!
-Shantonu
-----Original Message-----
From: ofiwg [mailto:[email protected]] On Behalf Of Hefty,
Sean
Sent: Friday, October 28, 2016 12:30 PM
To: Hefty, Sean <[email protected]>; Jeff Squyres (jsquyres)
<[email protected]>
Cc: OFIWG Mailing list <[email protected]>
Subject: Re: [ofiwg] sockets fabtests failure in testing for 1.4.0 release
> Fabtests commit def17d223107244f1d9ce77a440085f717a4b69e occurred
> between v1.3 and 1.4.
>
> This commits applied fixes to both of the tests that are failing.
>
> I haven't found a relevant change to libfabric yet, but my guess is
> that a fix was applied to the sockets provider, which exposed the bugs
> in fabtests. If that's the case, then the failures are okay.
This looks like the likely culprit:
1d3bbe6e8b959507380799bc5c27fb55959ebebe
prov/sockets: Add error-checks in fi_getname
- Added checks in fi_getname to see if the endpoint is
enabled (fi_enable/fi_listen or fi_setname).
(Please see #2188)
Signed-off-by: Jithin Jose <[email protected]>
_______________________________________________
ofiwg mailing list
[email protected]
http://lists.openfabrics.org/mailman/listinfo/ofiwg
_______________________________________________
ofiwg mailing list
[email protected]
http://lists.openfabrics.org/mailman/listinfo/ofiwg
