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" writes:
> >
> > Thanks for looking into this bug. neovim-qt now builds succes
On Fri, Jun 02, 2017 at 05:39:34PM -0400, Aaron M. Ucko wrote:
> "Aaron M. Ucko" 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?p
notfixed 845685 0.2.7-1
found 845685 0.2.7-1
thanks
"Aaron M. Ucko" 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=kfre
On Thu, Dec 15, 2016 at 11:03:40PM -0500, Aaron M. Ucko wrote:
> James McCoy writes:
>
> > As far as I can tell, what's happening is the async network connection
> > that's started by the connectToNeovim call has already errored out by
> > the time the onError SPY is created. The test then times
James McCoy writes:
> As far as I can tell, what's happening is the async network connection
> that's started by the connectToNeovim call has already errored out by
> the time the onError SPY is created. The test then times out waiting
> for the error to occur.
That's an unfortunate design. Pe
On Fri, Nov 25, 2016 at 03:24:23PM -0500, Aaron M. Ucko wrote:
> The kFreeBSD build of neovim-qt failed:
>
> Start 2: tst_neovimconnector
>2/12 Test #2: tst_neovimconnector ..***Failed 15.12 sec
> * Start testing of NeovimQt::Test *
> Config: Using Q
Source: neovim-qt
Version: 0.2.4-1
Severity: important
Justification: fails to build from source
The kFreeBSD build of neovim-qt failed:
Start 2: tst_neovimconnector
2/12 Test #2: tst_neovimconnector ..***Failed 15.12 sec
* Start testing of NeovimQt::Test
7 matches
Mail list logo
