Fix for the CI asan test failure due to a memory leak

[Yegappan Lakshmanan]

Hi all,

The CI ASAN test is currently failing due to a memory leak.  The fix for
this is in the https://github.com/vim/vim/pull/12948 PR.

Regards,
Yegappan

-- 
-- 
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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/CAAW7x7mpzffs%3Dd%3DCTqVb7bhpBu0B%3Dqa9ouhSUaMO2ULjbfyMSQ%40mail.gmail.com.

Re: Surprising test failure after rebasing PR

[Yegappan Lakshmanan]

Hi,

On Mon, Aug 14, 2023 at 6:39 PM Ernie Rael  wrote:
>
> Bunch of failures, all of them
>
> Set up snd-dummy
> E: Package 'linux-modules-extra-5.15.0-1042-azure' has no installation 
> candidate
>
> I see this after rebasing and pushing two PR's.
>
> Is there something I need to do?
>

No.  We started seeing these failures for the past few days.

Regards,
Yegappan

-- 
-- 
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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/CAAW7x7kyUZUvQW42jDDV%3DT0Q%3D6Vz9kHLGr4-T5K_TvtDgp263A%40mail.gmail.com.

Surprising test failure after rebasing PR

[Ernie Rael]

Bunch of failures, all of them

   Set up snd-dummy
   E: Package 'linux-modules-extra-5.15.0-1042-azure' has no
   installation candidate

I see this after rebasing and pushing two PR's.

Is there something I need to do?

-ernie

--
--
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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/ca7afb2c-5a0e-ea25-6b19-ce18fe84fb29%40raelity.com.

Re: Test Failure

[Elimar Riesebieter]

* Elimar Riesebieter  [2022-11-20 16:05 +0100]:

> Hi all,
> 
> Environment: Linux
> Terminal: tmux
> Compiler: clang-15
> Version: 9.0.0915
> 
> There is a test failure:
> Found errors in Test_autocmd_user_clear_group():
> Run 1, 15:38:56 - 15:39:01:
> command line..script 
> /source/vim/vim-9.0.0915/src/vim-motif/testdir/runtest.vim[515]..function 
> RunTheTest[52]..Test_autocmd_user_clear_group[18]..StopVimInTerminal[14]..WaitForAssert[2]..5_WaitForCommon[11]..47
>  line 1: Expected 'finished' but got 'running'

Seems to be fixed by 9.0.1087

Elimar
-- 
  Excellent day for drinking heavily.
  Spike the office water cooler;-)

-- 
-- 
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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/20221223180411.mnwy7j5amw3hzdir%40baumbart.home.lxtec.de.

Re: Test Failure

[Bram Moolenaar]

> * Bram Moolenaar  [2022-11-20 15:20 +]:
> 
> > > Environment: Linux
> > > Terminal: tmux
> > > Compiler: clang-15
> > > Version: 9.0.0915
> > > 
> > > There is a test failure:
> > > Found errors in Test_autocmd_user_clear_group():
> > > Run 1, 15:38:56 - 15:39:01:
> > > command line..script 
> > > /source/vim/vim-9.0.0915/src/vim-motif/testdir=
> > > /runtest.vim[515]..function 
> > > RunTheTest[52]..Test_autocmd_user_clear_group[1=
> > > 8]..StopVimInTerminal[14]..WaitForAssert[2]..5_WaitForCommon[11].. > > bda>47 line 1: Expected 'finished' but got 'running'
> > 
> > It does not fail for me in a similar setup, and CI also doesn't show
> > this failure.  Can you think of anything that matters?  I can't really
> > fix a test failure if I can't reproduce it.
> > 
> > You could try increasing the "50" argument of TermWait() in line 2239
> > and see if that makes a difference.
> 
> In which file?

In the test that fails, which is in src/testdir/test_autocmd.vim.
The line number is now 2394.

-- 
Ten bugs in the hand is better than one as yet undetected.

 /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net   \\\
///  \\\
\\\sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
 \\\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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/20221210102356.B169B1C1742%40moolenaar.net.

Re: Test Failure

[Elimar Riesebieter]

* Bram Moolenaar  [2022-11-20 15:20 +]:

> 
> > Environment: Linux
> > Terminal: tmux
> > Compiler: clang-15
> > Version: 9.0.0915
> > 
> > There is a test failure:
> > Found errors in Test_autocmd_user_clear_group():
> > Run 1, 15:38:56 - 15:39:01:
> > command line..script /source/vim/vim-9.0.0915/src/vim-motif/testdir=
> > /runtest.vim[515]..function RunTheTest[52]..Test_autocmd_user_clear_group[1=
> > 8]..StopVimInTerminal[14]..WaitForAssert[2]..5_WaitForCommon[11].. > bda>47 line 1: Expected 'finished' but got 'running'
> 
> It does not fail for me in a similar setup, and CI also doesn't show
> this failure.  Can you think of anything that matters?  I can't really
> fix a test failure if I can't reproduce it.
> 
> You could try increasing the "50" argument of TermWait() in line 2239
> and see if that makes a difference.

In which file?

Thanks
Elimar
-- 
  Learned men are the cisterns of knowledge,
  not the fountainheads ;-)

-- 
-- 
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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/20221210080051.iw4oz6nyu7hg2bsi%40baumbart.home.lxtec.de.

Re: Test Failure

[Bram Moolenaar]

> Environment: Linux
> Terminal: tmux
> Compiler: clang-15
> Version: 9.0.0915
> 
> There is a test failure:
> Found errors in Test_autocmd_user_clear_group():
> Run 1, 15:38:56 - 15:39:01:
> command line..script /source/vim/vim-9.0.0915/src/vim-motif/testdir=
> /runtest.vim[515]..function RunTheTest[52]..Test_autocmd_user_clear_group[1=
> 8]..StopVimInTerminal[14]..WaitForAssert[2]..5_WaitForCommon[11].. bda>47 line 1: Expected 'finished' but got 'running'

It does not fail for me in a similar setup, and CI also doesn't show
this failure.  Can you think of anything that matters?  I can't really
fix a test failure if I can't reproduce it.

You could try increasing the "50" argument of TermWait() in line 2239
and see if that makes a difference.

-- 
>From "know your smileys":
 |-(Contact lenses, but has lost them

 /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net   \\\
///  \\\
\\\sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
 \\\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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/20221120152028.0FFC91C12B2%40moolenaar.net.

Test Failure

[Elimar Riesebieter]

Hi all,

Environment: Linux
Terminal: tmux
Compiler: clang-15
Version: 9.0.0915

There is a test failure:
Found errors in Test_autocmd_user_clear_group():
Run 1, 15:38:56 - 15:39:01:
command line..script 
/source/vim/vim-9.0.0915/src/vim-motif/testdir/runtest.vim[515]..function 
RunTheTest[52]..Test_autocmd_user_clear_group[18]..StopVimInTerminal[14]..WaitForAssert[2]..5_WaitForCommon[11]..47
 line 1: Expected 'finished' but got 'running'

Thanks for investigation
Elimar

-- 
  The path to source is always uphill!
-unknown-

-- 
-- 
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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/20221120150518.cjvbewrxz2elv7ao%40baumbart.home.lxtec.de.

Re: Test Failure

[Bram Moolenaar]

Ernie Rael wrote:

>  It's been weeks since I've built vim, and considering the impending
>  release I built and ran tests this morning.
> 
>  -ernie
> 
>  On linux, gtk3, 8.2.5141
> 
> 
>  Executed:=C2=A0 5206 Tests
> =C2=A0Skipped:=C2=A0=C2=A0=C2=A0 62 Tests
> =C2=A0 FAILED:=C2=A0=C2=A0=C2=A0=C2=A0 1 Tests
> 
> 
>  Failures:
> =C2=A0=C2=A0 =C2=A0From test_startup.vim:
> =C2=A0=C2=A0 =C2=A0Found errors in Test_geometry():
> =C2=A0=C2=A0 =C2=A0command line..script
>  /ref/vim/src/testdir/runtest.vim[464]..function
>  RunTheTest[44]..Test_geometry line 30: Expected '43' but got '130'
> =C2=A0=C2=A0 =C2=A0command line..script
>  /ref/vim/src/testdir/runtest.vim[464]..function
>  RunTheTest[44]..Test_geometry line 31: Expected '[41, 43]' but got '[4=
> 1,
>  130]'
> >>> I have not seen this failure, not on CI and not on my own system.  I'm
> >>> just running all tests under valgrind (which takes a long time) and it
> >>> also doesn't fail then.
> >>>
> >>> It might depend on your window manager perhaps.
> >> I was unfamiliar with the -geometry option, there's a status bar across
> >> the top of the laptop. Guess the bar must be 130 pixels in height.
> > Possibly.  Still, the window manager should compensate for that.
> >
> > You could try changing "43" in Test_geometry() to 150.
> > Does that work, or does it then fail in another way?
> >
> Yes, it works fine with 150.
> 
> I asked for it to position at 43, it couldn't and it put it at 130.=20
> Isn't that compensation? (Not that I'm trying to defend the window manager)

OK, so the window manager uses an absolute position, but then pushes the
window down to avoid overlapping the status bar.  We can use 150 to
avoid that problem.

-- 
If you had to identify, in one word, the reason why the
human race has not achieved, and never will achieve, its
full potential, that word would be "meetings."

 /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net   \\\
///  \\\
\\\sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
 \\\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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/20220621133919.DCAF11C183E%40moolenaar.net.

Re: Test Failure

[Ernie Rael]

On 6/20/22 1:52 PM, Bram Moolenaar wrote:

Ernie Rael wrote:


It's been weeks since I've built vim, and considering the impending
release I built and ran tests this morning.

-ernie

On linux, gtk3, 8.2.5141


Executed:  5206 Tests
    Skipped:    62 Tests
     FAILED: 1 Tests


Failures:
       From test_startup.vim:
       Found errors in Test_geometry():
       command line..script
/ref/vim/src/testdir/runtest.vim[464]..function
RunTheTest[44]..Test_geometry line 30: Expected '43' but got '130'
       command line..script
/ref/vim/src/testdir/runtest.vim[464]..function
RunTheTest[44]..Test_geometry line 31: Expected '[41, 43]' but got '[41,
130]'

I have not seen this failure, not on CI and not on my own system.  I'm
just running all tests under valgrind (which takes a long time) and it
also doesn't fail then.

It might depend on your window manager perhaps.

I was unfamiliar with the -geometry option, there's a status bar across
the top of the laptop. Guess the bar must be 130 pixels in height.

Possibly.  Still, the window manager should compensate for that.

You could try changing "43" in Test_geometry() to 150.
Does that work, or does it then fail in another way?


Yes, it works fine with 150.

I asked for it to position at 43, it couldn't and it put it at 130. 
Isn't that compensation? (Not that I'm trying to defend the window manager)


-ernie

--
--
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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/5833366f-fed2-faac-cae4-e3ce3a9065ec%40raelity.com.

Re: Test Failure

[Bram Moolenaar]

Ernie Rael wrote:

> >> It's been weeks since I've built vim, and considering the impending
> >> release I built and ran tests this morning.
> >>
> >> -ernie
> >>
> >> On linux, gtk3, 8.2.5141
> >>
> >>
> >> Executed:  5206 Tests
> >>    Skipped:    62 Tests
> >>     FAILED: 1 Tests
> >>
> >>
> >> Failures:
> >>       From test_startup.vim:
> >>       Found errors in Test_geometry():
> >>       command line..script
> >> /ref/vim/src/testdir/runtest.vim[464]..function
> >> RunTheTest[44]..Test_geometry line 30: Expected '43' but got '130'
> >>       command line..script
> >> /ref/vim/src/testdir/runtest.vim[464]..function
> >> RunTheTest[44]..Test_geometry line 31: Expected '[41, 43]' but got '[41,
> >> 130]'
> > I have not seen this failure, not on CI and not on my own system.  I'm
> > just running all tests under valgrind (which takes a long time) and it
> > also doesn't fail then.
> >
> > It might depend on your window manager perhaps.
> 
> I was unfamiliar with the -geometry option, there's a status bar across 
> the top of the laptop. Guess the bar must be 130 pixels in height.

Possibly.  Still, the window manager should compensate for that.

You could try changing "43" in Test_geometry() to 150.
Does that work, or does it then fail in another way?

-- 
Never under any circumstances take a sleeping pill
and a laxative on the same night.

 /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net   \\\
///  \\\
\\\sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
 \\\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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/20220620205240.3EF731C055A%40moolenaar.net.

Re: Test Failure

[Ernie Rael]

On 6/20/22 10:45 AM, Bram Moolenaar wrote:

Ernie Rael wrote:


It's been weeks since I've built vim, and considering the impending
release I built and ran tests this morning.

-ernie

On linux, gtk3, 8.2.5141


Executed:  5206 Tests
   Skipped:    62 Tests
    FAILED: 1 Tests


Failures:
      From test_startup.vim:
      Found errors in Test_geometry():
      command line..script
/ref/vim/src/testdir/runtest.vim[464]..function
RunTheTest[44]..Test_geometry line 30: Expected '43' but got '130'
      command line..script
/ref/vim/src/testdir/runtest.vim[464]..function
RunTheTest[44]..Test_geometry line 31: Expected '[41, 43]' but got '[41,
130]'

I have not seen this failure, not on CI and not on my own system.  I'm
just running all tests under valgrind (which takes a long time) and it
also doesn't fail then.

It might depend on your window manager perhaps.


I was unfamiliar with the -geometry option, there's a status bar across 
the top of the laptop. Guess the bar must be 130 pixels in height.


-ernie





--
--
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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/8af696d2-968f-0c1c-ba16-d6ce82db25ea%40raelity.com.

Re: Test Failure

[Bram Moolenaar]

Ernie Rael wrote:

> It's been weeks since I've built vim, and considering the impending 
> release I built and ran tests this morning.
> 
> -ernie
> 
> On linux, gtk3, 8.2.5141
> 
> 
> Executed:  5206 Tests
>   Skipped:    62 Tests
>    FAILED: 1 Tests
> 
> 
> Failures:
>      From test_startup.vim:
>      Found errors in Test_geometry():
>      command line..script 
> /ref/vim/src/testdir/runtest.vim[464]..function 
> RunTheTest[44]..Test_geometry line 30: Expected '43' but got '130'
>      command line..script 
> /ref/vim/src/testdir/runtest.vim[464]..function 
> RunTheTest[44]..Test_geometry line 31: Expected '[41, 43]' but got '[41, 
> 130]'

I have not seen this failure, not on CI and not on my own system.  I'm
just running all tests under valgrind (which takes a long time) and it
also doesn't fail then.

It might depend on your window manager perhaps.

-- 
ALL:   A witch!  A witch!
WITCH: It's a fair cop.
ALL:   Burn her!  Burn her!  Let's make her into a ladder.
 "Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD

 /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net   \\\
///  \\\
\\\sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
 \\\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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/20220620174518.02F401C075E%40moolenaar.net.

Test Failure

[Ernie Rael]

It's been weeks since I've built vim, and considering the impending 
release I built and ran tests this morning.


-ernie

On linux, gtk3, 8.2.5141


Executed:  5206 Tests
 Skipped:    62 Tests
  FAILED: 1 Tests


Failures:
    From test_startup.vim:
    Found errors in Test_geometry():
    command line..script 
/ref/vim/src/testdir/runtest.vim[464]..function 
RunTheTest[44]..Test_geometry line 30: Expected '43' but got '130'
    command line..script 
/ref/vim/src/testdir/runtest.vim[464]..function 
RunTheTest[44]..Test_geometry line 31: Expected '[41, 43]' but got '[41, 
130]'


--
--
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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/cf04ee2c-09c8-1ed6-4860-1bd848e8cff1%40raelity.com.

Test_terminal_tmap test failure in CI

[Yegappan Lakshmanan]

Hi,

The Test_terminal_tmap() test fails occasionally in the Linux GUI CI action:

https://github.com/vim/vim/runs/5817654101?check_suite_focus=true

I am not able to reproduce this failure in a local setup. I don't know where
it fails in that test. Is anyone else able to reproduce this failure?

Thanks,
Yegappan

