Re: Damn race conditions ...

[Bart Schaefer <schaefer@brasslantern.com>]

On Mar 17, 10:54pm, Jun T. wrote:
}
} 2014/03/17 06:15, Bart Schaefer <schaefer@brasslantern.com> wrote:
} 
} > This is still happening sporadically:
} 
} What OS (and hardware) are you using?

It's a 64bit virtualbox VM running 32bit CentOS 4.9.  Failed 16 out of
200 times when I ran it in a loop.  On the host hardware (quad-core
Intel i3, ubuntu 12.04.4) it failed only 1 out of 100.

  { repeat 100 make check TESTNUM=X02 } |& grep -c '[1-9] failure'

} (I guess you have already tried uncommenting all of zpty_flush)

You mean uncommenting the other 3 calls to zpty_flush?  Yes.  It
still fails sometimes (I didn't bother running the full hundreds
of passes).

} What happens if you modify the test as follows (i.e., add a text
} after 'redo') ?

Applied that patch, but still get occasional failure.

OF course it's not consistent WHERE it failes, so patching any one test
is not likely to help.  E.g., in this most recent try the failure is
here:

../../zsh-5.0/Test/X02zlevi.ztst: starting.
*** /tmp/zsh.ztst.out.30213     Mon Mar 17 17:44:32 2014
--- /tmp/zsh.ztst.tout.30213    Mon Mar 17 17:44:32 2014
***************
*** 1,2 ****
! BUFFER: binging
! CURSOR: 3
--- 1,3 ----
! BUFFER: ing
! ing
! CURSOR: 6
Test ../../zsh-5.0/Test/X02zlevi.ztst failed: output differs from expected as
shown above for:
  comptesteval 'setopt overstrike;print -z bung'
  zletest $'ing\e2|.'
Was testing: repeat initial edit with overstrike set
../../zsh-5.0/Test/X02zlevi.ztst: test failed.