From: Wenji Huang <wenji.huang@oracle.com>
To: systemTAP <systemtap@sources.redhat.com>
Cc: elena Zannoni <elena.zannoni@oracle.com>,
"VAN HEES,KRIS" <kris.van.hees@oracle.com>
Subject: 2.6.28-rc4 test results
Date: Fri, 14 Nov 2008 02:39:00 -0000 [thread overview]
Message-ID: <491CE34E.1070808@oracle.com> (raw)
Hi,
These are test results on 2.6.28-rc4 from labrat. In fact, stap couldn't
work on 2.6.28-rc4 due to kernel change in include/linux/cpumask.h.
+#define for_each_cpu(cpu, mask) \
+ for ((cpu) = 0; (cpu) < 1; (cpu)++, (void)mask)
in commit cb56d98e2a7530615899597551db685d68a2e852.
Unfortunately, Stap has own for_each_cpu macro in runtime/runtime.h
The conflict will cause compilation error even the simplest script like
'probe begin{}'. To make test running, I temporarily disabled kernel
for_each_cpu macro. Maybe this will affect test results.
Anyway, the problem needs a long term solution. Maybe we can get rid of
for_each_cpu, use for_each_cpu_mask directed.
Regards,
Wenji
------------------------------------------------------------------------------
Package: systemtap_snapshot
(0.7.1/0.131-master(589db2fc)-2.6.28_rc4-snapshot)
Previous build: 2008/11/03 09:15:54 - 2008/11/03 09:15:54
Current build: 2008/11/11 02:25:03 - 2008/11/11 02:25:03
Host: rctest-32
Platform: Linux 2.6.28-rc4 i386 (EL4U6) (before: Linux 2.6.28-rc3
i386 (EL4U6))
URL:
http://build.alchar.org/cgi/showBuild?host=rctest-32&pkg=systemtap_snapshot&date=20081111-022503
First failure: test
Test result: 823: 760 +, 34 -, 29 S, 0 E (before: 825: 760 +, 36 -,
29 S, 0 E)
Old -> New Test
----- ----- ----------------------------------
PASS -> FAIL test - systemtap.syscall/syscall.exp(32-bit alarm)
FAIL -> PASS test - systemtap.syscall/syscall.exp(32-bit uid16)
FAIL -> PASS test - systemtap.syscall/syscall.exp(32-bit unlink)
FAIL -> N/A test -
systemtap.stress/current.exp(systemtap.stress/current.stp shutdown)
N/A -> PASS test -
systemtap.stress/current.exp(systemtap.stress/current.stp shutdown and
output)
PASS -> FAIL test - systemtap.syscall/syscall.exp(32-bit dir)
FAIL -> PASS test - systemtap.syscall/syscall.exp(32-bit select)
PASS -> FAIL test - systemtap.syscall/syscall.exp(32-bit stat)
FAIL -> N/A test -
systemtap.examples/check.exp(systemtap.examples/general/para-callgraph run)
FAIL -> PASS test - systemtap.syscall/syscall.exp(32-bit mmap)
PASS -> FAIL test - systemtap.syscall/syscall.exp(32-bit chmod)
FAIL -> PASS test - systemtap.syscall/syscall.exp(32-bit acct)
PASS -> N/A test -
systemtap.examples/check.exp(systemtap.examples/profiling/functioncallcount
run)
PASS -> FAIL test - systemtap.syscall/syscall.exp(32-bit clock)
------------------------------------------------------------------------------
Package: systemtap_snapshot
(0.7.1/0.131-master(589db2fc)-2.6.28_rc4-snapshot)
Previous build: 2008/11/04 09:47:14 - 2008/11/04 09:47:14
Current build: 2008/11/11 09:55:56 - 2008/11/11 09:55:56
Host: rctest-64
Platform: Linux 2.6.28-rc4 x86_64 (EL5.2) (before: Linux
2.6.28-rc3 x86_64 (EL5.2))
URL:
http://build.alchar.org/cgi/showBuild?host=rctest-64&pkg=systemtap_snapshot&date=20081111-095556
First failure: test
Test result: 854: 787 +, 36 -, 31 S, 0 E (before: 854: 793 +, 30 -,
31 S, 0 E)
Old -> New Test
----- ----- ----------------------------------
N/A -> FAIL test - systemtap.syscall/syscall.exp(64-bit alarm)
FAIL -> N/A test - systemtap.syscall/syscall.exp(64-bit dir)
N/A -> FAIL test - systemtap.syscall/syscall.exp(64-bit link)
PASS -> N/A test - systemtap.syscall/syscall.exp(alarm)
PASS -> FAIL test - systemtap.base/global_end.exp(global_end)
PASS -> FAIL test - systemtap.samples/queue_demo.exp(queue_demo)
N/A -> PASS test - systemtap.syscall/syscall.exp(dir)
PASS -> N/A test - systemtap.syscall/syscall.exp(net1)
PASS -> FAIL test - systemtap.syscall/syscall.exp(32-bit umask)
PASS -> N/A test - systemtap.syscall/syscall.exp(link)
PASS -> FAIL test - systemtap.syscall/syscall.exp(32-bit timer)
N/A -> FAIL test - systemtap.syscall/syscall.exp(64-bit net1)
reply other threads:[~2008-11-14 2:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=491CE34E.1070808@oracle.com \
--to=wenji.huang@oracle.com \
--cc=elena.zannoni@oracle.com \
--cc=kris.van.hees@oracle.com \
--cc=systemtap@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).