-- 
-- 
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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/CAAW7x7%3DXu_WA21HMcNO4vg_7zdjs%3DJmeR%3De7GwKJnTS%3DsiVJ1Q%40mail.gmail.com.

Re: Test failure building 8.2.4575

[Bram Moolenaar]

Elimar Riesebieter wrote:

> this failure appears on building 8.2.4575 gtk3 variant. The platform
> this time it is Linux-ppc32.
> 
> Failures:
> From test_messages.vim:
> Found errors in Test_fileinfo_after_echo():
> Run 1:
> command line..script /source/vim/vim-8.2.4575/src/vim-gtk3/testdir/=
> runtest.vim[456]..function RunTheTest[44]..Test_fileinfo_after_echo[18]..Ve=
> rifyScreenDump line 61: See dump file difference: call term_dumpdiff("testd=
> ir/failed/Test_fileinfo_after_echo.dump", "testdir/dumps/Test_fileinfo_afte=
> r_echo.dump"); difference in line 1: "> 

Test failure building 8.2.4575

[Elimar Riesebieter]

Hi all,

this failure appears on building 8.2.4575 gtk3 variant. The platform
this time it is Linux-ppc32.

Failures:
From test_messages.vim:
Found errors in Test_fileinfo_after_echo():
Run 1:
command line..script 
/source/vim/vim-8.2.4575/src/vim-gtk3/testdir/runtest.vim[456]..function 
RunTheTest[44]..Test_fileinfo_after_echo[18]..VerifyScreenDump line 61: See 
dump file difference: call 
term_dumpdiff("testdir/failed/Test_fileinfo_after_echo.dump", 
"testdir/dumps/Test_fileinfo_after_echo.dump"); difference in line 1: "> 

Re: Test Failure building 8.2.4575

[Bram Moolenaar]

Elimar Riesebieter wrote:

> Environment:
> Linux, tmux, clang-13, amd64
> 
> building 8.2.4575 gives me:
> 
> Failures:
> From test_vim9_script.vim:
> Found errors in Test_profile_with_lambda():
> Caught exception in Test_profile_with_lambda(): Vim(call):E484: Can't 
> open file Xdidprofile @ command line..script 
> /source/vim/vim-8.2.4574/src/vim-gtk3/testdir/runtest.vim[456]..function 
> RunTheTest[44]..Test_profile_with_lambda, line 53

Fixed with patch 8.2.4575.  Was a bit of a puzzle why this was failing.
Turns out there were three reasons.

-- 
God made the integers; all else is the work of Man.
-- Kronecker

 /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net   \\\
///  \\\
\\\sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
 \\\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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/20220315193402.01F661C42FC%40moolenaar.net.

Test Failure building 8.2.4575

[Elimar Riesebieter]

Hi all,

Environment:
Linux, tmux, clang-13, amd64

building 8.2.4575 gives me:

Failures:
From test_vim9_script.vim:
Found errors in Test_profile_with_lambda():
Caught exception in Test_profile_with_lambda(): Vim(call):E484: Can't 
open file Xdidprofile @ command line..script 
/source/vim/vim-8.2.4574/src/vim-gtk3/testdir/runtest.vim[456]..function 
RunTheTest[44]..Test_profile_with_lambda, line 53

Elimar
-- 
  355/113: Not the famous irrational number pi,
   but an incredible simulation!
-unknown

-- 
-- 
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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/20220315193024.usp2snqpkfbokx2g%40baumbart.home.lxtec.de.

Re: Test failure building 8.2.3567

[Elimar Riesebieter]

* Dominique Pellé  [2021-10-30 15:33 +0200]:

[...] 
> I tried building with all GUIs:
> >
> > gui  test outcome
> > ---  ---
> > noneTest SKIPPED (xim feature missing)
> > athena   Test FAILS
> > motifTest FAILS
> > gtk2 Test PASS
> > gtk3 Test PASS
> >
> > Maybe we need to skip the test with athena & motif, but it looks like
> > a workaround. I don't really know whether the test is wrong or whether it
> > shows a bug in Vim.
> >
> > I'll create a PR with an added `CheckFeature gui_gtk`.
> >
> > Dominique
> >
> 
> This PR should fix it: https://github.com/vim/vim/pull/9069

Yep, build runs fine ;-)

Elimar
-- 
  Alles, was viel bedacht wird, wird bedenklich!;-)
 Friedrich Nietzsche

-- 
-- 
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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/20211031045402.uwpmq6udspw4ztxi%40baumbart.home.lxtec.de.

Re: Test failure building 8.2.3567

[Dominique Pellé]

Dominique Pellé wrote:

Elimar Riesebieter wrote:
>
> > Hi all,
> >
> > build environment:
> > CC=clang13
> > tmux session
> > TERM=tmux-256color
> > compiling 8.2.3567
> >
> > Failures:
> > From test_edit.vim:
> > Found errors in Test_edit_CTRL_hat():
> > command line..script
> /source/vim/vim-8.2.3567/src/vim-athena/testdir/runtest.vim[450]..function
> RunTheTest[44]..Test_edit_CTRL_hat line 10: Expected 0 but got 2
>
> I can reproduce by building with:
>
> $ CC=clang-13 ./configure --with-features=huge --enable-gui=athena
> --enable-python3interp=yes
> $ make -j10
> $ make test_edit
> ...
> Found errors in Test_edit_CTRL_hat():
> command line..script
> /home/pel/sb/vim/src/testdir/runtest.vim[450]..function
> RunTheTest[44]..Test_edit_CTRL_hat line 10: Expected 0 but got 2
>
> tmux is not needed to reproduce. What's needed in the athena or motif gui
> (even if the test
> fails in the terminal).
>
> I tried building with all GUIs:
>
> gui  test outcome
> ---  ---
> noneTest SKIPPED (xim feature missing)
> athena   Test FAILS
> motifTest FAILS
> gtk2 Test PASS
> gtk3 Test PASS
>
> Maybe we need to skip the test with athena & motif, but it looks like
> a workaround. I don't really know whether the test is wrong or whether it
> shows a bug in Vim.
>
> I'll create a PR with an added `CheckFeature gui_gtk`.
>
> Dominique
>

This PR should fix it: https://github.com/vim/vim/pull/9069

-- 
-- 
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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/CAON-T_jFS-c88LJz%2BTB5Bj8_XudfCjA%3DiN%3DHo%3D4rtzGhrdVbcg%40mail.gmail.com.

Re: Test failure building 8.2.3567

[Dominique Pellé]

Elimar Riesebieter wrote:

> Hi all,
>
> build environment:
> CC=clang13
> tmux session
> TERM=tmux-256color
> compiling 8.2.3567
>
> Failures:
> From test_edit.vim:
> Found errors in Test_edit_CTRL_hat():
> command line..script
/source/vim/vim-8.2.3567/src/vim-athena/testdir/runtest.vim[450]..function
RunTheTest[44]..Test_edit_CTRL_hat line 10: Expected 0 but got 2

I can reproduce by building with:

$ CC=clang-13 ./configure --with-features=huge --enable-gui=athena
--enable-python3interp=yes
$ make -j10
$ make test_edit
...
Found errors in Test_edit_CTRL_hat():
command line..script
/home/pel/sb/vim/src/testdir/runtest.vim[450]..function
RunTheTest[44]..Test_edit_CTRL_hat line 10: Expected 0 but got 2

tmux is not needed to reproduce. What's needed in the athena or motif gui
(even if the test
fails in the terminal).

I tried building with all GUIs:

gui  test outcome
---  ---
noneTest SKIPPED (xim feature missing)
athena   Test FAILS
motifTest FAILS
gtk2 Test PASS
gtk3 Test PASS

Maybe we need to skip the test with athena & motif, but it looks like
a workaround. I don't really know whether the test is wrong or whether it
shows a bug in Vim.

I'll create a PR with an added `CheckFeature gui_gtk`.

Dominique

-- 
-- 
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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/CAON-T_hJvyfOVV_Xmd0HA%2BdGwmoeE%3D_FC4UUCX7RjovR-06jRA%40mail.gmail.com.

Test failure building 8.2.3567

[Elimar Riesebieter]

Hi all,

build environment:
CC=clang13
tmux session
TERM=tmux-256color
compiling 8.2.3567

Failures:
From test_edit.vim:
Found errors in Test_edit_CTRL_hat():
command line..script 
/source/vim/vim-8.2.3567/src/vim-athena/testdir/runtest.vim[450]..function 
RunTheTest[44]..Test_edit_CTRL_hat line 10: Expected 0 but got 2

Elimar
-- 
  Learned men are the cisterns of knowledge,
  not the fountainheads ;-)

-- 
-- 
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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/20211030122427.fwdbmdrkfvfid5nh%40baumbart.home.lxtec.de.

Re: Test failure building 8.2.3404

[Elimar Riesebieter]

* Dominique Pellé  [2021-09-05 22:48 +0200]:

