make check

[Parmelan, Edouard]

Alice,

> When I run make check on my red-hat Linux, everything is correct (except 
> UDPTest: UDPTest ... output saved to UDPTest.fail) until ExecTest. When
this
>  test arrives, it stops and I must press "control C" to continue.
> TestScript and TestScriptThread : FAIL
I don't know for UDPTest, but for ExecTest I have the same
problem with GNU/Linux.

That's not realy a problem, in fact in test/regression there
are a lot of files know (for each test there is a TEST.out file).

ExecTest run /bin/ls.

The output of /bin/ls is a pipe but ExecTest don't read it, it
just wait for the end of /bin/ls.

But /bin/ls is blocked until it could write again in the pipe :(
As the reader of this pipe don't read it, /bin/ls is blocked for
ever.  This is a deadlock !

Edouard.


> 
> .
> MarkResetTest ... passed
> HashtableTest1 ... passed
> FAIL: TestScript
> ExecTest (I press control C here) ... ERROR: output saved to ExecTest.fail
> CatchDeath ... ignored
> ThreadStop ... ignored
> DeadThread ... passed
> tthrd1 ... passed
> FAIL: TestScriptThread
> ===================
> 2 of 2 tests failed
> ===================
> make[3]: *** [check-TESTS] Error 1
> make[2]: *** [check-am] Interruption.
> make[1]: *** [check-recursive] Interruption.
> make: *** [check-recursive] Interruption.  
> 
> What Can I do ?
> 
> Thanks,
> 
> Alice