#1092414 neovim: FTBFS: make[1]: *** [debian/rules:129: override_dh_auto_test-arch] Error 1

Package:
src:neovim
Source:
src:neovim
Submitter:
Lucas Nussbaum
Date:
2025-05-04 21:36:01 UTC
Severity:
normal
Tags:
#1092414#5
Date:
2025-01-07 19:51:45 UTC
From:
To:
Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
The full build log is available from:
http://qa-logs.debian.net/2025/01/06/neovim_0.9.5-10_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20250106;users=lucas@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20250106&fusertaguser=lucas@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.

#1092414#12
Date:
2025-01-14 01:20:52 UTC
From:
To:
Control: severity -1 important

This looks like typical flakiness that I see in the neovim tests.
Downgrading the severity.

Attached build passes, but there's not much different.

Cheers,

#1092414#19
Date:
2025-05-04 21:33:55 UTC
From:
To:
Hi James,
in the reproduce.debian.net logs, in these tests:

Failures:
	From test_options.vim:
	Found errors in Test_shortmess_F3():
	command line..script /build/reproducible-path/neovim-0.10.4/test/old/testdir/runtest.vim[543]..function RunTheTest[55]..Test_shortmess_F3 line 19: Expected ['bar'] but got ['foo']
	command line..script /build/reproducible-path/neovim-0.10.4/test/old/testdir/runtest.vim[543]..function RunTheTest[55]..Test_shortmess_F3 line 29: Expected ['baz'] but got ['foo']
----

FAILED   1 test, listed below:
FAILED   test/functional/terminal/edit_spec.lua @ 38: :edit term://* runs TermOpen early enough to set buffer-local 'scrollback'
test/functional/terminal/edit_spec.lua:67: Row 1 did not match.
Expected:
  |*96: foobar          |
  |                    |
  |^[Process exited 0]  |
  |                    |
Actual:
  |*36: foobar          |
  |                    |
  |^[Process exited 0]  |
  |                    |

To print the expect() call that would assert the current screen state, use
screen:snapshot_util(). In case of non-deterministic failures, use
screen:redraw_debug() to show all intermediate screen states.

Snapshot:
screen:expect({
  grid = [[
    36: foobar          |
                        |
    ^[Process exited 0]  |
                        |
  ]]
})

stack traceback:
	test/functional/ui/screen.lua:850: in function '_wait'
	test/functional/ui/screen.lua:526: in function 'expect'
	test/functional/terminal/edit_spec.lua:67: in function <test/functional/terminal/edit_spec.lua:38>
--- FAILED 1 test, listed below: FAILED test/functional/ui/highlight_spec.lua @ 1350: CursorColumn highlight is updated if cursor is moved from timer test/functional/ui/highlight_spec.lua:1362: Row 1 did not match. Expected: |*aaaa{21:a} | |*bbbb{21:b} | |*cccc{21:c} | |*dddd^d | |{1:~ }| |{1:~ }| |{1:~ }| | | Actual: |*^aaaaa | |*{21:b}bbbb | |*{21:c}cccc | |*{21:d}dddd | |{1:~ }| |{1:~ }| |{1:~ }| | | To print the expect() call that would assert the current screen state, use screen:snapshot_util(). In case of non-deterministic failures, use screen:redraw_debug() to show all intermediate screen states. Snapshot: screen:expect({ grid = [[ ^aaaaa | {21:b}bbbb | {21:c}cccc | {21:d}dddd | {1:~ }|*3 | ]] }) stack traceback: test/functional/ui/screen.lua:850: in function '_wait' test/functional/ui/screen.lua:526: in function 'expect' test/functional/ui/highlight_spec.lua:1362: in function <test/functional/ui/highlight_spec.lua:1350> For the tests which fail in `_wait`, maybe the timeouts could be increased. Thanks, Chris