Followed the differences found by Qian and verified none of them (did
not verify the ppc suspicious one) has any regression in GDB testsuite.
I did not reproduce the original possible regression seen on ppc64 RHEL6
systems. The kernel was build directly from roland's git tree with and without
On Wed, 25 Nov 2009 23:30:37 +0100, Jan Kratochvil wrote:
Please point at some built or easily buildable kernel .rpm first.
http://kojipkgs.fedoraproject.org/scratch/roland/task_1825649/
OK, taken for reverification.
Followed the differences found by Qian and verified none of them (did
On Sun, 29 Nov 2009 23:39:59 +0100, Jan Kratochvil wrote:
Followed the differences found by Qian and verified none of them (did not
verify the ppc suspicious one) has any regression in GDB testsuite.
Forgot the log FYI.
Regards,
Jan
-result-2.6.31.5-127.fc12.x86_64/gdb
On Wed, Nov 25, 2009 at 01:17:15PM -0800, Roland McGrath wrote:
That's certainly good to hear. If you are pretty confident about that,
then I am quite happy to consider nonregression on all of ptrace-tests the
sole gating test for kernel changes. We just don't want to wind up having
other
On Fri, 27 Nov 2009 15:11:09 +0100, Veaceslav Falico wrote:
-FAIL: gdb.base/foll-fork.exp: unpatch child, unpatched parent breakpoints
from child (timeout)
+PASS: gdb.base/foll-fork.exp: unpatch child, unpatched parent breakpoints
from child
-PASS: gdb.base/foll-fork.exp: set follow parent,
On 11/27, Veaceslav Falico wrote:
On Wed, Nov 25, 2009 at 01:17:15PM -0800, Roland McGrath wrote:
That's certainly good to hear. If you are pretty confident about that,
then I am quite happy to consider nonregression on all of ptrace-tests the
sole gating test for kernel changes. We
On Fri, 27 Nov 2009 15:34:05 +0100, Oleg Nesterov wrote:
Jan, if you see something particular which needs more attention or should
be fixed, please let me know. I'll try to investigate then.
I am still not finished with the verifications yesterday but so far no kernel
behavior change has been
First of all, thanks Ananth and Cai for help!
Jan, I need your help ;)
looking at different reports I can't understand how to interpret them.
To the point, I do not understand if the overall results are good or bad.
The first question, are these tests supposed to be stable?
For example,
In general everything where is a word thread has unstable results and
nonstop tests are also a bit unstable.
So where exactly is the problem in these cases? Are the tests overly
timing-sensitive where there is no actual behavior bug? Or is gdb overly
timing-sensitive where there is no actual
On Wed, 25 Nov 2009 22:17:15 +0100, Roland McGrath wrote:
In general everything where is a word thread has unstable results and
nonstop tests are also a bit unstable.
So where exactly is the problem in these cases? Are the tests overly
timing-sensitive where there is no actual behavior
10 matches
Mail list logo