Elimar Riesebieter wrote:
> * Christian Brabandt <[email protected]> [2019-07-24 19:33 +0200]: > > > Can you share the actual failed screendump file? > > > > > Am 24.07.2019 um 15:27 schrieb Elimar Riesebieter <[email protected]>: > > > > > > * Bram Moolenaar <[email protected]> [2019-07-24 15:00 +0200]: > > > > > >> > > >> Elimar Riesebieter wrote: > > >> > > >>> I get test failures as follows: > > >>> > > >>> Failures: > > >>> From test_diffmode.vim: > > >>> Found errors in Test_diff_screen(): > > >>> Run 1: > > >>> function > > >>> RunTheTest[40]..Test_diff_screen[95]..VerifyBoth[4]..VerifyScreenDump > > >>> line 55: external: See dump file difference: call > > >>> term_dumpdiff("testdir/failed/Test_diff_13.dump", > > >>> "testdir/dumps/Test_diff_13.dump"); difference in line 1: > > >>> "|-+0#0000e05#a8a8a8255| > > > >>> +0#0000000#ffffff0@34||+1&&|-+0#0000e05#a8a8a8255| | > > >>> +0#0000000#ffffff0@34"; difference in line 20: "|"+0&&|X|f|i|l|e|2|"| > > >>> |0|L|,| |0|C| @59" > > >> > > >> [...] > > >> > > >>> Flaky test failed too often, giving up > > >>> :r > > >>> > > >>> The failures are different in different attempts. Building on i386 > > >>> and amd64 runs fine, > > >> > > >> Any idea why it fails? Could it be an actual failure in the diff code? > > >> Might be related to byte order perhaps. > > >> I can't reproduce, thus it's hard for me to try fixing it. > > > > > > Well 8.1.1714 built fine. But there was no change in > > > test_diffmode.vim... I don't have an overview which files in runtime > > > changed since 8.1.1714. > > It seems that v8.1.1724 is the first tag where test_diffmode.vim > fails. That didn't change functionality, only timing. > Please find attached screendumps. > Thanks for investigation The first screendump is wrong. But from the others I can see that there is something different about how commands are interpreted. E.g. for Test_diff_15.dump it did not get the "set" command to change the diff options. In Test_diff_16.dump it did get the next command, thus it looks like it completely dropped the set command. Is this build without the GUI feature? Then the value for BREAKCHECK_SKIP jumped from 32 to 1000. You can try if using a lower value indeed makes it work again. That's not a solution, but good to check if this changes the results. For me it still works even when I set BREAKCHECK_SKIP to 10000. -- "The future's already arrived - it's just not evenly distributed yet." -- William Gibson /// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org /// \\\ help me help AIDS victims -- http://ICCF-Holland.org /// -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/201907252104.x6PL4ReU021386%40masaka.moolenaar.net.
