Control: forwarded -1 https://github.com/equalsraf/neovim-qt/issues/289
On Fri, Jun 02, 2017 at 07:27:36PM -0400, James McCoy wrote: > On Fri, Jun 02, 2017 at 05:39:34PM -0400, Aaron M. Ucko wrote: > > "Aaron M. Ucko" <[email protected]> writes: > > > > Thanks for looking into this bug. neovim-qt now builds successfully on > > kfreebsd-amd64, but still fails on kfreebsd-i386, with nearly the same > > error; per > > https://buildd.debian.org/status/fetch.php?pkg=neovim-qt&arch=kfreebsd-i386&ver=0.2.7-1&stamp=1496290825&raw=0 > > the only difference is that > > > > > FAIL! : NeovimQt::Test::connectToNeovimTCP() 'SPYWAIT(onError)' > > > returned FALSE. () > > > Loc: [/«PKGBUILDDIR»/test/tst_neovimconnector.cpp(62)] > > > > has changed to > > > > FAIL! : NeovimQt::Test::connectToNeovimTCP() Compared values are not > > the same > > Loc: [/«PKGBUILDDIR»/test/tst_neovimconnector.cpp(65)] > > Yeah, this is a separate failure. I'll look into it. Full details on my investigation are in the upstream bug report. The short version is, it seems like Qt's non-blocking socket handling isn't reacting to EINPROGRESS properly all the time on kFreeBSD. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