> Bram Moolenaar  wrote:
> 
> > Elimar Riesebieter wrote:
> >
> > > Environment: amd64
> > > Shell: zsh
> > > Term: tmux session
> > > Compiler: clang-12
> > > LANG: C
> > >
> > > Hi all,
> > >
> > > Building 8.2.3404 gives me
> > >
> > > ###
> > > Failures:
> > > From test_signals.vim:
> > > Found errors in Test_deadly_signal_TERM():
> > > Run 1:
> > > command line..script 
> > > /source/vim/vim-8.2.3404/src/vim-nox/testdir/runtest.vim[486]..function 
> > > RunTheTest[44]..Test_deadly_signal_TERM line 35: Expected ['VimLeavePre 
> > > triggered', 'VimLeave triggered'] but got ['VimLeavePre triggered']
> > > Run 2:
> > > command line..script 
> > > /source/vim/vim-8.2.3404/src/vim-nox/testdir/runtest.vim[520]..function 
> > > RunTheTest[44]..Test_deadly_signal_TERM line 35: Expected ['VimLeavePre 
> > > triggered', 'VimLeave triggered'] but got ['VimLeavePre triggered']
> > > Run 3:
> > > command line..script 
> > > /source/vim/vim-8.2.3404/src/vim-nox/testdir/runtest.vim[520]..function 
> > > RunTheTest[44]..Test_deadly_signal_TERM line 35: Expected ['VimLeavePre 
> > > triggered', 'VimLeave triggered'] but got ['VimLeavePre triggered']
> > > Flaky test failed too often, giving up
> > >
> > > TEST FAILURE
> > > ###
> >
> > It's unrelated to the 8.2.3404 patch, with what patch did it start
> > failing?
> >
> > CI doesn't report this error.  Does the failure go away when you change
> > something in your setup?  e.g. not use tmux or use another shell.
> 
> This failure looks related or maybe similar to
> https://github.com/vim/vim/issues/7402
> 
> There it was found that building Vim with `-D_REENTRANT` fixes it.
> 
> Can you  confirm Elimar?

Indeed adding -D_REENTRANT to the CFLAGS (CPPFLAGS) fixes the issue.

Thanks
Elimar
-- 
  On the keyboard of life you have always
  to keep a finger at the escape key;-)

-- 
-- 
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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/20210906153211.x236ukyt634hnfiq%40baumbart.home.lxtec.de.

Re: Test failure building 8.2.3404

[Dominique Pellé]

Bram Moolenaar  wrote:

> Elimar Riesebieter wrote:
>
> > Environment: amd64
> > Shell: zsh
> > Term: tmux session
> > Compiler: clang-12
> > LANG: C
> >
> > Hi all,
> >
> > Building 8.2.3404 gives me
> >
> > ###
> > Failures:
> > From test_signals.vim:
> > Found errors in Test_deadly_signal_TERM():
> > Run 1:
> > command line..script 
> > /source/vim/vim-8.2.3404/src/vim-nox/testdir/runtest.vim[486]..function 
> > RunTheTest[44]..Test_deadly_signal_TERM line 35: Expected ['VimLeavePre 
> > triggered', 'VimLeave triggered'] but got ['VimLeavePre triggered']
> > Run 2:
> > command line..script 
> > /source/vim/vim-8.2.3404/src/vim-nox/testdir/runtest.vim[520]..function 
> > RunTheTest[44]..Test_deadly_signal_TERM line 35: Expected ['VimLeavePre 
> > triggered', 'VimLeave triggered'] but got ['VimLeavePre triggered']
> > Run 3:
> > command line..script 
> > /source/vim/vim-8.2.3404/src/vim-nox/testdir/runtest.vim[520]..function 
> > RunTheTest[44]..Test_deadly_signal_TERM line 35: Expected ['VimLeavePre 
> > triggered', 'VimLeave triggered'] but got ['VimLeavePre triggered']
> > Flaky test failed too often, giving up
> >
> > TEST FAILURE
> > ###
>
> It's unrelated to the 8.2.3404 patch, with what patch did it start
> failing?
>
> CI doesn't report this error.  Does the failure go away when you change
> something in your setup?  e.g. not use tmux or use another shell.

This failure looks related or maybe similar to
https://github.com/vim/vim/issues/7402

There it was found that building Vim with `-D_REENTRANT` fixes it.

Can you  confirm Elimar?

Regards
Dominique

-- 
-- 
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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/CAON-T_gCnW4DHciwmbBiQWqeKY_FBBFz1UG-B63MjgMs2m-Oig%40mail.gmail.com.

Re: Test failure building 8.2.3404

[Bram Moolenaar]

Elimar Riesebieter wrote:

> Environment: amd64
> Shell: zsh
> Term: tmux session
> Compiler: clang-12
> LANG: C
> 
> Hi all,
> 
> Building 8.2.3404 gives me
> 
> ###
> Failures:
> From test_signals.vim:
> Found errors in Test_deadly_signal_TERM():
> Run 1:
> command line..script 
> /source/vim/vim-8.2.3404/src/vim-nox/testdir/runtest.vim[486]..function 
> RunTheTest[44]..Test_deadly_signal_TERM line 35: Expected ['VimLeavePre 
> triggered', 'VimLeave triggered'] but got ['VimLeavePre triggered']
> Run 2:
> command line..script 
> /source/vim/vim-8.2.3404/src/vim-nox/testdir/runtest.vim[520]..function 
> RunTheTest[44]..Test_deadly_signal_TERM line 35: Expected ['VimLeavePre 
> triggered', 'VimLeave triggered'] but got ['VimLeavePre triggered']
> Run 3:
> command line..script 
> /source/vim/vim-8.2.3404/src/vim-nox/testdir/runtest.vim[520]..function 
> RunTheTest[44]..Test_deadly_signal_TERM line 35: Expected ['VimLeavePre 
> triggered', 'VimLeave triggered'] but got ['VimLeavePre triggered']
> Flaky test failed too often, giving up
> 
> TEST FAILURE
> ###

It's unrelated to the 8.2.3404 patch, with what patch did it start
failing?

CI doesn't report this error.  Does the failure go away when you change
something in your setup?  e.g. not use tmux or use another shell.

-- 
I used to be indecisive, now I'm not sure.

 /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net   \\\
///  \\\
\\\sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
 \\\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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/202109052022.185KMTkO1169302%40masaka.moolenaar.net.

Test failure building 8.2.3404

[Elimar Riesebieter]

Environment: amd64
Shell: zsh
Term: tmux session
Compiler: clang-12
LANG: C

Hi all,

Building 8.2.3404 gives me

###
Failures:
From test_signals.vim:
Found errors in Test_deadly_signal_TERM():
Run 1:
command line..script 
/source/vim/vim-8.2.3404/src/vim-nox/testdir/runtest.vim[486]..function 
RunTheTest[44]..Test_deadly_signal_TERM line 35: Expected ['VimLeavePre 
triggered', 'VimLeave triggered'] but got ['VimLeavePre triggered']
Run 2:
command line..script 
/source/vim/vim-8.2.3404/src/vim-nox/testdir/runtest.vim[520]..function 
RunTheTest[44]..Test_deadly_signal_TERM line 35: Expected ['VimLeavePre 
triggered', 'VimLeave triggered'] but got ['VimLeavePre triggered']
Run 3:
command line..script 
/source/vim/vim-8.2.3404/src/vim-nox/testdir/runtest.vim[520]..function 
RunTheTest[44]..Test_deadly_signal_TERM line 35: Expected ['VimLeavePre 
triggered', 'VimLeave triggered'] but got ['VimLeavePre triggered']
Flaky test failed too often, giving up

TEST FAILURE
###

Thanks for investigation
Elimar
-- 
  The path to source is always uphill!
-unknown-

-- 
-- 
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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/20210905194032.ndxpyuhnkdcnqw74%40baumbart.home.lxtec.de.

Re: Test failure building 8.2.3104

[Elimar Riesebieter]

* Christian Brabandt  [2021-07-05 09:43 +0200]:

> 
> On So, 04 Jul 2021, Bram Moolenaar wrote:
> 
> > 
> > Elimar Riesebieter wrote:
> > 
> > > Environment:
> > > amd64
> > > tmux
> > > clang-12
> > > 
> > > Failures:
> > > From test_vim9_builtin.vim:
> > > Found errors in Test_remote_foreground():
> > > command line..script 
> > > /source/vim/vim-8.2.3104/src/vim-gtk3/testdir/runtest.vim[473]..function 
> > > RunTheTest[44]..Test_remote_foreground line 5: Expected 'E241:' but got 
> > > 'E240: No connection to the X server': 
> > > remote_foreground("NonExistingServer")
> > 
> > I can't think of a recent change that could have caused this.
> > Perhaps it's a flaky test failure?
> 
> I suppose we need to have this change:
> 
> diff --git a/src/testdir/check.vim b/src/testdir/check.vim
> index d6bfe004a..97ab6e5cf 100644
> --- a/src/testdir/check.vim
> +++ b/src/testdir/check.vim
> @@ -209,6 +209,14 @@ func CheckNotAsan()
>endif
>  endfunc
> 
> +" Command to Check for environment variable
> +command -nargs=1 CheckEnv call CheckEnv()
> +func CheckEnv(name)
> +  if !exists('$' .. a:name)
> +throw 'Skipped: Environment variable ' .. a:name .. ' does not exists'
> +  endif
> +endfunc
> +
>  " Command to check for satisfying any of the conditions.
>  " e.g. CheckAnyOf Feature:bsd Feature:sun Linux
>  command -nargs=+ CheckAnyOf call CheckAnyOf()
> diff --git a/src/testdir/test_vim9_builtin.vim 
> b/src/testdir/test_vim9_builtin.vim
> index 38bd8271c..3a952ee79 100644
> --- a/src/testdir/test_vim9_builtin.vim
> +++ b/src/testdir/test_vim9_builtin.vim
> @@ -1416,6 +1416,7 @@ def Test_remote_foreground()
># remote_foreground() doesn't fail on MS-Windows
>CheckNotMSWindows
>CheckDefFailure(['remote_foreground(10)'], 'E1013: Argument 1: type 
> mismatch, expected string but got number')
> +  CheckEnv DISPLAY
>assert_fails('remote_foreground("NonExistingServer")', 'E241:')
>  enddef

This patch fixes the issue for me!

Thanks
Elimar
-- 
  Do you smell something burning or is it me?

-- 
-- 
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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/20210705093033.rrohw3imryatftvg%40toy.home.lxtec.de.

Re: Test failure building 8.2.3104

[Christian Brabandt]

On So, 04 Jul 2021, Bram Moolenaar wrote:

> 
> Elimar Riesebieter wrote:
> 
> > Environment:
> > amd64
> > tmux
> > clang-12
> > 
> > Failures:
> > From test_vim9_builtin.vim:
> > Found errors in Test_remote_foreground():
> > command line..script 
> > /source/vim/vim-8.2.3104/src/vim-gtk3/testdir/runtest.vim[473]..function 
> > RunTheTest[44]..Test_remote_foreground line 5: Expected 'E241:' but got 
> > 'E240: No connection to the X server': 
> > remote_foreground("NonExistingServer")
> 
> I can't think of a recent change that could have caused this.
> Perhaps it's a flaky test failure?

I suppose we need to have this change:

diff --git a/src/testdir/check.vim b/src/testdir/check.vim
index d6bfe004a..97ab6e5cf 100644
--- a/src/testdir/check.vim
+++ b/src/testdir/check.vim
@@ -209,6 +209,14 @@ func CheckNotAsan()
   endif
 endfunc

+" Command to Check for environment variable
+command -nargs=1 CheckEnv call CheckEnv()
+func CheckEnv(name)
+  if !exists('$' .. a:name)
+throw 'Skipped: Environment variable ' .. a:name .. ' does not exists'
+  endif
+endfunc
+
 " Command to check for satisfying any of the conditions.
 " e.g. CheckAnyOf Feature:bsd Feature:sun Linux
 command -nargs=+ CheckAnyOf call CheckAnyOf()
diff --git a/src/testdir/test_vim9_builtin.vim 
b/src/testdir/test_vim9_builtin.vim
index 38bd8271c..3a952ee79 100644
--- a/src/testdir/test_vim9_builtin.vim
+++ b/src/testdir/test_vim9_builtin.vim
@@ -1416,6 +1416,7 @@ def Test_remote_foreground()
   # remote_foreground() doesn't fail on MS-Windows
   CheckNotMSWindows
   CheckDefFailure(['remote_foreground(10)'], 'E1013: Argument 1: type 
mismatch, expected string but got number')
+  CheckEnv DISPLAY
   assert_fails('remote_foreground("NonExistingServer")', 'E241:')
 enddef


Best,
Christian
-- 
Elektrizität ist: Morgens mit Spannung aufstehen, mit Widerstand zur
Schule gehen, in allen Stunden gegen den Strom fließen, geladen nach
Hause kommen und dann noch vom Vater eine gewischt kriegen!

-- 
-- 
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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/20210705074307.GB283422%40256bit.org.

Re: Test failure building 8.2.3104

[Bram Moolenaar]

Elimar Riesebieter wrote:

> Environment:
> amd64
> tmux
> clang-12
> 
> Failures:
> From test_vim9_builtin.vim:
> Found errors in Test_remote_foreground():
> command line..script 
> /source/vim/vim-8.2.3104/src/vim-gtk3/testdir/runtest.vim[473]..function 
> RunTheTest[44]..Test_remote_foreground line 5: Expected 'E241:' but got 
> 'E240: No connection to the X server': remote_foreground("NonExistingServer")

I can't think of a recent change that could have caused this.
Perhaps it's a flaky test failure?

-- 
>From "know your smileys":
 :q vi user saying, "How do I get out of this damn emacs editor?"

 /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net   \\\
///  \\\
\\\sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
 \\\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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/202107042130.164LU1a62626698%40masaka.moolenaar.net.

Test failure building 8.2.3104

[Elimar Riesebieter]

Hi all,

Environment:
amd64
tmux
clang-12

Failures:
From test_vim9_builtin.vim:
Found errors in Test_remote_foreground():
command line..script 
/source/vim/vim-8.2.3104/src/vim-gtk3/testdir/runtest.vim[473]..function 
RunTheTest[44]..Test_remote_foreground line 5: Expected 'E241:' but got 'E240: 
No connection to the X server': remote_foreground("NonExistingServer")

Thanks
Elimar
-- 
  Experience is something you don't get until
  just after you need it!

-- 
-- 
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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/20210704173941.dvtc6nzjscaa63ve%40toy.home.lxtec.de.

Re: Test failure

[Elimar Riesebieter]

* Yegappan Lakshmanan  [2021-06-13 06:06 -0700]:

> Hi,
> 
> On Sun, Jun 13, 2021 at 5:50 AM Elimar Riesebieter  wrote:
> >
> > Hi all,
> >
> > building 8.2.2984 gives me:
> >
> > From test_excmd.vim:
> > Found errors in Test_sandbox():
> > command line..script 
> > /source/vim/vim-8.2.2984/src/vim-athena/testdir/runtest.vim[473]..function 
> > RunTheTest[44]..Test_sandbox[1]..Sandbox_tests line 62: Expected 'E48:' but 
> > got 'E519: Option not supported: imstyle': set imstyle
> >
> > Arch: amd64
> > Buildenv: tmux zsh
> > Compiler: clang-12
> >
> 
> Are you building with the Athena GUI support?

Yes

> What is the output of
> the following Vim
> commands?
> 
> :echo has('xim')
> :echo has('gui_gtk')

The build host is a headless machine. I am building Debian packages
for all supported gui versions and tiny, nox variants.

Elimar
-- 
  Excellent day for drinking heavily.
  Spike the office water cooler;-)

-- 
-- 
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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/20210613141310.rpuv5kuv6bpcvgcc%40toy.home.lxtec.de.

Re: Test failure

[Yegappan Lakshmanan]

Hi,

On Sun, Jun 13, 2021 at 5:50 AM Elimar Riesebieter  wrote:
>
> Hi all,
>
> building 8.2.2984 gives me:
>
> From test_excmd.vim:
> Found errors in Test_sandbox():
> command line..script 
> /source/vim/vim-8.2.2984/src/vim-athena/testdir/runtest.vim[473]..function 
> RunTheTest[44]..Test_sandbox[1]..Sandbox_tests line 62: Expected 'E48:' but 
> got 'E519: Option not supported: imstyle': set imstyle
>
> Arch: amd64
> Buildenv: tmux zsh
> Compiler: clang-12
>

Are you building with the Athena GUI support? What is the output of
the following Vim
commands?

:echo has('xim')
:echo has('gui_gtk')

Thanks,
Yegappan

-- 
-- 
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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/CAAW7x7m18Jt0J%3DNmb-yCJZa7bOj0Ghwg84moSe9v75TKDtSqxw%40mail.gmail.com.

Test failure

[Elimar Riesebieter]

Hi all,

building 8.2.2984 gives me:

>From test_excmd.vim:
Found errors in Test_sandbox():
command line..script 
/source/vim/vim-8.2.2984/src/vim-athena/testdir/runtest.vim[473]..function 
RunTheTest[44]..Test_sandbox[1]..Sandbox_tests line 62: Expected 'E48:' but got 
'E519: Option not supported: imstyle': set imstyle

Arch: amd64
Buildenv: tmux zsh
Compiler: clang-12

Thanks
Elimar
-- 
  "Talking much about oneself can also
   be a means to conceal oneself."
 -Friedrich Nietzsche

-- 
-- 
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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/20210613125005.xkglvrqol5s7i4yx%40toy.home.lxtec.de.

Re: Test failure building 8.2.2395

[Elimar Riesebieter]

Hi Dominique,

* Dominique Pellé  [2021-01-24 14:11 +0100]:

> Elimar Riesebieter wrote:
> 
> > Hi all,
> >
> > building 8.2.2395 I get:
> >
> > From test_fold.vim:
> > Found errors in Test_fold_relative_move():
> > command line..script 
> > /source/vim/vim-8.2.2395/src/vim-gtk3/testdir/runtest.vim[468]..function 
> > RunTheTest[39]..Test_fold_relative_move line 25: Expected 3 but got 2
> > command line..script 
> > /source/vim/vim-8.2.2395/src/vim-gtk3/testdir/runtest.vim[468]..function 
> > RunTheTest[39]..Test_fold_relative_move line 30: Expected 2 but got 1
> >
> > Building within tmux. Using clang-11 as compiler. Platform -> Linux amd64
> >
> > Elimar
> 
> Hi Elimar
> 
> The failing test is fixed in vim-8.2.2399.

8.2.2401 is running fine now. Thanks for cooperation. Much
appreciated ;-)

Elimar
-- 
  You cannot propel yourself forward by
  patting yourself on the back.

-- 
-- 
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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/20210124132752.cex7t5nuvhsez24j%40toy.home.lxtec.de.

Re: Test failure building 8.2.2395

[Dominique Pellé]

Elimar Riesebieter wrote:

> Hi all,
>
> building 8.2.2395 I get:
>
> From test_fold.vim:
> Found errors in Test_fold_relative_move():
> command line..script 
> /source/vim/vim-8.2.2395/src/vim-gtk3/testdir/runtest.vim[468]..function 
> RunTheTest[39]..Test_fold_relative_move line 25: Expected 3 but got 2
> command line..script 
> /source/vim/vim-8.2.2395/src/vim-gtk3/testdir/runtest.vim[468]..function 
> RunTheTest[39]..Test_fold_relative_move line 30: Expected 2 but got 1
>
> Building within tmux. Using clang-11 as compiler. Platform -> Linux amd64
>
> Elimar

Hi Elimar

The failing test is fixed in vim-8.2.2399.

Regards
Dominique

-- 
-- 
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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/CAON-T_j5B52emfXQNYTFTNW575vNnhUzdGuN_iCFFSjy_V6-nQ%40mail.gmail.com.

Re: Test failure building 8.2.2395

[Bram Moolenaar]

Elimar Riesebieter wrote:

> building 8.2.2395 I get:
> 
> From test_fold.vim:
> Found errors in Test_fold_relative_move():
> command line..script 
> /source/vim/vim-8.2.2395/src/vim-gtk3/testdir/runtest.vim[468]..function 
> RunTheTest[39]..Test_fold_relative_move line 25: Expected 3 but got 2
> command line..script 
> /source/vim/vim-8.2.2395/src/vim-gtk3/testdir/runtest.vim[468]..function 
> RunTheTest[39]..Test_fold_relative_move line 30: Expected 2 but got 1
> 
> Building within tmux. Using clang-11 as compiler. Platform -> Linux amd64

I cannot reproduce it.  Does valgrind say anything?

-- 
A scientist is someone who knows exactly how an engine works, but
can't fix his car when it fails to start.
An engineer is someone who knows only some things about an engine, but
can fix his car when it's broken.

 /// Bram Moolenaar -- b...@moolenaar.net -- 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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/202101231415.10NEFii52500101%40masaka.moolenaar.net.

Re: Test failure building 8.2.2395

[Dominique Pellé]

On Sat, Jan 23, 2021 at 2:19 PM Elimar Riesebieter  wrote:
>
> Hi all,
>
> building 8.2.2395 I get:
>
> From test_fold.vim:
> Found errors in Test_fold_relative_move():
> command line..script 
> /source/vim/vim-8.2.2395/src/vim-gtk3/testdir/runtest.vim[468]..function 
> RunTheTest[39]..Test_fold_relative_move line 25: Expected 3 but got 2
> command line..script 
> /source/vim/vim-8.2.2395/src/vim-gtk3/testdir/runtest.vim[468]..function 
> RunTheTest[39]..Test_fold_relative_move line 30: Expected 2 but got 1
>
> Building within tmux. Using clang-11 as compiler. Platform -> Linux amd64
>
> Elimar

I also see this test failure. I had created this ticket about it:

https://github.com/vim/vim/issues/7731

Glad it's not just me who sees this test failure :-)
Since not everybody sees the test failure, maybe
it's triggered by some build configs? I need to check
several build configs.

I hope to find time later today to look at it, at least
I want to look at the valgrind uninitialized memory in
the ticket (although it may be unrelated to the test failure).

Regards
Dominique

-- 
-- 
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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/CAON-T_j3bv905ron1OWrCZkVWOoKqx1C%2BZee%3DzQ02BcUAACaNA%40mail.gmail.com.

Test failure building 8.2.2395

[Elimar Riesebieter]

Hi all,

building 8.2.2395 I get:

>From test_fold.vim:
Found errors in Test_fold_relative_move():
command line..script 
/source/vim/vim-8.2.2395/src/vim-gtk3/testdir/runtest.vim[468]..function 
RunTheTest[39]..Test_fold_relative_move line 25: Expected 3 but got 2
command line..script 
/source/vim/vim-8.2.2395/src/vim-gtk3/testdir/runtest.vim[468]..function 
RunTheTest[39]..Test_fold_relative_move line 30: Expected 2 but got 1

Building within tmux. Using clang-11 as compiler. Platform -> Linux amd64

Elimar
-- 
  Learned men are the cisterns of knowledge,
  not the fountainheads ;-)

-- 
-- 
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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/20210123131916.pkv2baiiuo3jewoq%40toy.home.lxtec.de.

Re: Test failure in test_vim9_assign.vim

[Elimar Riesebieter]

* Bram Moolenaar  [2020-12-20 14:50 +0100]:

> 
> Elimar Riesebieter wrote:
> 
> > building 8.2.2166 gives me the following error:
> > 
> > Failures: 
> > From test_vim9_assign.vim:
> > Found errors in Test_assignment_dict():
> > command line..script 
> > /source/vim/vim-8.2.2166/src/vim-gtk3/testdir/runtest.vim[468]..function 
> > RunTheTest[39]..Test_assignment_dict[17]..CheckDefFailure line 3: ['var dd 
> > = {one: 1}', 'dd.one) = 2']: Expected 'E15:' but got 'E488: Trailing 
> > characters: ) = 2': ['var dd = {one: 1}', 'dd.one) = 2']
> 
> I'm sure I had fixed that...  Ah, but didn't include the fix.  Will make
> a separate patch.

Fixed with 8.2.2167.

Thanks
Elimar
-- 
  On the keyboard of life you have always
  to keep a finger at the escape key;-)

-- 
-- 
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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/20201220143010.2slyn2tcfjx3dynu%40toy.home.lxtec.de.

Re: Test failure in test_vim9_assign.vim

[Bram Moolenaar]

Elimar Riesebieter wrote:

> building 8.2.2166 gives me the following error:
> 
> Failures: 
> From test_vim9_assign.vim:
> Found errors in Test_assignment_dict():
> command line..script 
> /source/vim/vim-8.2.2166/src/vim-gtk3/testdir/runtest.vim[468]..function 
> RunTheTest[39]..Test_assignment_dict[17]..CheckDefFailure line 3: ['var dd = 
> {one: 1}', 'dd.one) = 2']: Expected 'E15:' but got 'E488: Trailing 
> characters: ) = 2': ['var dd = {one: 1}', 'dd.one) = 2']

I'm sure I had fixed that...  Ah, but didn't include the fix.  Will make
a separate patch.

-- 
An easy way to determine if you have enough teamwork to be doomed is simply to
measure how long it takes from the time you decide to go to lunch together
until the time you actually eat.
(Scott Adams - The Dilbert principle)

 /// Bram Moolenaar -- b...@moolenaar.net -- 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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/202012201350.0BKDo50c1894227%40masaka.moolenaar.net.

Test failure in test_vim9_assign.vim

[Elimar Riesebieter]

Hi all,

building 8.2.2166 gives me the following error:

Failures: 
From test_vim9_assign.vim:
Found errors in Test_assignment_dict():
command line..script 
/source/vim/vim-8.2.2166/src/vim-gtk3/testdir/runtest.vim[468]..function 
RunTheTest[39]..Test_assignment_dict[17]..CheckDefFailure line 3: ['var dd = 
{one: 1}', 'dd.one) = 2']: Expected 'E15:' but got 'E488: Trailing characters: 
) = 2': ['var dd = {one: 1}', 'dd.one) = 2']

Thanks in advance
Elimar
-- 
  Obviously the human brain works like a computer.
  Since there are no stupid computers humans can't be stupid.
  There are just a few running with Windows or even CE ;-)

-- 
-- 
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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/20201220132547.uizwuhsmaegkihe5%40toy.home.lxtec.de.

Re: Test Failure in test_terminal3.vim

[Bram Moolenaar]

Elimar Riesebieter wrote:

> * Elimar Riesebieter  [2020-07-15 08:52 +0200]:
> 
> > Hi all,
> > 
> > tried to build 8.2.1216 on amd64 within a tmux session using shadow
> > dirs and got:
> > 
> > >From test_terminal3.vim:
> > Found errors in Test_terminal_getwinpos():
> > Run 1:
> > function 
> > RunTheTest[39]..Test_terminal_getwinpos[16]..WaitForAssert[2]..7_WaitForCommon[11]..58
> >  line 1: Pattern '\\[\\d\\+, \\d\\+\\]' does not match '[-1, -1]\[  occurs 
> > 34 times]0,0-1 All'
> > function RunTheTest[39]..Test_terminal_getwinpos line 32: Expected 
> > range 1 - 1142, but got 0
> > function RunTheTest[39]..Test_terminal_getwinpos line 33: Expected 
> > range 1 - 419, but got 0
> 
> 
> As of 8.2.1287 for some not comprehensible reasons the tests are
> running fine now.
> 
> Sorry for the noise-

The terminal tests were hanging on Travis once in a while, for unknown
reasons.  I split off some tests to separate files, since then I haven't
seen the hang.  Might be correlated with your problem?

-- 
hundred-and-one symptoms of being an internet addict:
88. Every single time you press the 'Get mail' button...it does get new mail.

 /// Bram Moolenaar -- b...@moolenaar.net -- 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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/202007251755.06PHtTqE380545%40masaka.moolenaar.net.

Re: Test Failure in test_terminal3.vim

[Elimar Riesebieter]

* Elimar Riesebieter  [2020-07-15 08:52 +0200]:

> Hi all,
> 
> tried to build 8.2.1216 on amd64 within a tmux session using shadow
> dirs and got:
> 
> >From test_terminal3.vim:
> Found errors in Test_terminal_getwinpos():
> Run 1:
> function 
> RunTheTest[39]..Test_terminal_getwinpos[16]..WaitForAssert[2]..7_WaitForCommon[11]..58
>  line 1: Pattern '\\[\\d\\+, \\d\\+\\]' does not match '[-1, -1]\[  occurs 34 
> times]0,0-1 All'
> function RunTheTest[39]..Test_terminal_getwinpos line 32: Expected 
> range 1 - 1142, but got 0
> function RunTheTest[39]..Test_terminal_getwinpos line 33: Expected 
> range 1 - 419, but got 0


