Control: severity -1 serious
On Tue, 28 Jul 2026 07:18:44 -0400 James McCoy <[email protected]> wrote:
Package: vim-youcompleteme
Version: 0+20240827+gitb6e8c64+ds-8
Severity: important
The completion.test.vim, completion_info.test.vim, and
completion_noresolve.test.vim autopkgtests all fail like below:
Found errors in Test_Select_Next_Previous_InsertModeMapping(). Retrying.
command line..script
/tmp/autopkgtest-lxc.tg7g_8lw/downtmp/build.1jz/src/test/lib/run_test.vim[387]..function
RunTheTest[68]..Test_Select_Next_Previous_InsertModeMapping[52]..FeedAndCheckMain[2]..Check2[2]..CheckCurrentLine
line 1: Expected ' foo.c' but got ' foo.'
command line..script
/tmp/autopkgtest-lxc.tg7g_8lw/downtmp/build.1jz/src/test/lib/run_test.vim[387]..function
RunTheTest[68]..Test_Select_Next_Previous_InsertModeMapping[52]..FeedAndCheckMain[2]..Check3[2]..CheckCurrentLine
line 1: Expected ' foo.x' but got ' foo.'
command line..script
/tmp/autopkgtest-lxc.tg7g_8lw/downtmp/build.1jz/src/test/lib/run_test.vim[387]..function
RunTheTest[68]..Test_Select_Next_Previous_InsertModeMapping[52]..FeedAndCheckMain[2]..Check4[1]..CheckCurrentLine
line 1: Expected ' foo.a' but got ' fooa'
I haven't had time yet to try and bisect which patch changed the
behavior.
This is already in the archive and blocking vim from migrating to testing, thus
raising the severity to RC.
Cheers,
Emilio
