This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: Test result on Fedora release 12 64bits
- From: Mark Wielaard <mjw at redhat dot com>
- To: wenji dot huang at oracle dot com
- Cc: SystemTAP <systemtap at sources dot redhat dot com>
- Date: Tue, 01 Dec 2009 11:55:05 +0100
- Subject: Re: Test result on Fedora release 12 64bits
- References: <4B1382C1.3020202@oracle.com>
Hi Wenji,
On Mon, 2009-11-30 at 16:30 +0800, Wenji Huang wrote:
> Host: Linux localhost.localdomain 2.6.31.5-127.fc12.x86_64 #1 SMP Sat
> Nov 7 21:11:14 EST 2009 x86_64 x86_64 x86_64 GNU/Linux
> Snapshot: version 1.0/0.143 commit release-1.0-249-g508968a
> GCC: 4.4.2 [gcc (GCC) 4.4.2 20091027 (Red Hat 4.4.2-7)]
> Distro: Fedora release 12 (Constantine)
I haven't upgraded to F12 yet, will do so in a minute, but if the
failures you are seeing aren't local issues, we do have a lot of
regressions :{ Just ran on F11 with kernel 2.6.30.9-99.fc11.x86_64 and
elfutils 0.142 against systemtap git tip and only saw 7 failures.
> FAIL: backtrace-unwindsyms (0 0)
> FAIL: bad kprobe registration: kernel.statement(-1).absolute (timeout)
> FAIL: bad kprobe registration: kprobe.function("no_such_function") (timeout)
> FAIL: bad optional kprobe registration: kernel.statement(-1).absolute
> (timeout)
> FAIL: beginenderror (timeout)
> FAIL: beginenderror (0 0 0)
> FAIL: bz10078 -p5 (2)
All the above pass for me.
> FAIL: empty-struct resolve-pass compilation failed
This is http://sourceware.org/bugzilla/show_bug.cgi?id=10732
> FAIL: optionalprobe unexpected timeout
> FAIL: overflow_error timed out
> FAIL: overflow_error (0)
> FAIL: sdt "" uprobe
> FAIL: sdt c++ additional_flags=-O2 uprobe
> FAIL: sdt "" utrace
These all pass for me.
> FAIL: skip tracking (timeout)
> FAIL: skip tracking (2 0)
This one also fails for me as:
FAIL: skip tracking (8 0)
> FAIL: systemtap.base/timers.stp shutdown (eof)
This one passes for me.
> FAIL:
> lib-uprobesgcc-O3default-pie-sep-debug-uprobeslibgcc-O3default-prelink-sep-debug_uprobeslibgcc-O3default-prelink-sep-debug
> (0)
> FAIL:
> mark-uprobesgcc-O3default-pie-sep-debug-uprobeslibgcc-O3default-prelink-sep-debug_uprobeslibgcc-O3default-prelink-sep-debug
> (0)
> FAIL:
> uname-uprobesgcc-O3default-pie-sep-debug-uprobeslibgcc-O3default-prelink-sep-debug_uprobeslibgcc-O3default-prelink-sep-debug
> (0)
> FAIL:
> ustack-uprobesgcc-O3default-pie-sep-debug-uprobeslibgcc-O3default-prelink-sep-debug_uprobeslibgcc-O3default-prelink-sep-debug
> print (0)
> FAIL:
> ustack-uprobesgcc-O3default-pie-sep-debug-uprobeslibgcc-O3default-prelink-sep-debug_uprobeslibgcc-O3default-prelink-sep-debug
> main (0)
> FAIL:
> ustack-uprobesgcc-O3default-pie-sep-debug-uprobeslibgcc-O3default-prelink-sep-debug_uprobeslibgcc-O3default-prelink-sep-debug
> main_func (0)
> FAIL:
> ustack-uprobesgcc-O3default-pie-sep-debug-uprobeslibgcc-O3default-prelink-sep-debug_uprobeslibgcc-O3default-prelink-sep-debug
> lib_main (0)
> FAIL:
> ustack-uprobesgcc-O3default-pie-sep-debug-uprobeslibgcc-O3default-prelink-sep-debug_uprobeslibgcc-O3default-prelink-sep-debug
> lib_func (0)
You might be able to track down what this is by running the separate
tests indivudally (which takes a bit more time). Edit
testsuite/systemtap.exelib/exelib.exp:
# Don't enable all sub-tests by default, enable them separately when
# you want to track down an issue.
# Enable just the all-in-one test for regular test runs to safe time
#set subtestlist {lib mark uname ustack cleanup}
set subtestlist {libmarkunamestack cleanup}
The libmarkunamestack tests combines all of the separate tests in one
big test.
> FAIL: systemtap.stress/current.stp startup (timeout)
I am seeing some failures you aren't seeing:
FAIL: flightrec5 (failed to remove output file)
FAIL: function arguments: unexpected timeout
FAIL: systemtap.examples/process/sleepingBeauties run
FAIL: buildok/process_test.stp
FAIL: buildok/tty.stp
I'll upgrade my machine to F12 and see what happens.
Cheers,
Mark