On Fri, Oct 26, 2018 at 03:30:54PM +0200, Helmut Grohne wrote:
> neovim fails to build from source in unstable.
>
> | [ ERROR ] 6 errors, listed below:
> | [ ERROR ] test/functional/helpers.lua @ 743: after_each
> | test/helpers.lua:289: crash detected (see above)
> |
> | stack traceback:
> | test/helpers.lua:289: in function 'check_cores'
> | test/functional/helpers.lua:748: in function
> <test/functional/helpers.lua:743>
I haven't seen these on the buidds or locally. The only issue I've been
seeing, aside from some flaky tests, I've filed upstream[0]:
[ RUN ] mbyte utf_char2bytes: FAIL
test/unit/helpers.lua:731: (string) '
not enough memory'
stack traceback:
test/unit/helpers.lua:747: in function 'itp_parent'
test/unit/helpers.lua:774: in function <test/unit/helpers.lua:764>
[0]: https://github.com/neovim/neovim/issues/9212
> Looking to reproducible builds, the failure pattern looks quite random:
>
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/neovim.html
I'm not actually sure what's happening in the most recent builds there.
I don't see any explicit error output, just the testing stopping earlier
than it should.
The armhf & ppc64el buildd failures I can't reproduce on the
porterboxes, although the latter is likely another flaky test.
> However, in local builds for unstable/amd64 in sbuild, I didn't get a
> single successful build.
If it's not any of the mentioned failures, then some more information
would be useful, as I have quite the opposite behavior locally.
Cheers,
--
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
