This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: ARM port of testsuite and general testsuite fixes
I'll comment on a few test cases that I'm familiar with.
=======
$ egrep '^(FAIL|XPASS)' systemtap.log
FAIL: BASIC2 wasn't cached
FAIL: OPTION2 wasn't cached
FAIL: BULK2 wasn't cached
FAIL: MERGE2 wasn't cached
FAIL: RUNTIME2 wasn't cached
FAIL: BASIC4 wasn't cached
Hmm, those are odd. Those are related to caching problems, which should
be platform agnostic. Can you send me the full log of the run of
systemtap.base/cache.exp?
There wasn't that much in the log:
=====
testcase /usr/src/systemtap-20070602/testsuite/systemtap.base/bench.exp completed in 143 seconds
Running /usr/src/systemtap-20070602/testsuite/systemtap.base/cache.exp ...
PASS: BASIC1 wasn't cached
FAIL: BASIC2 wasn't cached
PASS: OPTION1 wasn't cached
FAIL: OPTION2 wasn't cached
PASS: BULK1 wasn't cached
FAIL: BULK2 wasn't cached
PASS: MERGE1 wasn't cached
FAIL: MERGE2 wasn't cached
PASS: RUNTIME1 wasn't cached
FAIL: RUNTIME2 wasn't cached
Warning: failed to create systemtap data directory ("/dev/null"): Not a directory^M
Disabling cache support.^M
PASS: DISABLED1 wasn't cached
Warning: failed to create systemtap data directory ("/dev/null"): Not a directory^M
Disabling cache support.^M
PASS: DISABLED2 wasn't cached
Warning: using '-m' disables cache support.^M
PASS: MODNAM1 wasn't cached
Warning: using '-m' disables cache support.^M
PASS: MODNAM2 wasn't cached
PASS: ERROR1 wasn't cached
PASS: ERROR2 wasn't cached
PASS: BASIC3 wasn't cached
FAIL: BASIC4 wasn't cached
testcase /usr/src/systemtap-20070602/testsuite/systemtap.base/cache.exp completed in 183 seconds
=====
In hopes of getting more info, I reran it with:
=====
# runtest --all --verbose --verbose --tool_opts=install \
--tool systemtap --srcdir "/usr/src/systemtap-20070602/testsuite" \
systemtap.base/cache.exp
Running /usr/src/systemtap-20070602/testsuite/systemtap.base/cache.exp ...
PASS: BASIC1 wasn't cached
FAIL: BASIC2 wasn't cached
PASS: OPTION1 wasn't cached
FAIL: OPTION2 wasn't cached
PASS: BULK1 wasn't cached
FAIL: BULK2 wasn't cached
PASS: MERGE1 wasn't cached
FAIL: MERGE2 wasn't cached
ERROR: tcl error sourcing /usr/src/systemtap-20070602/testsuite/systemtap.base/cache.exp.
ERROR: can't read "env(SYSTEMTAP_RUNTIME)": no such variable
while executing
"exec /bin/ln -s $env(SYSTEMTAP_RUNTIME) $new_runtime"
(file "/usr/src/systemtap-20070602/testsuite/systemtap.base/cache.exp" line 105)
invoked from within
"source /usr/src/systemtap-20070602/testsuite/systemtap.base/cache.exp"
("uplevel" body line 1)
invoked from within
"uplevel #0 source /usr/src/systemtap-20070602/testsuite/systemtap.base/cache.exp"
invoked from within
"catch "uplevel #0 source $test_file_name""
=====
Grumble. It looks like this test is expecting to be invoked
from the Makefile only. Is this a legal assumption? There's no
supported way to run some tests directly outside of the Makefile,
or is this test busted?
FAIL: OVERLOAD2 didn't receive expected overload
This one probably needs adjusting for arm. It expects the background
system processing to cause the systemtap script to overload (since the
overload parameters have been dramatically lowered).
Can you send me the full log of the run of systemtap.base/overload.exp?
There's Martin's note on this that may be the problem, but here is the
log just in case. Not much here:
=====
Running /usr/src/systemtap-20070602/testsuite/systemtap.base/overload.exp ...
Pass 1: parsed user script and 53 library script(s) in 8530usr/8900sys/17441real ms.^M
Pass 2: analyzed script: 4 probe(s), 0 function(s), 0 embed(s), 1 global(s) in 4420usr/36630sys/86859real ms.^M
Pass 3: translated to C into "/tmp/stap7ZpRAI/stap_49444f1d762d7dd03f9f1261927c6901_685.c" in 20usr/410sys/593real ms.^M
Pass 4: compiled C into "stap_49444f1d762d7dd03f9f1261927c6901_685.ko" in 87270usr/25880sys/124170real ms.^M
Pass 5: starting run.^M
systemtap starting probe^M
systemtap ending probe^M
Pass 5: run completed in 380usr/2200sys/4515real ms.^M
PASS: OVERLOAD1 didn't overload
Pass 1: parsed user script and 53 library script(s) in 8690usr/9790sys/19363real ms.^M
Pass 2: analyzed script: 4 probe(s), 0 function(s), 0 embed(s), 1 global(s) in 4570usr/29450sys/79570real ms.^M
Pass 3: translated to C into "/tmp/stapNwKXnw/stap_1e3558f4d38ba9c8739da2d566aeac82_741.c" in 50usr/500sys/617real ms.^M
Pass 4: compiled C into "stap_1e3558f4d38ba9c8739da2d566aeac82_741.ko" in 87560usr/27490sys/120262real ms.^M
Pass 5: starting run.^M
systemtap starting probe^M
systemtap ending probe^M
Pass 5: run completed in 400usr/2750sys/6657real ms.^M
FAIL: OVERLOAD2 didn't receive expected overload
Pass 1: parsed user script and 53 library script(s) in 8580usr/9820sys/18982real ms.^M
Pass 2: analyzed script: 4 probe(s), 0 function(s), 0 embed(s), 1 global(s) in 4050usr/29450sys/38291real ms.^M
Pass 3: translated to C into "/tmp/stappxKjB8/stap_9b34ad72d58a658e7a328026dcd15944_756.c" in 30usr/410sys/503real ms.^M
Pass 4: compiled C into "stap_9b34ad72d58a658e7a328026dcd15944_756.ko" in 86170usr/27310sys/117645real ms.^M
Pass 5: starting run.^M
systemtap starting probe^M
systemtap ending probe^M
PASS: OVERLOAD3 didn't overload
testcase /usr/src/systemtap-20070602/testsuite/systemtap.base/overload.exp completed in 656 seconds
=====
Is this helpful? Is there a way to rerun it to get more info out of it?
--
David Smith
dsmith@redhat.com
Red Hat
http://www.redhat.com
256.217.0141 (direct)
256.837.0057 (fax)
Quentin