As of 8.2.1287 for some not comprehensible reasons the tests are
running fine now.

Sorry for the noise-
-- 
  You cannot propel yourself forward by
  patting yourself on the back.

-- 
-- 
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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/20200725145539.p543xzlmgnim4rl3%40toy.home.lxtec.de.

Re: Test Failure in test_terminal3.vim

[Bram Moolenaar]

Elimar Riesebieter wrote:

> tried to build 8.2.1216 on amd64 within a tmux session using shadow
> dirs and got:
> 
> From test_terminal3.vim:
> Found errors in Test_terminal_getwinpos():
> Run 1:
> function 
> RunTheTest[39]..Test_terminal_getwinpos[16]..WaitForAssert[2]..7_WaitForCommon[11]..58
>  line 1: Pattern '\\[\\d\\+, \\d\\+\\]' does not match '[-1, -1]\[  occurs 34 
> times]0,0-1 All'
> function RunTheTest[39]..Test_terminal_getwinpos line 32: Expected 
> range 1 - 1142, but got 0
> function RunTheTest[39]..Test_terminal_getwinpos line 33: Expected 
> range 1 - 419, but got 0

I tried using tmux, but didn't have this problem.
Anything else that might matter?

-- 
How To Keep A Healthy Level Of Insanity:
14. Put mosquito netting around your work area. Play a tape of jungle
sounds all day.

 /// Bram Moolenaar -- b...@moolenaar.net -- 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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/202007151152.06FBqcLF3310449%40masaka.moolenaar.net.

Test Failure in test_terminal3.vim

[Elimar Riesebieter]

Hi all,

tried to build 8.2.1216 on amd64 within a tmux session using shadow
dirs and got:

>From test_terminal3.vim:
Found errors in Test_terminal_getwinpos():
Run 1:
function 
RunTheTest[39]..Test_terminal_getwinpos[16]..WaitForAssert[2]..7_WaitForCommon[11]..58
 line 1: Pattern '\\[\\d\\+, \\d\\+\\]' does not match '[-1, -1]\[  occurs 34 
times]0,0-1 All'
function RunTheTest[39]..Test_terminal_getwinpos line 32: Expected 
range 1 - 1142, but got 0
function RunTheTest[39]..Test_terminal_getwinpos line 33: Expected 
range 1 - 419, but got 0

Thanks in advance
Elimar
-- 
.~.
/V\   L   I   N   U   X
   /( )\ >Phear the Penguin<
   ^^-^^

-- 
-- 
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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/20200715065216.wu75mys6kyduyhnp%40toy.home.lxtec.de.

Re: Test failure in Appveyor caused by patch 8.2.0921

[Bram Moolenaar]

Yegappan wrote:

> The MS-Windows tests are failing in Appveyor after patch 8.2.0921
> (CTRL-W T in cmdline window causes trouble).
> 
> It looks like the test_cmdline.vim test hangs.

I'm afraid I see no way to abort the test.  It will timeout after an
hour...

-- 
E  M  A  C  S
s  e  l  o  h
c  t  t  n  i
a  a t  f
pr  t
eo
 l

 /// Bram Moolenaar -- b...@moolenaar.net -- 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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/202006071735.057HZ1br100940%40masaka.moolenaar.net.

Test failure in Appveyor caused by patch 8.2.0921

[Yegappan Lakshmanan]

Hi,

The MS-Windows tests are failing in Appveyor after patch 8.2.0921
(CTRL-W T in cmdline window causes trouble).

It looks like the test_cmdline.vim test hangs.

- Yegappan

-- 
-- 
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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/CAAW7x7kG42GmS-ObmaYzFdz5ByTeD1y4UBVyB095ZWEmDgmbBQ%40mail.gmail.com.

Re: Test failure building 8.2.0746

[Yegappan Lakshmanan]

Hi,

On Wed, May 13, 2020 at 4:09 AM Elimar Riesebieter 
wrote:

> * Elimar Riesebieter  [2020-05-13 12:09 +0200]:
>
> > Building 8.2.0746 on amd64 within a tmux-session gives the follwing test
> > failure:
> >
> > Failures:
> > From test_terminal.vim:
> > Found errors in Test_term_keycode_translation():
> > Run 1:
> > function RunTheTest[39]..Test_term_keycode_translation line 30:
> Expected ['', '', '', '', '', '', '', '',
> '', '', '', '', '', '', '',
> '', '', '', '', '', '', '',
> '', '', '', '', '', '',
> '', '', '0123456789', '\t\t.+-*/'] but got ['', '',
> '', '', '', '', '', '', '', '', '',
> '', '', '', '', '', '', '',
> '', '', '', '', '\t\t.+-*/', '',
> '', '', '', '', '', '',
> '', '45678012']
>
> Noticed this is https://github.com/vim/vim/issues/6070.
>
> I tried to run the test with different TERM (xterm,
> rxvt-unicode-256color, tmux-256color) settings but no success.
>
>
I am not able to reproduce this test failure in a tmux session running
on Ubuntu 19.10 inside a gnome-terminal. I tried running the test with
TERM set to xterm, screen and tmux-256color. In all the case, the
test passes.


> Kitty is not available here. But to be honest, we shouldn't need a
> special terminal emulator to run this test, though.
>
>
You don't need a special terminal emulator to run this test.

Regards,
Yegappan


> Elimar
>
>

-- 
-- 
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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/CAAW7x7kWOkx4590FUKq14cMsRWc0Kz-TT2ire7HpGtYjMSKLAA%40mail.gmail.com.

Re: Test failure building 8.2.0746

[Bram Moolenaar]

Elimar Riesebieter wrote:

> Building 8.2.0746 on amd64 within a tmux-session gives the follwing test
> failure:
> 
> Failures:
> From test_terminal.vim:
> Found errors in Test_term_keycode_translation():
> Run 1:
> function RunTheTest[39]..Test_term_keycode_translation line 30: 
> Expected ['', '', '', '', '', '', '', '', 
> '', '', '', '', '', '', '', '', 
> '', '', '', '', '', '', '', 
> '', '', '', '', '', '', '', 
> '0123456789', '\t\t.+-*/'] but got ['', '', '', '', '', 
> '', '', '', '', '', '', '', '', 
> '', '', '', '', '', '', '', 
> '', '', '\t\t.+-*/', '', '', '', 
> '', '', '', '', '', '45678012']

I still can't reproduce this problem, also when running in tmux.
Anything else that matters?

-- 
The primary purpose of the DATA statement is to give names to constants;
instead of referring to pi as 3.141592653589793 at every appearance, the
variable PI can be given that value with a DATA statement and used instead
of the longer form of the constant.  This also simplifies modifying the
program, should the value of pi change.
-- FORTRAN manual for Xerox Computers

 /// Bram Moolenaar -- b...@moolenaar.net -- 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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/202005131454.04DEskhK011157%40masaka.moolenaar.net.

Re: Test failure building 8.2.0746

[Elimar Riesebieter]

* Elimar Riesebieter  [2020-05-13 12:09 +0200]:

> Building 8.2.0746 on amd64 within a tmux-session gives the follwing test
> failure:
> 
> Failures:
> From test_terminal.vim:
> Found errors in Test_term_keycode_translation():
> Run 1:
> function RunTheTest[39]..Test_term_keycode_translation line 30: 
> Expected ['', '', '', '', '', '', '', '', 
> '', '', '', '', '', '', '', '', 
> '', '', '', '', '', '', '', 
> '', '', '', '', '', '', '', 
> '0123456789', '\t\t.+-*/'] but got ['', '', '', '', '', 
> '', '', '', '', '', '', '', '', 
> '', '', '', '', '', '', '', 
> '', '', '\t\t.+-*/', '', '', '', 
> '', '', '', '', '', '45678012']

Noticed this is https://github.com/vim/vim/issues/6070. 

I tried to run the test with different TERM (xterm,
rxvt-unicode-256color, tmux-256color) settings but no success.

Kitty is not available here. But to be honest, we shouldn't need a
special terminal emulator to run this test, though.

Elimar
-- 
  Obviously the human brain works like a computer.
  Since there are no stupid computers humans can't be stupid.
  There are just a few running with Windows or even CE ;-)

-- 
-- 
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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/20200513110911.dks3grn6asrxo26v%40toy.home.lxtec.de.

Test failure building 8.2.0746

[Elimar Riesebieter]

Building 8.2.0746 on amd64 within a tmux-session gives the follwing test
failure:

Failures:
From test_terminal.vim:
Found errors in Test_term_keycode_translation():
Run 1:
function RunTheTest[39]..Test_term_keycode_translation line 30: 
Expected ['', '', '', '', '', '', '', '', 
'', '', '', '', '', '', '', '', 
'', '', '', '', '', '', '', 
'', '', '', '', '', '', '', 
'0123456789', '\t\t.+-*/'] but got ['', '', '', '', '', 
'', '', '', '', '', '', '', '', 
'', '', '', '', '', '', '', 
'', '', '\t\t.+-*/', '', '', '', 
'', '', '', '', '', '45678012']

Elimar
-- 
  >what IMHO then?
  IMHO - Inhalation of a Multi-leafed Herbal Opiate ;)
  --posting from alex in debian-user--

-- 
-- 
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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/20200513100900.zbv4vwggmd332227%40toy.home.lxtec.de.

Re: Appveyor normal build test failure

[Bram Moolenaar]

Yegappan wrote:

> The Appveyor normal build test is failing with the following errors:
> 
> Failures:
> >From test_vim9_script.vim:
> Caught exception: Vim(def):E117: Unknown function: test_null_job @
> C:/projects/vim/src/testdir/test_vim9_script.vim, line 171
> 
> Found errors in Test_assignment():
> Caught exception in Test_assignment(): Vim(call):call_eval_func(partial)
> not implemented yet @ function RunTheTest, line 40

Thanks for notifying me, I forgot to check Appveyor and their emails are
so spammy I tend to ignore then.

-- 
LAUNCELOT: Isn't there a St. Arrggghhh's in Cornwall?
ARTHUR:No, that's Saint Ives.
 "Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD

 /// Bram Moolenaar -- b...@moolenaar.net -- 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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/202004021712.032HCcij013381%40masaka.moolenaar.net.

Appveyor normal build test failure

[Yegappan Lakshmanan]

Hi,

The Appveyor normal build test is failing with the following errors:

Failures:
>From test_vim9_script.vim:
Caught exception: Vim(def):E117: Unknown function: test_null_job @
C:/projects/vim/src/testdir/test_vim9_script.vim, line 171

Found errors in Test_assignment():
Caught exception in Test_assignment(): Vim(call):call_eval_func(partial)
not implemented yet @ function RunTheTest, line 40

- Yegappan

-- 
-- 
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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/CAAW7x7kzYCnh8pjUOc3bkCt3eHvHR7Lkr9TW8QeDQKAtm9UVGg%40mail.gmail.com.

