Re: Bug#852962: ycmd FTBFS on mipsel: test failures
Christoph Biedl <[email protected]>
| Newsgroups | gmane.linux.debian.devel.release,gmane.linux.debian.ports.mips |
|---|---|
| Message-ID | <[email protected]> |
James Cowgill wrote...
> On Thu, 1 Jun 2017 00:15:28 +0200 Christoph Biedl
> > Did so, but failed to reproduce the issue on the mipsel porter box.
> > However, the bug seems to manifest when building in a qemu-static
> > chroot. In that scenario however, diagnostic tools like strace
> > fail.
> >
> > Updates will follow as I get them.
>
> I've tried this on various mips hardware and I can only seems to fail on
> Loongsons (where is reliably fails 100% of the time). Blacklisting it on
> those machines could be an option given how close to the release we are.
Thanks for looking into this, James. Personally, if such a blacklisting
was acceptable for the release team (Cc:'ed), I was happy to spend the
remaining time on other issues in stretch. Since I still haven't figured
out what actually goes wrong during the test suite, I'd just like to
avoid this package (and its reverse dependencies) fall out of stretch.
Christoph
signature.asc
(application/pgp-signature, 819 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCgAGBQJZNZiSAAoJEMQsWOtZFJL9f8UP+wbhWrROKy3tdAxZ+f1edX/d /WmkdsWpqBnuyFtgaDqp8KhQHsXLD2Fc3JcIgiJhM2vC6sojWmW6RFQTcBMQQ/TI kxXtJ+m4EkGJO1LFyc6NBCzFpfKTLgNTryY56oQjvQOdRJsqE07Lgr6DC15N+Qru ko1ygAMemAr+z4uJZMY0Dl4J7etaVm9FwJE7fn/iK6zu4AR69rnDXqnlXfsjBK+a sKZSYiULVzW1CM0pu/AjlXtTeoV/873bxWcxb/aQrJSZP03mksyZNihjNdXHg5nf YnInrJP9GecQisO5OvjrvUSFb+zXzRsZkUjqan6EWWUiZ2gsZr6qd+qPxnyUJSa6 BBPEl5sv48SE7vlSpCraDHoMqBWp+NtRaPSYqdlnkIn8+nrTrVVgC7VTUxgWiVRv VvrKzdcW1VE5rC95slJ//CMIsKy9Hd7id2Z05phfe6AFlIFLTQyIaTbxDR+qu0WB XDLKwU/xllFhLdw+OSFsRw2KeWbHIfZqivHyWAYDoRYExi0lnk0hVD/VNng3z3/v 9DVt7br6s/+sz97g0nWBfwa3gI/gk67dGsDOFOysFab++BTR3HfrKxir18GU9FHC uzKRG1VTm9RPczPwg+Huzrdmjc8l/WRhjggSZi680ufOV5cpdEl3jKDjMRUVZ2l/ bWMl72M+gyJfTbIHJy++ =jXnM -----END PGP SIGNATURE-----