Stucki wrote:
> Am 01.09.2018 um 15:30 schrieb Bram Moolenaar:> > ... the timeouts
> longer?
> >
> > Which test is that? Ideally we would have some way of measuring how
> > slow the machine is and adjusting to that. Or we can just increase
> > the
> > timeout. That is not a good idea when it's supposed to timeout, so we
> > need to know what to change.
> The test is 'test_quotestar.vim' and seems to ask for the X-Buffers.
> I should have mentioned, all happened on a virtually small debian
> 'workstation' running in an vmware-cluster for tests.
> ------------------------------- output was -----------------------------
> >From test_quotestar.vim:
> Found errors in Test_quotestar():
> First run:
> Caught exception in Test_quotestar(): WaitFor() timed out after 5000
> msec @ function
> RunTheTest[40]..Test_quotestar[11]..Do_test_quotestar_for_x11[56]..WaitFor,
> line 4
> Second run:
> Caught exception in Test_quotestar(): WaitFor() timed out after 5000
> msec @ function
> RunTheTest[40]..Test_quotestar[11]..Do_test_quotestar_for_x11[56]..WaitFor,
> line 4
> TEST FAILURE
> ------------------------------------------------------------------------
Although it says that it timed out, it may actually have failed.
It uses a selection of 250 Kbyte, it's possible that your machine cannot
handle that.
Is there a way we can detect this system is "small"? Then we could skip
this part of the test.
> Testing the buffers from remote to my display with 'xclip' works
> perfectly without undue delays.
> BUT as I found out today, my problem seems to be, that X11 may be broken
> by missing some dependencies(?). The GUI (auto) was ignored but the test
> still is tried. May be the test is not skipped, because I configured
> with --with-x(?) or is there 'with x but without GUI'?
> >> Another test fails, seemingly because there is no
> >> textual representation of my passwd entry. The machine
> >> ...
> >> 'getent passwd $USER' still works, but with the old
> >> 'grep $USER /etc/passwd' nobody will be seen.
> >> ...
> > What is the log output for this (in src/testdir/messages)?
> ------------------------------- output was
> -----------------------------From test_cmdline.vim:
> Found errors in Test_cmdline_complete_user_names():
> function RunTheTest[40]..Test_cmdline_complete_user_names line 8:
> Pattern '^"e \\~.*\\<stucki\\>' does not match '"e ~salt saned sddm snmp
> speech-dispatcher sshd sssd statd sync sys systemd-bus-proxy
> systemd-network systemd-resolve systemd-timesync'
> TEST FAILURE
> Makefile:41: recipe for target 'report' failed
> make[1]: *** [report] Error 1
> make[1]: Leaving directory '/home/stucki/GIT/vim/src/testdir'
> Makefile:2083: recipe for target 'scripttests' failed
> make: *** [scripttests] Error 2
> ------------------------------------------------------------------------
>
> If I then add a line "stucki:*:####:####:c v. Stuckrad:/home/stucki"
> (with #### the correct numbers of course) to '/etc/passwd' and rerun
> with 'make test' all tests pass. As I mentioned; 'getent passwd stucki'
> shows the correct line in all cases. 'sssd' seems to be some modern
> expansion of the name service switch(ing) services, which allows e.g.
> laptops to cache logins from the last connection for a while to be
> abroad without network and continue to login locally.
If you type the command:
:e ~s<Tab>
Do you also see it fail? Then the test is successful :-).
Not sure if we can fix Vim.
--
hundred-and-one symptoms of being an internet addict:
16. You step out of your room and realize that your parents have moved and
you don't have a clue when it happened.
/// 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.