Re: Test failure E89 in Test_terminal_special_chars() line 11 (bwipe)

[Bram Moolenaar]

James McCoy wrote:

> > > > On Sat, Feb 22, 2020 at 9:02 AM Bram Moolenaar  
> > > > wrote:
> > > > >
> > > > > Dominique wrote:
> > > > >
> > > > > > At https://buildd.debian.org/status/package.php?p=vim
> > > > > > I noticed this test failure on hppa architecture:
> > > > > >
> > > > > > Caught exception in Test_terminal_special_chars(): 
> > > > > > Vim(bwipeout):E89:
> > > > > > No write since last change for buffer 132 (add ! to override) @
> > > > > > function RunTheTest[40]..Test_terminal_special_chars, line 11
> > > > > >
> > > > > > Line 11 in Test_terminal_special_chars() is 'bwipe'.
> > > > > > It looks like we should call 'bwipe!' (with exclamation mark)
> > > > > > in Test_terminal_special_chars(). Although I don't
> > > > > > understand why the current buffer would have
> > > > > > change in this test.
> > > > >
> > > > > After "term ls" finishes it should be possible to wipe out the buffer.
> > > > > You might have found an actual problem, adding "!" would be ignoring
> > > > > that problem.
> > > > 
> > > > I can reproduce this on the hppa porterbox.  Running the test on its
> > > > own is fine.  It's only when running the entire file that the error
> > > > shows up.  I'll see if I can narrow down what's causing the problem.
> > > 
> > > I appreciate it.  I can't reproduce.  I thought of something like
> > > 'fileformat' making the buffer marked as changed, but since this is also
> > > a kind of Unix it's probably something else.
> > 
> > Trimming test_terminal.vim down to just Test_terminal_shell_option() and
> > Test_terminal_special_chars() reproduces the problem.  Switching the
> > order of those tests "fixes" the problem, although I see no reason why
> > there should be any interaction.
> > 
> > I added some debugging and it seems that, when the test fails, the
> > terminal job has not finished yet.
> 
> Created PR#5685 with this fix and another set of fixes for
> test_autocmd.vim.
> 
> The only remaining test failures I'm reliably seeing are these:
> 
> Failures: 
>   From test_number.vim:
>   Found errors in Test_relativenumber_colors():
>   Run 1:
>   function 
> RunTheTest[40]..Test_relativenumber_colors[19]..VerifyScreenDump line 55: See 
> dump file difference: call 
> term_dumpdiff("testdir/failed/Test_relnr_colors_2.dump", 
> "testdir/dumps/Test_relnr_colors_2.dump"); difference in line 10: "|:|h|i| 
> |L|i|n|e|N|r|A|b|o|v|e| |c|t|e|r|m|f| @9|1@2|,|1| @8|5@1|%| "
>   function 
> RunTheTest[40]..Test_relativenumber_colors[23]..VerifyScreenDump line 55: See 
> dump file difference: call 
> term_dumpdiff("testdir/failed/Test_relnr_colors_3.dump", 
> "testdir/dumps/Test_relnr_colors_3.dump"); difference in line 10: "|:|h|i| 
> |L|i|n|e|N|r|B|e|l|o|w| |c|t|e|r|m|f| @9|1@2|,|1| @8|5@1|%| "
>   Run 2:
>   function 
> RunTheTest[40]..Test_relativenumber_colors[19]..VerifyScreenDump line 55: See 
> dump file difference: call 
> term_dumpdiff("testdir/failed/Test_relnr_colors_2.dump", 
> "testdir/dumps/Test_relnr_colors_2.dump"); difference in line 10: "|:|h|i| 
> |L|i|n|e|N|r|A|b|o|v|e| |c|t|e|r|m|f| @9|1@2|,|1| @8|5@1|%| "
>   function 
> RunTheTest[40]..Test_relativenumber_colors[23]..VerifyScreenDump line 55: See 
> dump file difference: call 
> term_dumpdiff("testdir/failed/Test_relnr_colors_3.dump", 
> "testdir/dumps/Test_relnr_colors_3.dump"); difference in line 10: "|:|h|i| 
> |L|i|n|e|N|r|B|e|l|o|w| |c|t|e|r|m|f| @9|1@2|,|1| @8|5@1|%| "
>   Flaky test failed too often, giving up
> 
> The problem above is that the display of the ":hi" command is getting
> truncated.

We are not interested in the command line for this test, let's clear it.

>   From test_popup.vim:
>   Found errors in Test_popup_and_previewwindow_dump():
>   Run 1:
>   function 
> RunTheTest[40]..Test_popup_and_previewwindow_dump[16]..VerifyScreenDump line 
> 55: See dump file difference: call 
> term_dumpdiff("testdir/failed/Test_popup_and_previewwindow_01.dump", 
> "testdir/dumps/Test_popup_and_previewwindow_01.dump"); difference in line 19: 
> "|[+3#000&|N|o| |N|a|m|e|]| |[|+|]| @43|1@1|,|1| @10|B|o|t"
>   Run 2:
>   fu

Re: Test failure E89 in Test_terminal_special_chars() line 11 (bwipe)

[Bram Moolenaar]

James McCoy wrote:

> > > On Sat, Feb 22, 2020 at 9:02 AM Bram Moolenaar  wrote:
> > > >
> > > > Dominique wrote:
> > > >
> > > > > At https://buildd.debian.org/status/package.php?p=vim
> > > > > I noticed this test failure on hppa architecture:
> > > > >
> > > > > Caught exception in Test_terminal_special_chars(): Vim(bwipeout):E89:
> > > > > No write since last change for buffer 132 (add ! to override) @
> > > > > function RunTheTest[40]..Test_terminal_special_chars, line 11
> > > > >
> > > > > Line 11 in Test_terminal_special_chars() is 'bwipe'.
> > > > > It looks like we should call 'bwipe!' (with exclamation mark)
> > > > > in Test_terminal_special_chars(). Although I don't
> > > > > understand why the current buffer would have
> > > > > change in this test.
> > > >
> > > > After "term ls" finishes it should be possible to wipe out the buffer.
> > > > You might have found an actual problem, adding "!" would be ignoring
> > > > that problem.
> > > 
> > > I can reproduce this on the hppa porterbox.  Running the test on its
> > > own is fine.  It's only when running the entire file that the error
> > > shows up.  I'll see if I can narrow down what's causing the problem.
> > 
> > I appreciate it.  I can't reproduce.  I thought of something like
> > 'fileformat' making the buffer marked as changed, but since this is also
> > a kind of Unix it's probably something else.
> 
> Trimming test_terminal.vim down to just Test_terminal_shell_option() and
> Test_terminal_special_chars() reproduces the problem.  Switching the
> order of those tests "fixes" the problem, although I see no reason why
> there should be any interaction.
> 
> I added some debugging and it seems that, when the test fails, the
> terminal job has not finished yet.
> 
> This change seems to make the test reliably pass.
> 
> diff --git i/src/testdir/test_terminal.vim w/src/testdir/test_terminal.vim
> index 64bc7db1e..2e482b278 100644
> --- i/src/testdir/test_terminal.vim
> +++ w/src/testdir/test_terminal.vim
> @@ -781,7 +781,7 @@ func Test_terminal_special_chars()
>call writefile(['x'], 'Xdir with spaces/quoted"file')
>term ls Xdir\ with\ spaces/quoted\"file
>call WaitForAssert({-> assert_match('quoted"file', term_getline('', 1))})
> -  call term_wait('')
> +  call WaitForAssert({-> assert_match('finish', term_getstatus(bufnr()))})
>  
>call delete('Xdir with spaces', 'rf')
>bwipe

I'll include it, thanks.

> While I've got the environment setup, I'll take a look at some of the
> other test failures on that system (and with a more recent Vim build).

Appreciated.

-- 
hundred-and-one symptoms of being an internet addict:
98. The Alta Vista administrators ask you what sites are missing
in their index files.

 /// Bram Moolenaar -- b...@moolenaar.net -- 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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/202002231230.01NCUQCK001398%40masaka.moolenaar.net.

Re: Test failure E89 in Test_terminal_special_chars() line 11 (bwipe)

[James McCoy]

On Sat, Feb 22, 2020 at 04:56:26PM -0500, James McCoy wrote:
> On Sat, Feb 22, 2020 at 09:21:56PM +0100, Bram Moolenaar wrote:
> > 
> > James McCoy wrote:
> > 
> > > On Sat, Feb 22, 2020 at 9:02 AM Bram Moolenaar  wrote:
> > > >
> > > > Dominique wrote:
> > > >
> > > > > At https://buildd.debian.org/status/package.php?p=vim
> > > > > I noticed this test failure on hppa architecture:
> > > > >
> > > > > Caught exception in Test_terminal_special_chars(): Vim(bwipeout):E89:
> > > > > No write since last change for buffer 132 (add ! to override) @
> > > > > function RunTheTest[40]..Test_terminal_special_chars, line 11
> > > > >
> > > > > Line 11 in Test_terminal_special_chars() is 'bwipe'.
> > > > > It looks like we should call 'bwipe!' (with exclamation mark)
> > > > > in Test_terminal_special_chars(). Although I don't
> > > > > understand why the current buffer would have
> > > > > change in this test.
> > > >
> > > > After "term ls" finishes it should be possible to wipe out the buffer.
> > > > You might have found an actual problem, adding "!" would be ignoring
> > > > that problem.
> > > 
> > > I can reproduce this on the hppa porterbox.  Running the test on its
> > > own is fine.  It's only when running the entire file that the error
> > > shows up.  I'll see if I can narrow down what's causing the problem.
> > 
> > I appreciate it.  I can't reproduce.  I thought of something like
> > 'fileformat' making the buffer marked as changed, but since this is also
> > a kind of Unix it's probably something else.
> 
> Trimming test_terminal.vim down to just Test_terminal_shell_option() and
> Test_terminal_special_chars() reproduces the problem.  Switching the
> order of those tests "fixes" the problem, although I see no reason why
> there should be any interaction.
> 
> I added some debugging and it seems that, when the test fails, the
> terminal job has not finished yet.

Created PR#5685 with this fix and another set of fixes for
test_autocmd.vim.

The only remaining test failures I'm reliably seeing are these:

Failures: 
From test_number.vim:
Found errors in Test_relativenumber_colors():
Run 1:
function 
RunTheTest[40]..Test_relativenumber_colors[19]..VerifyScreenDump line 55: See 
dump file difference: call 
term_dumpdiff("testdir/failed/Test_relnr_colors_2.dump", 
"testdir/dumps/Test_relnr_colors_2.dump"); difference in line 10: "|:|h|i| 
|L|i|n|e|N|r|A|b|o|v|e| |c|t|e|r|m|f| @9|1@2|,|1| @8|5@1|%| "
function 
RunTheTest[40]..Test_relativenumber_colors[23]..VerifyScreenDump line 55: See 
dump file difference: call 
term_dumpdiff("testdir/failed/Test_relnr_colors_3.dump", 
"testdir/dumps/Test_relnr_colors_3.dump"); difference in line 10: "|:|h|i| 
|L|i|n|e|N|r|B|e|l|o|w| |c|t|e|r|m|f| @9|1@2|,|1| @8|5@1|%| "
Run 2:
function 
RunTheTest[40]..Test_relativenumber_colors[19]..VerifyScreenDump line 55: See 
dump file difference: call 
term_dumpdiff("testdir/failed/Test_relnr_colors_2.dump", 
"testdir/dumps/Test_relnr_colors_2.dump"); difference in line 10: "|:|h|i| 
|L|i|n|e|N|r|A|b|o|v|e| |c|t|e|r|m|f| @9|1@2|,|1| @8|5@1|%| "
function 
RunTheTest[40]..Test_relativenumber_colors[23]..VerifyScreenDump line 55: See 
dump file difference: call 
term_dumpdiff("testdir/failed/Test_relnr_colors_3.dump", 
"testdir/dumps/Test_relnr_colors_3.dump"); difference in line 10: "|:|h|i| 
|L|i|n|e|N|r|B|e|l|o|w| |c|t|e|r|m|f| @9|1@2|,|1| @8|5@1|%| "
Flaky test failed too often, giving up

The problem above is that the display of the ":hi" command is getting truncated.

From test_popup.vim:
Found errors in Test_popup_and_previewwindow_dump():
Run 1:
function 
RunTheTest[40]..Test_popup_and_previewwindow_dump[16]..VerifyScreenDump line 
55: See dump file difference: call 
term_dumpdiff("testdir/failed/Test_popup_and_previewwindow_01.dump", 
"testdir/dumps/Test_popup_and_previewwindow_01.dump"); difference in line 19: 
"|[+3#000&|N|o| |N|a|m|e|]| |[|+|]| @43|1@1|,|1| @10|B|o|t"
Run 2:
function 
RunTheTest[40]..Test_popup_and_previewwindow_dump[16]..VerifyScreenDump line 
55: See dump file difference: call 
term_dumpdiff("testdir/failed/Test_popup_and_previewwindow_01.dump", 
"testdir/dumps/Test_popup_and_previewwindow_01.dump"); difference in line 19: 
"|[+3#000&|N|o| |N|a|m|e|]| |[|+|]| @43|1@1|,|1| @10|B|o|t&quo

Re: Test failure E89 in Test_terminal_special_chars() line 11 (bwipe)

[James McCoy]

On Sat, Feb 22, 2020 at 09:21:56PM +0100, Bram Moolenaar wrote:
> 
> James McCoy wrote:
> 
> > On Sat, Feb 22, 2020 at 9:02 AM Bram Moolenaar  wrote:
> > >
> > > Dominique wrote:
> > >
> > > > At https://buildd.debian.org/status/package.php?p=vim
> > > > I noticed this test failure on hppa architecture:
> > > >
> > > > Caught exception in Test_terminal_special_chars(): Vim(bwipeout):E89:
> > > > No write since last change for buffer 132 (add ! to override) @
> > > > function RunTheTest[40]..Test_terminal_special_chars, line 11
> > > >
> > > > Line 11 in Test_terminal_special_chars() is 'bwipe'.
> > > > It looks like we should call 'bwipe!' (with exclamation mark)
> > > > in Test_terminal_special_chars(). Although I don't
> > > > understand why the current buffer would have
> > > > change in this test.
> > >
> > > After "term ls" finishes it should be possible to wipe out the buffer.
> > > You might have found an actual problem, adding "!" would be ignoring
> > > that problem.
> > 
> > I can reproduce this on the hppa porterbox.  Running the test on its
> > own is fine.  It's only when running the entire file that the error
> > shows up.  I'll see if I can narrow down what's causing the problem.
> 
> I appreciate it.  I can't reproduce.  I thought of something like
> 'fileformat' making the buffer marked as changed, but since this is also
> a kind of Unix it's probably something else.

Trimming test_terminal.vim down to just Test_terminal_shell_option() and
Test_terminal_special_chars() reproduces the problem.  Switching the
order of those tests "fixes" the problem, although I see no reason why
there should be any interaction.

I added some debugging and it seems that, when the test fails, the
terminal job has not finished yet.

This change seems to make the test reliably pass.

diff --git i/src/testdir/test_terminal.vim w/src/testdir/test_terminal.vim
index 64bc7db1e..2e482b278 100644
--- i/src/testdir/test_terminal.vim
+++ w/src/testdir/test_terminal.vim
@@ -781,7 +781,7 @@ func Test_terminal_special_chars()
   call writefile(['x'], 'Xdir with spaces/quoted"file')
   term ls Xdir\ with\ spaces/quoted\"file
   call WaitForAssert({-> assert_match('quoted"file', term_getline('', 1))})
-  call term_wait('')
+  call WaitForAssert({-> assert_match('finish', term_getstatus(bufnr()))})
 
   call delete('Xdir with spaces', 'rf')
   bwipe

While I've got the environment setup, I'll take a look at some of the
other test failures on that system (and with a more recent Vim build).

Cheers,
-- 
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7  2D23 DFE6 91AE 331B A3DB

-- 
-- 
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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/2020015625.kwjw3dmfzxsluu5a%40localhost.

Re: Test failure E89 in Test_terminal_special_chars() line 11 (bwipe)

