[ofiwg] sockets fabtests failure in testing for 1.4.0 release

[Hefty, Sean]

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.

- Sean


> -----Original Message-----
> From: Jeff Squyres (jsquyres) [mailto:jsquyres at cisco.com]
> Sent: Friday, October 28, 2016 12:22 PM
> To: Hefty, Sean <sean.hefty at intel.com>
> Cc: OFIWG Mailing list <ofiwg at lists.openfabrics.org>
> Subject: Re: sockets fabtests failure in testing for 1.4.0 release
> 
> I notice that there are several other providers who have not done this
> test.  According to https://github.com/ofiwg/libfabric/issues/2405, we
> still need the following to run this test:
> 
> - MXM
> - UDP
> - Verbs
> 
> 
> 
> > On Oct 28, 2016, at 3:17 PM, Hefty, Sean <sean.hefty at intel.com>
> wrote:
> >
> >> I'm seeing a problem in a specific test:
> >>
> >> - Build and install libfabric 1.3.0
> >> - Build and install fabtests 1.3.0 against the installed libfabric
> >> 1.3.0
> >> - Remove libfabric 1.3.0
> >> - Build and install libfabric 1.4.0 in its place
> >> - Run fabtests
> >>
> >> Running the simple loopback fabtests/sockets, I get 2 failures (see
> >> below).
> >
> > I ran a slightly different test, and I see the same 2 failures.  In
> my case I built and ran 1.4, then replaced fabtests with v1.2 (what I
> had that was convenient).
> >
> > I'll investigate more.
> >
> > - Sean
> 
> 
> --
> Jeff Squyres
> jsquyres at cisco.com
> For corporate legal information go to:
> http://www.cisco.com/web/about/doing_business/legal/cri/