[ofiwg] sockets fabtests failure in testing for 1.4.0 release

Hossain, Shantonu shantonu.hossain at intel.com
Fri Oct 28 12:34:29 PDT 2016

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!

-----Original Message-----
From: ofiwg [mailto:ofiwg-bounces at lists.openfabrics.org] On Behalf Of Hefty, Sean
Sent: Friday, October 28, 2016 12:30 PM
To: Hefty, Sean <sean.hefty at intel.com>; Jeff Squyres (jsquyres) <jsquyres at cisco.com>
Cc: OFIWG Mailing list <ofiwg at lists.openfabrics.org>
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:


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 <jithin.jose at intel.com> _______________________________________________
ofiwg mailing list
ofiwg at lists.openfabrics.org

More information about the ofiwg mailing list