[Bram Moolenaar]

James McCoy wrote:

> On Sat, Feb 22, 2020 at 9:02 AM Bram Moolenaar  wrote:
> >
> > Dominique wrote:
> >
> > > At https://buildd.debian.org/status/package.php?p=vim
> > > I noticed this test failure on hppa architecture:
> > >
> > > Caught exception in Test_terminal_special_chars(): Vim(bwipeout):E89:
> > > No write since last change for buffer 132 (add ! to override) @
> > > function RunTheTest[40]..Test_terminal_special_chars, line 11
> > >
> > > Line 11 in Test_terminal_special_chars() is 'bwipe'.
> > > It looks like we should call 'bwipe!' (with exclamation mark)
> > > in Test_terminal_special_chars(). Although I don't
> > > understand why the current buffer would have
> > > change in this test.
> >
> > After "term ls" finishes it should be possible to wipe out the buffer.
> > You might have found an actual problem, adding "!" would be ignoring
> > that problem.
> 
> I can reproduce this on the hppa porterbox.  Running the test on its
> own is fine.  It's only when running the entire file that the error
> shows up.  I'll see if I can narrow down what's causing the problem.

I appreciate it.  I can't reproduce.  I thought of something like
'fileformat' making the buffer marked as changed, but since this is also
a kind of Unix it's probably something else.

-- 
hundred-and-one symptoms of being an internet addict:
93. New mail alarm on your palmtop annoys other churchgoers.

 /// Bram Moolenaar -- b...@moolenaar.net -- 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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/20200021.01MKLu6H026083%40masaka.moolenaar.net.

Re: Test failure E89 in Test_terminal_special_chars() line 11 (bwipe)

[James McCoy]

On Sat, Feb 22, 2020 at 9:02 AM Bram Moolenaar  wrote:
>
>
> Dominique wrote:
>
> > At https://buildd.debian.org/status/package.php?p=vim
> > I noticed this test failure on hppa architecture:
> >
> > Caught exception in Test_terminal_special_chars(): Vim(bwipeout):E89:
> > No write since last change for buffer 132 (add ! to override) @
> > function RunTheTest[40]..Test_terminal_special_chars, line 11
> >
> > Line 11 in Test_terminal_special_chars() is 'bwipe'.
> > It looks like we should call 'bwipe!' (with exclamation mark)
> > in Test_terminal_special_chars(). Although I don't
> > understand why the current buffer would have
> > change in this test.
>
> After "term ls" finishes it should be possible to wipe out the buffer.
> You might have found an actual problem, adding "!" would be ignoring
> that problem.

I can reproduce this on the hppa porterbox.  Running the test on its
own is fine.  It's only when running the entire file that the error
shows up.  I'll see if I can narrow down what's causing the problem.

Cheers,
James

-- 
-- 
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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/CAFeRdpds1z3H0BoBhvng35Q0L5C1qvbw42Uf3yfm1aDG3xo%2BXA%40mail.gmail.com.

Re: Test failure E89 in Test_terminal_special_chars() line 11 (bwipe)

[Bram Moolenaar]

Dominique wrote:

> At https://buildd.debian.org/status/package.php?p=vim
> I noticed this test failure on hppa architecture:
> 
> Caught exception in Test_terminal_special_chars(): Vim(bwipeout):E89:
> No write since last change for buffer 132 (add ! to override) @
> function RunTheTest[40]..Test_terminal_special_chars, line 11
> 
> Line 11 in Test_terminal_special_chars() is 'bwipe'.
> It looks like we should call 'bwipe!' (with exclamation mark)
> in Test_terminal_special_chars(). Although I don't
> understand why the current buffer would have
> change in this test.

After "term ls" finishes it should be possible to wipe out the buffer.
You might have found an actual problem, adding "!" would be ignoring
that problem.

> Test_terminal_cwd() has the same kind of error.

-- 
>From "know your smileys":
 :-| :-|   Deja' vu!

 /// Bram Moolenaar -- b...@moolenaar.net -- 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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/202002221401.01ME1xba009771%40masaka.moolenaar.net.

Test failure E89 in Test_terminal_special_chars() line 11 (bwipe)

[Dominique Pellé]

Hi

At https://buildd.debian.org/status/package.php?p=vim
I noticed this test failure on hppa architecture:

Caught exception in Test_terminal_special_chars(): Vim(bwipeout):E89:
No write since last change for buffer 132 (add ! to override) @
function RunTheTest[40]..Test_terminal_special_chars, line 11

Line 11 in Test_terminal_special_chars() is 'bwipe'.
It looks like we should call 'bwipe!' (with exclamation mark)
in Test_terminal_special_chars(). Although I don't
understand why the current buffer would have
change in this test.

Test_terminal_cwd() has the same kind of error.

Regards
Dominique

-- 
-- 
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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/CAON-T_g8-0XrCq7%2BZ0U8Z-XYP%3D9t9dEzYs-S2G8PCtoXcdg0Hg%40mail.gmail.com.

