Your message dated Mon, 19 Mar 2018 22:38:19 -0400
with message-id <[email protected]>
and subject line Re: Bug#863992: neovim-qt: FTBFS on mipsel: tst_shell neovim
crash
has caused the Debian Bug report #863992,
regarding neovim-qt: FTBFS on mipsel: tst_shell neovim crash
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
863992: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863992
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: neovim-qt
Version: 0.2.7-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
The experimental mipsel build of neovim-qt failed, as detailed in
https://buildd.debian.org/status/fetch.php?pkg=neovim-qt&arch=mipsel&ver=0.2.7-1&stamp=1496289160&raw=0
In particular, I observe
7/12 Test #7: tst_shell ........................***Failed 16.27 sec
[...]
PASS : NeovimQt::Test::uiStart()
QWARN : NeovimQt::Test::startVarsShellWidget() Neovim fatal error "The
Neovim process has crashed"
Could you please take a look?
Thanks!
--
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/[email protected]
--- End Message ---
--- Begin Message ---
On Sun, Jun 25, 2017 at 11:08:44PM -0400, James McCoy wrote:
> Control: severity -1 important
>
> On Fri, Jun 02, 2017 at 05:42:16PM -0400, Aaron M. Ucko wrote:
> > The experimental mipsel build of neovim-qt failed, as detailed in
> > https://buildd.debian.org/status/fetch.php?pkg=neovim-qt&arch=mipsel&ver=0.2.7-1&stamp=1496289160&raw=0
> > In particular, I observe
> >
> > 7/12 Test #7: tst_shell ........................***Failed 16.27 sec
> > [...]
> > PASS : NeovimQt::Test::uiStart()
> > QWARN : NeovimQt::Test::startVarsShellWidget() Neovim fatal error "The
> > Neovim process has crashed"
> >
> > Could you please take a look?
>
> I wasn't able to reproduce this manually on the porterbox, nor did the
> latest upload to unstable reproduce the problem. I do notice that the
> experimental build which failed was using the aspucd resolver. That
> tends to be overly aggressive on choosing packages from experimental to
> install, rather than preferring sid.
This appears to have been a problem with jemalloc (c.f., #843926). I
stopped building neovim against jemalloc for now, so that fixes the
issue.
Cheers,
--
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
--- End Message ---
