Christian Brabandt wrote:

> >> > > On Do, 18 Feb 2016, Bram Moolenaar wrote:
> >> > >
> >> > > > Christian Brabandt wrote:
> >> > > > > On Mi, 17 Feb 2016, Bram Moolenaar wrote:
> >> > > > >
> >> > > > > > Thanks.  I think we should also build a console version.  Since 
> >> > > > > > testing
> >> > > > > > appears to the take bulk of the time we can run the tests once 
> >> > > > > > with
> >> > > > > > HUGE-console features.  So perhaps we can build TINY-console 
> >> > > > > > with MSVC
> >> > > > > > and HUGE-console with MingW and then run the tests with the MingW
> >> > > > > > binary?  That way we cover more rows & columns in the build & 
> >> > > > > > test
> >> > > > > > matrix.
> >> > > > >
> >> > > > > Well, a console version is build for MSVC, since that appears to 
> >> > > > > build
> >> > > > > faster than MingW. Testing happens with the gvim.exe build from 
> >> > > > > MSVC,
> >> > > > > because first of all, the test I tried with MingW did stall on 
> >> > > > > test47
> >> > > > > and second of all, last time I checked with the nightly windows 
> >> > > > > builds,
> >> > > > > the gui version test was a lot faster than the console test.
> >> > > >
> >> > > > Running the tests in the console is different from running them in 
> >> > > > the
> >> > > > GUI, I think we should run both.
> >> > >
> >> > > Okay, we can do this. Will take longer however.
> >> >
> >> > I'm glad you are taking the time to make this work.  Pity it's not that
> >> > easy.  I see the current version still fails in some ways it would not
> >> > fail when run locally.
> >> 
> >> Yes, I saw some test failures for the console version. Attached patch
> >> appveyor_test_fixes.diff fixes those warnings (basically by making 
> >> sure,
> >> that VIMRUNTIME is defined) and disables 2 tests, for which I couldn't
> >> find out, why they failed.
> >> Also, this patch fixes a warning about an uninitialized variable in
> >> f_tan()
> > 
> > I don't think using "set" works with nmake:
> > 
> > set VIMRUNTIME=..\..\runtime && $(VIMPROG) -u NONE -U NONE -S 
> > runtest.vim $*.vim
> > 
> > I don't understand why you need this, Vim should be able to find the
> > runtime files relative to the executable.
> 
> I don't either exactly and I cannot reproduce the problems locally, so I 
> was toying
> around appveyor and find a way to fix it. The original problem can be 
> seen here:
> 
> https://ci.appveyor.com/project/chrisbra/vim-ch0ci/build/56/job/tvp5gjh3kxttotja#L4647
> 
>  From test_quickfix.vim:
> Found errors in Test_helpgrep():
> Caught exception in Test_helpgrep(): Vim(helpgrep):E480: No match: 
> quickfix @ function Test_helpgrep, line 1
> 
>  From test_syntax.vim:
> Found errors in Test_syn_iskeyword():
> Caught exception in Test_syn_iskeyword(): Vim(source):E484: Can't open 
> file C:/projects/vim-ch0ci/src/testdir\syntax\syntax.vim @ function 
> Test_syn_iskeyword, line 8
> 
>  From test_alot.vim:
> Found errors in Test_load_menu():
> function Test_load_menu line 4: 'error while loading menus: 
> Vim(source):E484: Can''t open file 
> C:/projects/vim-ch0ci/src/testdir/menu.vim'
> TEST FAILURE
> NMAKE : fatal error U1077: 'if' : return code '0x1'
> Stop.
> Command exited with code 2
> 
> Which looks like, Vimruntime isn't set or empty or something. An 
> alternative solution would be to
> set vimruntime in the testfiles, that failed. I'll send a patch later.

The output of :version should tell you if there is a fall-back for
$VIMRUNTIME.  If it's not set, then check the Makefile, in Make_mvc.mak
it's done around line 1323.  However, the default is empty.

It should work to find the runtime files relative to the binary.  This
happens in vim_getenv(), around line 4320 in misc1.c.  No idea why this
would not work in this setup.


-- 
LAUNCELOT: I am, sir. I am a Knight of King Arthur.
FATHER:    'Mm ... very nice castle, Camelot ... very good pig country....
                 "Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD

 /// 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].
For more options, visit https://groups.google.com/d/optout.

Raspunde prin e-mail lui