Re: cond_wait hang ups under MSWin32

Jerry D. Hedden wrote:
> Also, should the test be skipped/TODOed under Win32
until
> the problem is fixed?

Yves wrote::
> We should todo it, although maybe only under smoke
testing.
>
> Use an environment variable. Something like
> WIN32_SMOKE_SKIP_THREADS or something. People who need
it
> can set it up in a wrapper script.

Jerry D. Hedden wrote:
> Patch attached.  If $ENV{'WIN32_SMOKE'} is true, then
the
> offending tests will be set TODO.

Steve Hay wrote:
> I'm not sure that it makes sense to only mark a test as
TODO when run
> under Test-Smoke.
>
> Surely any test that is known to fail should be marked
as TODO
> regardless of how the test is being run.

Okay.  Then is the concensus that it should just be based
on
'$^O eq MSWin32'?

Jerry D. Hedden wrote:
> Also, should the test be skipped/TODOed under Win32
until
> the problem is fixed?

Yves wrote::
> We should todo it, although maybe only under smoke
testing.
>
> Use an environment variable. Something like
> WIN32_SMOKE_SKIP_THREADS or something. People who need
it
> can set it up in a wrapper script.

Jerry D. Hedden wrote:
> Patch attached.  If $ENV{'WIN32_SMOKE'} is true, then
the
> offending tests will be set TODO.

Steve Hay wrote:
> I'm not sure that it makes sense to only mark a test as
TODO when run
> under Test-Smoke.
>
> Surely any test that is known to fail should be marked
as TODO
> regardless of how the test is being run.

Jerry D. Hedden wrote:
> Okay.  Then is the concensus that it should just be
based on
> '$^O eq MSWin32'?

Attached patch does this.