|
From: Matt E. <ma...@gs...> - 2004-03-06 05:00:51
|
Using the latest version from CVS, I get a different set of failures. It builds successfully, but running "tests/vg_regtest --all" fails with 4 failures. The pth_cancel2 and inherit failures are the same in v2.1.0. I will start working on tracking these failures down. == 125 tests, 2 stderr failures, 2 stdout failures ================= corecheck/tests/pth_cancel2 (stderr) corecheck/tests/res_search (stdout) helgrind/tests/inherit (stderr) memcheck/tests/pth_once (stdout) *** pth_cancel2.stderr.exp 2002-11-18 06:33:37.000000000 -0500 --- pth_cancel2.stderr.out 2004-03-05 23:38:49.000000000 -0500 *************** *** 1 **** --- 2 ---- + write: Interrupted system call *** res_search.stdout.exp 2003-07-04 12:16:51.000000000 -0400 --- res_search.stdout.out 2004-03-05 23:39:04.000000000 -0500 *************** *** 1 **** - Success! --- 0 ---- *** inherit.stderr.exp 2003-10-18 18:27:10.000000000 -0400 --- inherit.stderr.out 2004-03-05 23:39:19.000000000 -0500 *************** *** 1 **** ! XXX We expect an error on inherit.c:48 --- 1,2 ---- ! ! *** pth_once.stdout.exp 2003-10-30 04:11:03.000000000 -0500 --- pth_once.stdout.out 2004-03-05 23:41:38.000000000 -0500 *************** *** 11 **** - identify_yourself: Hi, I'm thread # 9 --- 10 ---- *************** *** 20 **** --- 20 ---- + identify_yourself: Hi, I'm thread # 9 |
|
From: Tom H. <th...@cy...> - 2004-03-06 07:54:27
|
In message <002601c40336$8f4752f0$120...@gs...>
"Matt Emmerton" <ma...@gs...> wrote:
> *** pth_cancel2.stderr.exp 2002-11-18 06:33:37.000000000 -0500
> --- pth_cancel2.stderr.out 2004-03-05 23:38:49.000000000 -0500
> ***************
> *** 1 ****
> --- 2 ----
> + write: Interrupted system call
This one doesn't always happen in my experience, but does happen on
a percentage of runs. I think it's some sort of race condition but it
doesn't seem to make any sense to me as my reading of the pthreads
doco says that the writ should never return if it is cancelled.
I've also only ever seen this on RH9 which makes me suspect some sort
of kernel or glibc bug.
> *** res_search.stdout.exp 2003-07-04 12:16:51.000000000 -0400
> --- res_search.stdout.out 2004-03-05 23:39:04.000000000 -0500
> ***************
> *** 1 ****
> - Success!
> --- 0 ----
I haven't seen this in an recent RH9 builds.
> *** inherit.stderr.exp 2003-10-18 18:27:10.000000000 -0400
> --- inherit.stderr.out 2004-03-05 23:39:19.000000000 -0500
> ***************
> *** 1 ****
> ! XXX We expect an error on inherit.c:48
> --- 1,2 ----
> !
> !
This fails everywhere and is an expected failure.
> *** pth_once.stdout.exp 2003-10-30 04:11:03.000000000 -0500
> --- pth_once.stdout.out 2004-03-05 23:41:38.000000000 -0500
> ***************
> *** 11 ****
> - identify_yourself: Hi, I'm thread # 9
> --- 10 ----
> ***************
> *** 20 ****
> --- 20 ----
> + identify_yourself: Hi, I'm thread # 9
I've haven't seen this one either - it looks like that line has
moved in the output though - maybe a race between two threads?
Tom
--
Tom Hughes (th...@cy...)
Software Engineer, Cyberscience Corporation
http://www.cyberscience.com/
|