Hi James, Am Mon, Dec 30, 2024 at 10:25:38AM -0500, schrieb James McCoy: > I'm working on bisecting the Vim change which broke the test to see if > anything needs to be changed on the Vim side, but I'm filing this in > case YCM can be fixed.
Thanks for looking into this and reporting it to vim-ycm upstream! That said, I am not quite sure how to proceed now… this seems not like an issue that deserves to block testing migration for vim, so do you think vim upstream is going to deal with this some way or another soon or is that going to take a while if ever? vim-ycm upstream isn't usually supporting varying versions and doubly so in its tests, so I presume they will more or less wait until an affected vim reaches their CI which might or might not be a long while. I am happy to look into getting 'my' tests to pass with old/new vim if that helps/unblocks us in the meantime. Best regards David Kalnischkies
signature.asc
Description: PGP signature
