Re: [patch, testsuite] Fixes for gdb.python tests on remote Windows host

[Sandra Loosemore <sandra at codesourcery dot com>]

On 8/12/19 8:54 PM, Simon Marchi wrote:
> On 2019-08-12 10:18 p.m., Sandra Loosemore wrote:
> > I believe they are completely separate targets.  I don't know much about
> > cygwin, but I assume that Python built for cygwin library is linked with
> > the cygwin C library and understands cygwin's fake symbolic links, while
> > Python built for the mingw C library certainly does not.  Similarly,
> > using ";" instead of ":" in PATH-like things is a Windows thing, while
> > I'm pretty sure cygwin emulates the POSIX syntax.
>
> Indeed, testing on cygwin would be a whole other task.
>
> I forgot to mention, the patch LGTM, so if Christian is fine with this response too, then please push.

Thanks for the speedy review!  I fixed the indentation problem you noted 
before pushing the patch.

BTW, these are not the only issues I noticed in running the Python tests 
on Windows host.  There's another set involving the "explore" command 
and the python interactive help which fail with timeouts because the 
expected output is getting buffered.  At this point I'm not sure whether 
this is a problem with our test environment (we use cygwin ssh, which 
native Windows doesn't recognize as a tty), or some misconfiguration in 
the version of Windows python we are using.  I've got a local patch to 
temporarily disable those tests to speed up testing, but I don't think 
that's a good fix for mainline.  It would be better to figure out how to 
force Python to unbuffer the output.

-Sandra