Re: [vim/vim] 8c5a278fc508da6 causes test failure on macOS (#4789)

[Bram Moolenaar]

Turns out that since 8.1.1669 Travis did not report failed tests.


-- 
hundred-and-one symptoms of being an internet addict:
36. You miss more than five meals a week downloading the latest games from
Apogee.

 /// Bram Moolenaar -- b...@moolenaar.net -- 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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/201908082040.x78Ke76a019611%40masaka.moolenaar.net.

Re: Test failure in test_popupwin

[Christian Brabandt]

On Do, 25 Jul 2019, Bram Moolenaar wrote:

> The other way around: The modeless selection doesn't show.  It is
> selected with some tricky mouse events.  But it appears to work in most
> places.  Any idea what is different about this system?  Ah, you mention
> putty.  I also had it fail on an ssh connection.  Perhaps it's because
> in the terminal window mouse dragging is not activated.

So is there any way to detect whether mouse selection should work?

Best,
Christian
-- 
Philosoph:
  Mensch, der sich bei saurer Milch damit tröstet, daß sie zu vier
  Fünfteln aus Wasser besteht.

-- 
-- 
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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/20190726191430.GD32566%40256bit.org.

Re: Test failure in test_popupwin

[Bram Moolenaar]

Christian wrote:

> when running the testsuite, I see the following error for 
> test_popupwin.vim:
> 
> 
> Screenshot: https://i.imgur.com/1OEnpP5.png
> 
> 1 FAILED:
> Found errors in Test_popup_select():
> Run 1:
> function RunTheTest[40]..Test_popup_select[26]..VerifyScreenDump line 55: See 
> dump file difference: call 
> term_dumpdiff("testdir/failed/Test_popupwin_select_01.dump", 
> "testdir/dumps/Test_popupwin_select_01.dump"); difference in line 4: "|4| 
> @7|║+0#001#ffd7ff255|t|h|e|
> ─|w|o|r|d| @9|║| +0#000#ff0@45"; difference in line 5: "|5| 
> @7|║+0#001#ffd7ff255|s|o|m|e| |m|o|r|e| @8|║| +0#000#ff0@45"; 
> difference in line 6: "|6| @7|║+0#001#ffd7ff255|s|e|v|e|r|a|l| 
> |w|o|r|d|s| |h|e|r|e|║| +0#000#ff0@45"
> function RunTheTest[40]..Test_popup_select[33]..VerifyScreenDump line 55: See 
> dump file difference: call 
> term_dumpdiff("testdir/failed/Test_popupwin_select_02.dump", 
> "testdir/dumps/Test_popupwin_select_02.dump"); difference in line 1: 
> 

Re: Test failure in Test_diffmode.vim building 8.1.1735 on Linux powerpc

[Bram Moolenaar]

Elimar Riesebieter wrote:

> * Christian Brabandt  [2019-07-24 19:33 +0200]:
> 
> > Can you share the actual failed screendump file?
> > 
> > > Am 24.07.2019 um 15:27 schrieb Elimar Riesebieter :
> > > 
> > > * Bram Moolenaar  [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#e05#a8a8a8255| > 
> > >>> +0#000#ff0@34||+1&&|-+0#e05#a8a8a8255| | 
> > >>> +0#000#ff0@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 1.

-- 
"The future's already arrived - it's just not evenly distributed yet."
-- William Gibson

 /// Bram Moolenaar -- b...@moolenaar.net -- 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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/201907252104.x6PL4ReU021386%40masaka.moolenaar.net.

Test failure in test_popupwin

[Christian Brabandt]

Bram,
when running the testsuite, I see the following error for 
test_popupwin.vim:


Screenshot: https://i.imgur.com/1OEnpP5.png

1 FAILED:
Found errors in Test_popup_select():
Run 1:
function RunTheTest[40]..Test_popup_select[26]..VerifyScreenDump line 55: See 
dump file difference: call 
term_dumpdiff("testdir/failed/Test_popupwin_select_01.dump", 
"testdir/dumps/Test_popupwin_select_01.dump"); difference in line 4: "|4| 
@7|║+0#001#ffd7ff255|t|h|e|
─|w|o|r|d| @9|║| +0#000#ff0@45"; difference in line 5: "|5| 
@7|║+0#001#ffd7ff255|s|o|m|e| |m|o|r|e| @8|║| +0#000#ff0@45"; 
difference in line 6: "|6| @7|║+0#001#ffd7ff255|s|e|v|e|r|a|l| |w|o|r|d|s| 
|h|e|r|e|║| +0#000#ff0@45"
function RunTheTest[40]..Test_popup_select[33]..VerifyScreenDump line 55: See 
dump file difference: call 
term_dumpdiff("testdir/failed/Test_popupwin_select_02.dump", 
"testdir/dumps/Test_popupwin_select_02.dump"); difference in line 1: 

Re: Test failure in Test_diffmode.vim building 8.1.1735 on Linux powerpc

[Christian Brabandt]

On Mi, 24 Jul 2019, Elimar Riesebieter wrote:

> * Christian Brabandt  [2019-07-24 19:33 +0200]:
> 
> > Can you share the actual failed screendump file?
> > 
> > > Am 24.07.2019 um 15:27 schrieb Elimar Riesebieter :
> > > 
> > > * Bram Moolenaar  [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#e05#a8a8a8255| > 
> > >>> +0#000#ff0@34||+1&&|-+0#e05#a8a8a8255| | 
> > >>> +0#000#ff0@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. Please find attached screendumps.
> 
> Thanks for investigation

Well, the dump for 05 seems to be corrupted, it prints corrupted all 
over the place...

The dump for file 16 looks like it did not really update the diff? Not 
sure how this can happen.

The other is just the commandline displaying the filename instead of the 
:

To prevent this, the test always adds a "\n:" so that the commandline 
always displays as ':', apparently this did not work...

Can you manually run through the test Test_diff_screen() and see what 
happens?


Best,
Christian
-- 
Die Fähigkeit, seine Muße klug auszufüllen, ist die letzte Stufe der
persönlichen Kultur.
-- 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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/20190724211634.GC9808%40256bit.org.

Re: Test failure in Test_diffmode.vim building 8.1.1735 on Linux powerpc

[Elimar Riesebieter]

* Christian Brabandt  [2019-07-24 19:33 +0200]:

> Can you share the actual failed screendump file?
> 
> > Am 24.07.2019 um 15:27 schrieb Elimar Riesebieter :
> > 
> > * Bram Moolenaar  [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#e05#a8a8a8255| > 
> >>> +0#000#ff0@34||+1&&|-+0#e05#a8a8a8255| | 
> >>> +0#000#ff0@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. Please find attached screendumps.

Thanks for investigation

Elimar
-- 
  Excellent day for drinking heavily.
  Spike the office water cooler;-)

-- 
-- 
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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/20190724203438.gthapw4whsrqw3db%40toy.home.lxtec.de.


vim-8.1.1724_Test_diffs_dumps.tar.xz
Description: application/xz

Re: Test failure in Test_diffmode.vim building 8.1.1735 on Linux powerpc

[Christian Brabandt]

Can you share the actual failed screendump file?

> Am 24.07.2019 um 15:27 schrieb Elimar Riesebieter :
> 
> * Bram Moolenaar  [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#e05#a8a8a8255| > 
>>> +0#000#ff0@34||+1&&|-+0#e05#a8a8a8255| | 
>>> +0#000#ff0@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.
> 
> Elimar
> -- 
>  The path to source is always uphill!
>-unknown-
> 
> -- 
> -- 
> 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 vim_dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/vim_dev/20190724132744.bs7lftdbju5yz6wy%40toy.home.lxtec.de.

-- 
-- 
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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/492933A3-04A8-4D6C-BE1D-33462BA12E84%40256bit.org.

Re: Test failure in Test_diffmode.vim building 8.1.1735 on Linux powerpc

[Elimar Riesebieter]

* Bram Moolenaar  [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#e05#a8a8a8255| > 
> > +0#000#ff0@34||+1&&|-+0#e05#a8a8a8255| | 
> > +0#000#ff0@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.

Elimar
-- 
  The path to source is always uphill!
-unknown-

-- 
-- 
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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/20190724132744.bs7lftdbju5yz6wy%40toy.home.lxtec.de.

Re: Test failure in Test_diffmode.vim building 8.1.1735 on Linux powerpc

[Bram Moolenaar]

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#e05#a8a8a8255| > +0#000#ff0@34||+1&&|-+0#e05#a8a8a8255| 
> | +0#000#ff0@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.

-- 
THEOREM: VI is perfect.
PROOF: VI in roman numerals is 6.  The natural numbers < 6 which divide 6 are
1, 2, and 3. 1+2+3 = 6.  So 6 is a perfect number.  Therefore, VI is perfect.
QED
-- Arthur Tateishi

 /// Bram Moolenaar -- b...@moolenaar.net -- 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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/201907241300.x6OD03nZ029884%40masaka.moolenaar.net.

Test failure in Test_diffmode.vim building 8.1.1735 on Linux powerpc

[Elimar Riesebieter]

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#e05#a8a8a8255| > +0#000#ff0@34||+1&&|-+0#e05#a8a8a8255| | 
+0#000#ff0@34"; difference in line 20: "|"+0&&|X|f|i|l|e|2|"| |0|L|,| 
|0|C| @59"
function 
RunTheTest[40]..Test_diff_screen[112]..VerifyInternal[5]..VerifyScreenDump line 
55: See dump file difference: call 
term_dumpdiff("testdir/failed/Test_diff_17.dump", 
"testdir/dumps/Test_diff_17.dump"); difference in line 1: "| 
+0#e05#a8a8a8255@1>a+0#000#ff0| @33||+1&&| 
+0#e05#a8a8a8255@1|a+0#000#ff0| @33"; difference in line 4: "| 
+0#e05#a8a8a8255@1|-+0#4040ff13#af255@34||+1#000#ff0| 
+0#e05#a8a8a8255@1| +0#000#5fd7ff255@34"; difference in line 5: "| 
+0#e05#a8a8a8255@1|e+0#000#ff0|f| @32||+1&&| 
+0#e05#a8a8a8255@1|e+0#000#ff0|f| @32"; difference in line 6: "| 
+0#e05#a8a8a8255@1|x+2#000#ff404010@2| 

Re: Test failure in test_popupwin.vim building 8.1.1535

[Bram Moolenaar]

Elimar Riesebieter wrote:

> > * Bram Moolenaar  [2019-06-15 19:37 +0200]:
> > 
> > > 
> > > Elimar Riesebieter wrote:
> > > 
> > > > > > Building 8.1.1535 within a remote tmux session I get:
> > > > > > 
> > > > > > Executed:  2097 Tests
> > > > > >  Skipped:16 Tests
> > > > > >   FAILED: 1 Tests
> > > > > > 
> > > > > > 
> > > > > > Failures:
> > > > > > From test_popupwin.vim:
> > > > > > Found errors in Test_popup_select():
> > > > > > 
> > > > > 
> > > > > Yeah, had to update git on my Mac to be able to figure out what was
> > > > > failing.  Fixed in 8.1.1536.
> > > > 
> > > > I am running on a x86_64. And the failure still exists building
> > > > 8.1.1545.
> > > 
> > > It passes on Travis.  Is your setup different?
> > 
> > Building in a clean chroot.
> 
> I tried several LANG settings, gcc 8.3 vs. clang 8. All the same
> result. Tiny version builds but gtk version fails. All is done on
> "shadow dirs".
> 
> Please notice:
> 
> 
> --- src/vim-gtk/testdir/dumps/Test_popupwin_select_01.dump2019-06-15 
> 23:10:30.0 +0200
> +++ src/vim-gtk/testdir/failed/Test_popupwin_select_01.dump   2019-06-16 
> 09:10:20.520773300 +0200
> @@ -1,9 +1,9 @@
>  

Re: Test failure in test_popupwin.vim building 8.1.1535

[Elimar Riesebieter]

* Elimar Riesebieter  [2019-06-15 20:03 +0200]:

> * Bram Moolenaar  [2019-06-15 19:37 +0200]:
> 
> > 
> > Elimar Riesebieter wrote:
> > 
> > > > > Building 8.1.1535 within a remote tmux session I get:
> > > > > 
> > > > > Executed:  2097 Tests
> > > > >  Skipped:16 Tests
> > > > >   FAILED: 1 Tests
> > > > > 
> > > > > 
> > > > > Failures:
> > > > > From test_popupwin.vim:
> > > > > Found errors in Test_popup_select():
> > > > > 
> > > > 
> > > > Yeah, had to update git on my Mac to be able to figure out what was
> > > > failing.  Fixed in 8.1.1536.
> > > 
> > > I am running on a x86_64. And the failure still exists building
> > > 8.1.1545.
> > 
> > It passes on Travis.  Is your setup different?
> 
> Building in a clean chroot.

I tried several LANG settings, gcc 8.3 vs. clang 8. All the same
result. Tiny version builds but gtk version fails. All is done on
"shadow dirs".

Please notice:


--- src/vim-gtk/testdir/dumps/Test_popupwin_select_01.dump  2019-06-15 
23:10:30.0 +0200
+++ src/vim-gtk/testdir/failed/Test_popupwin_select_01.dump 2019-06-16 
09:10:20.520773300 +0200
@@ -1,9 +1,9 @@
 

Re: Test failure in test_popupwin.vim building 8.1.1535

[Elimar Riesebieter]

* Bram Moolenaar  [2019-06-15 19:37 +0200]:

> 
> Elimar Riesebieter wrote:
> 
> > > > Building 8.1.1535 within a remote tmux session I get:
> > > > 
> > > > Executed:  2097 Tests
> > > >  Skipped:16 Tests
> > > >   FAILED: 1 Tests
> > > > 
> > > > 
> > > > Failures:
> > > > From test_popupwin.vim:
> > > > Found errors in Test_popup_select():
> > > > 
> > > 
> > > Yeah, had to update git on my Mac to be able to figure out what was
> > > failing.  Fixed in 8.1.1536.
> > 
> > I am running on a x86_64. And the failure still exists building
> > 8.1.1545.
> 
> It passes on Travis.  Is your setup different?

Builing in a clean chroot.

Elimar
-- 
  Obviously the human brain works like a computer.
  Since there are no stupid computers humans can't be stupid.
  There are just a few running with Windows or even CE ;-)

-- 
-- 
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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/20190615180330.dbdwutfucidxgugm%40toy.home.lxtec.de.
For more options, visit https://groups.google.com/d/optout.

Re: Test failure in test_popupwin.vim building 8.1.1535

[Bram Moolenaar]

Elimar Riesebieter wrote:

> > > Building 8.1.1535 within a remote tmux session I get:
> > > 
> > > Executed:  2097 Tests
> > >  Skipped:16 Tests
> > >   FAILED: 1 Tests
> > > 
> > > 
> > > Failures:
> > > From test_popupwin.vim:
> > > Found errors in Test_popup_select():
> > > 
> > 
> > Yeah, had to update git on my Mac to be able to figure out what was
> > failing.  Fixed in 8.1.1536.
> 
> I am running on a x86_64. And the failure still exists building
> 8.1.1545.

It passes on Travis.  Is your setup different?

-- 
hundred-and-one symptoms of being an internet addict:
193. You ask your girlfriend to drive home so you can sit back with
 your PDA and download the information to your laptop

 /// Bram Moolenaar -- b...@moolenaar.net -- 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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/201906151737.x5FHbThB014256%40masaka.moolenaar.net.
For more options, visit https://groups.google.com/d/optout.

Re: Test failure in test_popupwin.vim building 8.1.1535

[Elimar Riesebieter]

* Bram Moolenaar  [2019-06-15 15:45 +0200]:

> 
> Elimar Riesebieter wrote:
> 
> > Building 8.1.1535 within a remote tmux session I get:
> > 
> > Executed:  2097 Tests
> >  Skipped:16 Tests
> >   FAILED: 1 Tests
> > 
> > 
> > Failures:
> > From test_popupwin.vim:
> > Found errors in Test_popup_select():
> > 
> 
> Yeah, had to update git on my Mac to be able to figure out what was
> failing.  Fixed in 8.1.1536.

I am running on a x86_64. And the failure still exists building
8.1.1545.

Elimar
-- 
  Never make anything simple and efficient when a way
  can be found to make it complex and wonderful ;-)

-- 
-- 
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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/20190615165006.tq2ljxogjq2rcb5f%40toy.home.lxtec.de.
For more options, visit https://groups.google.com/d/optout.

Re: Test failure in test_popupwin.vim building 8.1.1535

[Bram Moolenaar]

Elimar Riesebieter wrote:

> Building 8.1.1535 within a remote tmux session I get:
> 
> Executed:  2097 Tests
>  Skipped:16 Tests
>   FAILED: 1 Tests
> 
> 
> Failures:
> From test_popupwin.vim:
> Found errors in Test_popup_select():
> 

Yeah, had to update git on my Mac to be able to figure out what was
failing.  Fixed in 8.1.1536.

-- 
hundred-and-one symptoms of being an internet addict:
184. You no longer ask prospective dates what their sign is, instead
 your line is "Hi, what's your URL?"

 /// Bram Moolenaar -- b...@moolenaar.net -- 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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/201906151345.x5FDjMp6008028%40masaka.moolenaar.net.
For more options, visit https://groups.google.com/d/optout.

Test failure in test_popupwin.vim building 8.1.1535

[Elimar Riesebieter]

Building 8.1.1535 within a remote tmux session I get:

Executed:  2097 Tests
 Skipped:16 Tests
  FAILED: 1 Tests


Failures:
From test_popupwin.vim:
Found errors in Test_popup_select():
Run 1:
function RunTheTest[40]..Test_popup_select[25]..VerifyScreenDump line 
55: See dump file difference: call 
term_dumpdiff("failed/Test_popupwin_select_01.dump", 
"dumps/Test_popupwin_select_01.dump"); difference in line 4: "|4| 
@7|║+0#001#ffd7ff255|t|h|e| |w|o|r|d| @9|║| +0#000#ff0@45"; 
difference in line 5: "|5| @7|║+0#001#ffd7ff255|s|o|m|e| |m|o|r|e| @8|║| 
+0#000#ff0@45"; difference
in line 6: "|6| @7|║+0#001#ffd7ff255|s|e|v|e|r|a|l| |w|o|r|d|s| |h|e|r|e|║| 
+0#000#ff0@45"
function RunTheTest[40]..Test_popup_select[29]..VerifyScreenDump line 
55: See dump file difference: call 
term_dumpdiff("failed/Test_popupwin_select_02.dump", 
"dumps/Test_popupwin_select_02.dump"); difference in line 1: 

Re: Test failure

[Bram Moolenaar]

Elimar Riesebieter wrote:

> This is building vim-8.1.1439 in a remote tmux session with shadow
> dirs:
> 
> Found errors in Test_win_execute():
> function RunTheTest[40]..Test_win_execute line 15: Expected 'E937:' but got 
> 'E994: Not allowed in a popup window': call win_execute(popupwin, "bwipe!")

Fixed by 8.1.1440.

-- 
hundred-and-one symptoms of being an internet addict:
76. Your ISP regards you as a business partner rather than as a customer.

 /// Bram Moolenaar -- b...@moolenaar.net -- 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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/201906011529.x51FT9pf021492%40masaka.moolenaar.net.
For more options, visit https://groups.google.com/d/optout.

Test failure

[Elimar Riesebieter]

This is building vim-8.1.1439 in a remote tmux session with shadow
dirs:

Found errors in Test_win_execute():
function RunTheTest[40]..Test_win_execute line 15: Expected 'E937:' but got 
'E994: Not allowed in a popup window': call win_execute(popupwin, "bwipe!")

Elimar
-- 
  On the keyboard of life you have always
  to keep a finger at the escape key;-)

-- 
-- 
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 vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_dev/20190601150646.birrn4dkhp2d6v6k%40toy.home.lxtec.de.
For more options, visit https://groups.google.com/d/optout.

Re: [vim/vim] Vim 8.1.0922 Test failure on macOS 10.14 (#3965)

[Bram Moolenaar]

> > From test_terminal.vim:
> > Found errors in Test_terminal_postponed_scrollback():
> > Run 1:
> > function 
> > RunTheTest[40]..Test_terminal_postponed_scrollback[17]..VerifyScreenDump 
> > line 20: See dump file difference: call 
> > term_dumpdiff("Test_terminal_01.dump.failed", "dumps/Test_terminal_01.dump")
> > function 
> > RunTheTest[40]..Test_terminal_postponed_scrollback[23]..VerifyScreenDump 
> > line 20: See dump file difference: call 
> > term_dumpdiff("Test_terminal_02.dump.failed", "dumps/Test_terminal_02.dump")
> > function 
> > RunTheTest[40]..Test_terminal_postponed_scrollback[28]..VerifyScreenDump 
> > line 20: See dump file difference: call 
> > term_dumpdiff("Test_terminal_03.dump.failed", "dumps/Test_terminal_03.dump")
> > Run 2:
> > function 
> > RunTheTest[40]..Test_terminal_postponed_scrollback[17]..VerifyScreenDump 
> > line 20: See dump file difference: call 
> > term_dumpdiff("Test_terminal_01.dump.failed", "dumps/Test_terminal_01.dump")
> > function 
> > RunTheTest[40]..Test_terminal_postponed_scrollback[23]..VerifyScreenDump 
> > line 20: See dump file difference: call 
> > term_dumpdiff("Test_terminal_02.dump.failed", "dumps/Test_terminal_02.dump")
> > function 
> > RunTheTest[40]..Test_terminal_postponed_scrollback[28]..VerifyScreenDump 
> > line 20: See dump file difference: call 
> > term_dumpdiff("Test_terminal_03.dump.failed", "dumps/Test_terminal_03.dump")
> > Flaky test failed too often, giving up
> > TEST FAILURE
> > make[2]: *** [report] Error 1
> > make[1]: *** [scripttests] Error 2
> > make: *** [test] Error 2
> > ```
> 
> It appears to be a race condition.  It passes on my machine, thus it's
> hard to know how to fix it.  Increasing the sleep might work, even
> though it's not a good solution.

It is me who needed sleep.  I didn't notice the shell name was in the
screenshot.

-- 
Hanson's Treatment of Time:
There are never enough hours in a day, but always too
many days before Saturday.

 /// Bram Moolenaar -- b...@moolenaar.net -- 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 vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Test failure on arch i386

[Bram Moolenaar]

Elimar Riesebieter wrote:

> > > > Hi all,
> > > > 
> > > > compiling vim 8.1.0315 on arch i386 gives the following failure:
> > > > 
> > > > >From test_search.vim:
> > > > Found errors in Test_incsearch_substitute_dump():
> > > > function 
> > > > RunTheTest[40]..Test_incsearch_substitute_dump[69]..VerifyScreenDump 
> > > > line 14: See dump file difference: call 
> > > > term_dumpdiff("Test_incsearch_substitute_07.dump.failed", 
> > > > "dumps/Test_incsearch_substitute_07.dump")
> > > 
> > > 
> > > The diff is as follows:
> > > 
> > > 
> > > --- ./src/testdir/dumps/Test_incsearch_substitute_07.dump   
> > > 2018-08-21 21:58:13.0 +0200
> > > +++ ./src/vim-gtk3/testdir/Test_incsearch_substitute_07.dump.failed 
> > > 2018-08-22 03:11:40.341265509 +0200
> > > @@ -6,4 +6,4 @@
> > >  |f|o@1| |9| @64
> > >  |f|o@1| |1|0| @63
> > >  |b+9&&|a|r| +8&&|1@1| @63
> > > -|:+0&&|9|,|1@1|s|/|b|a|r> @59
> > > +|:+0&&|9|,|1@1|s|/|b|a|r> @31| @1| @25
> > 
> > Now that is weird, it's the same number of spaces but encoded
> > differently.  Looks like there is some attribute that's different but is
> > not reflected in the screendump.  Can you do some debugging on this?
> > It's hard for me, since I cannot reproduce it.
> 
> A second build in a tmux session ran fine. The first build was in a
> detached tmux session. Maybe that was the reason of the failure?

I found a mistake in the way the terminal dump handles the first
character, where a space and NUL should be considered equal.  If you can
still reproduce the problem, please check if the upcoming patch fixes
it.

-- 
Managers are like cats in a litter box.  They instinctively shuffle things
around to conceal what they've done.
(Scott Adams - The Dilbert principle)

 /// Bram Moolenaar -- b...@moolenaar.net -- 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 vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Test failure on arch ppc

[Elimar Riesebieter]

* James McCoy  [2018-08-22 07:36 -0400]:

> On Wed, Aug 22, 2018 at 08:10:10AM +0200, Elimar Riesebieter wrote:
> > * James McCoy  [2018-08-21 22:20 -0400]:
> > 
> > > On Wed, Aug 22, 2018 at 03:12:34AM +0200, Elimar Riesebieter wrote:
> > > > Hi all,
> > > > 
> > > > compiling vim 8.1.0315 on arch powerpc gives the following failure:
> > > > 
> > > > From test_cscope.vim:
> > > > Found errors in Test_cscope_add_dir():
> > > > Caught exception in Test_cscope_add_dir(): Vim(cscope):E563: 
> > > > stat(/source/vim/vim-8.1.0315/src/vim-basic/testdir/Xcscopedir/cscope.out)
> > > >  error: 2 @ function RunTheTest[40]..Test_cscope_add_dir, line 3
> > > 
> > > It looks like you're building in a shadow directory.  cscope doesn't
> > > follow symlinks, so the test fails to build a database for
> > > ../memfile_test.c.
> > 
> > Yes, I am building in a shadow dir. But on arch amd64 the tests run
> > fine, though.
> 
> Are you sure you have cscope installed in the amd64 environment?  I just
> had this same failure on amd64, now that I've installed cscope for
> Debian's builds.

Well, installed cscope and ran in to the same failure on amd64.

Elimar
-- 
  We all know Linux is great... it does infinite loops in 5 seconds.
-Linus Torvalds

-- 
-- 
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 vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Test failure on arch i386

[Elimar Riesebieter]

* Bram Moolenaar  [2018-08-22 12:42 +0200]:

> 
> Elimar Riesebieter wrote:
> 
> > > Hi all,
> > > 
> > > compiling vim 8.1.0315 on arch i386 gives the following failure:
> > > 
> > > >From test_search.vim:
> > > Found errors in Test_incsearch_substitute_dump():
> > > function 
> > > RunTheTest[40]..Test_incsearch_substitute_dump[69]..VerifyScreenDump line 
> > > 14: See dump file difference: call 
> > > term_dumpdiff("Test_incsearch_substitute_07.dump.failed", 
> > > "dumps/Test_incsearch_substitute_07.dump")
> > 
> > 
> > The diff is as follows:
> > 
> > 
> > --- ./src/testdir/dumps/Test_incsearch_substitute_07.dump   2018-08-21 
> > 21:58:13.0 +0200
> > +++ ./src/vim-gtk3/testdir/Test_incsearch_substitute_07.dump.failed 
> > 2018-08-22 03:11:40.341265509 +0200
> > @@ -6,4 +6,4 @@
> >  |f|o@1| |9| @64
> >  |f|o@1| |1|0| @63
> >  |b+9&&|a|r| +8&&|1@1| @63
> > -|:+0&&|9|,|1@1|s|/|b|a|r> @59
> > +|:+0&&|9|,|1@1|s|/|b|a|r> @31| @1| @25
> 
> Now that is weird, it's the same number of spaces but encoded
> differently.  Looks like there is some attribute that's different but is
> not reflected in the screendump.  Can you do some debugging on this?
> It's hard for me, since I cannot reproduce it.

A second build in a tmux session ran fine. The first build was in a
detached tmux session. Maybe that was the reason of the failure?

Elimar
-- 
  You cannot propel yourself forward by
  patting yourself on the back.

-- 
-- 
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 vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Test failure on arch i386

[Christian Brabandt]

On Mi, 22 Aug 2018, Bram Moolenaar wrote:

> > --- ./src/testdir/dumps/Test_incsearch_substitute_07.dump   2018-08-21 
> > 21:58:13.0 +0200
> > +++ ./src/vim-gtk3/testdir/Test_incsearch_substitute_07.dump.failed 
> > 2018-08-22 03:11:40.341265509 +0200
> > @@ -6,4 +6,4 @@
> >  |f|o@1| |9| @64
> >  |f|o@1| |1|0| @63
> >  |b+9&&|a|r| +8&&|1@1| @63
> > -|:+0&&|9|,|1@1|s|/|b|a|r> @59
> > +|:+0&&|9|,|1@1|s|/|b|a|r> @31| @1| @25
> 
> Now that is weird, it's the same number of spaces but encoded
> differently.  Looks like there is some attribute that's different but is
> not reflected in the screendump.  Can you do some debugging on this?
> It's hard for me, since I cannot reproduce it.

Looks like a problem I have noticed in #2732
https://github.com/vim/vim/pull/2732#issuecomment-375704176
Look at the diff from the message right above it.

Never found out what the problem was.

Best,
Christian
-- 
Meßgewänder: Das Kostüm der Narren am Himmlischen Hof.
-- Ambrose Gwinnet Bierce (Des Teufels Wörterbuch)

-- 
-- 
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 vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Test failure on arch i386

[Bram Moolenaar]

Elimar Riesebieter wrote:

> > Hi all,
> > 
> > compiling vim 8.1.0315 on arch i386 gives the following failure:
> > 
> > >From test_search.vim:
> > Found errors in Test_incsearch_substitute_dump():
> > function 
> > RunTheTest[40]..Test_incsearch_substitute_dump[69]..VerifyScreenDump line 
> > 14: See dump file difference: call 
> > term_dumpdiff("Test_incsearch_substitute_07.dump.failed", 
> > "dumps/Test_incsearch_substitute_07.dump")
> 
> 
> The diff is as follows:
> 
> 
> --- ./src/testdir/dumps/Test_incsearch_substitute_07.dump   2018-08-21 
> 21:58:13.0 +0200
> +++ ./src/vim-gtk3/testdir/Test_incsearch_substitute_07.dump.failed 
> 2018-08-22 03:11:40.341265509 +0200
> @@ -6,4 +6,4 @@
>  |f|o@1| |9| @64
>  |f|o@1| |1|0| @63
>  |b+9&&|a|r| +8&&|1@1| @63
> -|:+0&&|9|,|1@1|s|/|b|a|r> @59
> +|:+0&&|9|,|1@1|s|/|b|a|r> @31| @1| @25

Now that is weird, it's the same number of spaces but encoded
differently.  Looks like there is some attribute that's different but is
not reflected in the screendump.  Can you do some debugging on this?
It's hard for me, since I cannot reproduce it.

-- 
Mrs Abbott: I'm a paediatrician.
 Basil: Feet?
Mrs Abbott: Children.
 Sybil: Oh, Basil!
 Basil: Well, children have feet, don't they? That's how they move
around, my dear. You must take a look next time, it's most
interesting.   (Fawlty Towers)

 /// Bram Moolenaar -- b...@moolenaar.net -- 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 vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Test failure on arch ppc

[Bram Moolenaar]

James McCoy wrote:

> On Wed, Aug 22, 2018 at 03:12:34AM +0200, Elimar Riesebieter wrote:
> > Hi all,
> > 
> > compiling vim 8.1.0315 on arch powerpc gives the following failure:
> > 
> > From test_cscope.vim:
> > Found errors in Test_cscope_add_dir():
> > Caught exception in Test_cscope_add_dir(): Vim(cscope):E563: 
> > stat(/source/vim/vim-8.1.0315/src/vim-basic/testdir/Xcscopedir/cscope.out) 
> > error: 2 @ function RunTheTest[40]..Test_cscope_add_dir, line 3
> 
> It looks like you're building in a shadow directory.  cscope doesn't
> follow symlinks, so the test fails to build a database for
> ../memfile_test.c.

But it works with a shadow directory on other platforms.
Thus it still looks like it's specific for cscope on arch ppc.
Might be a cscope problem.

-- 
BLACK KNIGHT: I'm invincible!
ARTHUR:   You're a looney.
 "Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD

 /// Bram Moolenaar -- b...@moolenaar.net -- 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 vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Test failure on arch ppc

[Elimar Riesebieter]

* James McCoy  [2018-08-21 22:20 -0400]:

> On Wed, Aug 22, 2018 at 03:12:34AM +0200, Elimar Riesebieter wrote:
> > Hi all,
> > 
> > compiling vim 8.1.0315 on arch powerpc gives the following failure:
> > 
> > From test_cscope.vim:
> > Found errors in Test_cscope_add_dir():
> > Caught exception in Test_cscope_add_dir(): Vim(cscope):E563: 
> > stat(/source/vim/vim-8.1.0315/src/vim-basic/testdir/Xcscopedir/cscope.out) 
> > error: 2 @ function RunTheTest[40]..Test_cscope_add_dir, line 3
> 
> It looks like you're building in a shadow directory.  cscope doesn't
> follow symlinks, so the test fails to build a database for
> ../memfile_test.c.

Yes, I am building in a shadow dir. But on arch amd64 the tests run
fine, though.

Elimar
-- 
  The path to source is always uphill!
-unknown-

-- 
-- 
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 vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Test failure on arch ppc

[Christian Brabandt]

On Di, 21 Aug 2018, James McCoy wrote:

> On Wed, Aug 22, 2018 at 03:12:34AM +0200, Elimar Riesebieter wrote:
> > Hi all,
> > 
> > compiling vim 8.1.0315 on arch powerpc gives the following failure:
> > 
> > From test_cscope.vim:
> > Found errors in Test_cscope_add_dir():
> > Caught exception in Test_cscope_add_dir(): Vim(cscope):E563: 
> > stat(/source/vim/vim-8.1.0315/src/vim-basic/testdir/Xcscopedir/cscope.out) 
> > error: 2 @ function RunTheTest[40]..Test_cscope_add_dir, line 3
> 
> It looks like you're building in a shadow directory.  cscope doesn't
> follow symlinks, so the test fails to build a database for
> ../memfile_test.c.

I wonder why this did not occur earlier.

What is the symbolic link? We should be able to resolve the symbolic 
link in the test before calling cscope.

Best,
Christian
-- 
Einfachheit ist das Resultat der Reife.
-- Friedrich Johann Christoph Schiller

-- 
-- 
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 vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Test failure on arch ppc

[James McCoy]

On Wed, Aug 22, 2018 at 03:12:34AM +0200, Elimar Riesebieter wrote:
> Hi all,
> 
> compiling vim 8.1.0315 on arch powerpc gives the following failure:
> 
> From test_cscope.vim:
> Found errors in Test_cscope_add_dir():
> Caught exception in Test_cscope_add_dir(): Vim(cscope):E563: 
> stat(/source/vim/vim-8.1.0315/src/vim-basic/testdir/Xcscopedir/cscope.out) 
> error: 2 @ function RunTheTest[40]..Test_cscope_add_dir, line 3

It looks like you're building in a shadow directory.  cscope doesn't
follow symlinks, so the test fails to build a database for
../memfile_test.c.

Cheers,
-- 
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7  2D23 DFE6 91AE 331B A3DB

-- 
-- 
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 vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Test failure on arch i386

[Elimar Riesebieter]

* Elimar Riesebieter  [2018-08-22 03:16 +0200]:

> Hi all,
> 
> compiling vim 8.1.0315 on arch i386 gives the following failure:
> 
> >From test_search.vim:
> Found errors in Test_incsearch_substitute_dump():
> function RunTheTest[40]..Test_incsearch_substitute_dump[69]..VerifyScreenDump 
> line 14: See dump file difference: call 
> term_dumpdiff("Test_incsearch_substitute_07.dump.failed", 
> "dumps/Test_incsearch_substitute_07.dump")


The diff is as follows:


--- ./src/testdir/dumps/Test_incsearch_substitute_07.dump   2018-08-21 
21:58:13.0 +0200
+++ ./src/vim-gtk3/testdir/Test_incsearch_substitute_07.dump.failed 
2018-08-22 03:11:40.341265509 +0200
@@ -6,4 +6,4 @@
 |f|o@1| |9| @64
 |f|o@1| |1|0| @63
 |b+9&&|a|r| +8&&|1@1| @63
-|:+0&&|9|,|1@1|s|/|b|a|r> @59
+|:+0&&|9|,|1@1|s|/|b|a|r> @31| @1| @25


-- 
  "Talking much about oneself can also
   be a means to conceal oneself."
 -Friedrich Nietzsche

-- 
-- 
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 vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Test failure on arch i386

[Elimar Riesebieter]

Hi all,

compiling vim 8.1.0315 on arch i386 gives the following failure:

>From test_search.vim:
Found errors in Test_incsearch_substitute_dump():
function RunTheTest[40]..Test_incsearch_substitute_dump[69]..VerifyScreenDump 
line 14: See dump file difference: call 
term_dumpdiff("Test_incsearch_substitute_07.dump.failed", 
"dumps/Test_incsearch_substitute_07.dump")


Elimar
-- 
  "Talking much about oneself can also
   be a means to conceal oneself."
 -Friedrich Nietzsche

-- 
-- 
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 vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Test failure on arch ppc

[Elimar Riesebieter]

Hi all,

compiling vim 8.1.0315 on arch powerpc gives the following failure:

>From test_cscope.vim:
Found errors in Test_cscope_add_dir():
Caught exception in Test_cscope_add_dir(): Vim(cscope):E563: 
stat(/source/vim/vim-8.1.0315/src/vim-basic/testdir/Xcscopedir/cscope.out) 
error: 2 @ function RunTheTest[40]..Test_cscope_add_dir, line 3



Elimar
-- 
  "Talking much about oneself can also
   be a means to conceal oneself."
 -Friedrich Nietzsche

-- 
-- 
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 vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Test failure on linux-powerpc v8.0.1670

[Bram Moolenaar]

Elimar Riesebieter wrote:

> > From test_terminal.vim:
> > Found errors in Test_terminal_api_drop_newwin_fileformat():
> > Caught exception in Test_terminal_api_drop_newwin_fileformat(): WaitFor() 
> > timed out after 2000 msec @ function 
> > RunTheTest[38]..Test_terminal_api_drop_newwin_fileformat[4]..Api_drop_common[12]..WaitFor,
> >  line 25
> 
> Increase call wait for to 5000 in test_terminal.vim seems to fix it so far:

Hmm, OK.  That's a very long time though, there must be something that
causes the long delay.  If you try something like by hand, do you notice
a delay?

-- 
Would you care for a drink?   I mean, if it were, like,
disabled and you had to look after it?

 /// Bram Moolenaar -- b...@moolenaar.net -- 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 vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Test failure on linux-powerpc v8.0.1670

[Bram Moolenaar]

Elimar Riesebieter wrote:

> From test_terminal.vim:
> Found errors in Test_terminal_api_drop_newwin_fileformat():
> Caught exception in Test_terminal_api_drop_newwin_fileformat(): WaitFor() 
> timed out after 2000 msec @ function 
> RunTheTest[38]..Test_terminal_api_drop_newwin_fileformat[4]..Api_drop_common[12]..WaitFor,
>  line 25
> 
> 
> Builds on amd64 and i386 ran fine.

I haven't been able to reproduce this failure and similar ones with
"api_drop".  It also fails on Travis sometimes. I am looking forward to
get a hint on how to reproduce this failure.

Note that the similar _ff and _enc tests pass, but the _fileformat and
_encoding tests, which do exactly the same thing, then fail.  Maybe the
previous test wasn't completely finished somehow?

-- 
hundred-and-one symptoms of being an internet addict:
121. You ask for e-mail adresses instead of telephone numbers.

 /// Bram Moolenaar -- b...@moolenaar.net -- 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 vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Test failure on linux-powerpc v8.0.1670

[Elimar Riesebieter]

* Elimar Riesebieter  [2018-04-07 13:20 +0200]:

> >From test_terminal.vim:
> Found errors in Test_terminal_api_drop_newwin_fileformat():
> Caught exception in Test_terminal_api_drop_newwin_fileformat(): WaitFor() 
> timed out after 2000 msec @ function 
> RunTheTest[38]..Test_terminal_api_drop_newwin_fileformat[4]..Api_drop_common[12]..WaitFor,
>  line 25

Increase call wait for to 5000 in test_terminal.vim seems to fix it so far:

>From 27c1ef8d2c47d33f9723f4f619c1be6783af91d4 Mon Sep 17 00:00:00 2001
From: Elimar Riesebieter 
Date: Sat, 7 Apr 2018 16:19:00 +0200
Subject: [PATCH] Increase call wait for to 5000 in test_terminal.vim

---
 src/testdir/test_terminal.vim | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/testdir/test_terminal.vim b/src/testdir/test_terminal.vim
index cd7a2b21e..5645625cb 100644
--- a/src/testdir/test_terminal.vim
+++ b/src/testdir/test_terminal.vim
@@ -1061,7 +1061,7 @@ func Api_drop_common(options)
\ "set t_ts=",
\ ], 'Xscript')
   let buf = RunVimInTerminal('-S Xscript', {})
-  call WaitFor({-> bufnr('Xtextfile') > 0}, 2000)
+  call WaitFor({-> bufnr('Xtextfile') > 0}, 5000)
   call assert_equal('Xtextfile', expand('%:t'))
   call assert_true(winnr('$') >= 3)
   return buf
-- 
2.17.0


-- 
  Numeric stability is probably not all that
  important when you're guessing;-)

-- 
-- 
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 vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Test failure on linux-powerpc v8.0.1670

[Elimar Riesebieter]

>From test_terminal.vim:
Found errors in Test_terminal_api_drop_newwin_fileformat():
Caught exception in Test_terminal_api_drop_newwin_fileformat(): WaitFor() timed 
out after 2000 msec @ function 
RunTheTest[38]..Test_terminal_api_drop_newwin_fileformat[4]..Api_drop_common[12]..WaitFor,
 line 25


Builds on amd64 and i386 ran fine.

Elimar
-- 
  >what IMHO then?
  IMHO - Inhalation of a Multi-leafed Herbal Opiate ;)
  --posting from alex in debian-user--

-- 
-- 
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 vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: test failure in Test_quoteplus()

[tooth pik]

I've got xclip installed but I don't think it runs as a background
process, you have to invoke it to use it

On Tue, Mar 27, 2018 at 1:46 AM, Chr. von Stuckrad 
wrote:

> On Mon, 26 Mar 2018, tooth pik wrote:
>
> > function RunTheTest[38]..Test_quoteplus line 35: Expected 'Yes, I can.'
> but
> > got 'Can you hear me?'
>
> I had some 'Can you hear me' a while ago in LINUX. Those went away after
> I killed all 'clipboard managers' (in my case 'diodon' or 'glipper').
> They seem to grab the contents and vim then blocks.
>
> Stucki
>
> --
> Christoph von Stuckrad* * | also XMPP = |Mail 
> \
> Freie Universitaet Berlin |/_*| 'jabber' via|Tel(Mo.,Mi.):+49 30 838-75
> 459|
> IT Mathematik & Informatik|\ *|stucki@jabber|  (Di,Do,Fr):+49 30 77 39
> 6600|
> Takustr. 9 / 14195 Berlin * * |.fu-berlin.de|Fax(home):   +49 30 77 39
> 6601/
>
>
> --
> --
> 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 vim_dev+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
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 vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.