On Mi, 24 Feb 2016, Christian Brabandt wrote: > On Mi, 24 Feb 2016, Ken Takata wrote: > > > Hi, > > > > 2016/2/25 Thu 5:56:17 UTC+9 Bram Moolenaar wrote: > > > Christian - > > > > > > I included the appveyour changes, it appears to work. Thanks! > > > > > > It's very slow. I notice a lot of "Vim: Warning: Output is not to a > > > terminal" messages. These cause a sleep of two seconds, that that would > > > explain why running tests with the console version is slow. Any idea > > > how we can fix that? Maybe the batch script is not run in a console, we > > > would need to start one first? Or perhaps it's because AppVeyor > > > redirects the output. > > > > I think AppVeyor redirects the output in order to output them to the Web. > > I don't know how to avoid it. > > That's what I think as well. I'll ask support about it, to make sure.
http://help.appveyor.com/discussions/questions/2125-output-of-testjobs-is-no-real-console I don't think there is a way around. Therefor we can disable the console test and run only the gvim test. A daily console test is run for the vim-win32-installer anyhow (and there it does not matter how long it takes). Best, Christian -- Was das Glück betrifft, so haben weder Erfahrung noch Beobachtung in mir den Eindruck erweckt, daß Gläubige im Durchschnitt glücklicher oder unglücklicher seien als Glaubenslose. -- Bertrand A. W. Russell -- -- 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]. For more options, visit https://groups.google.com/d/optout.
