From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30226 invoked by alias); 8 Jan 2008 20:08:34 -0000 Received: (qmail 30063 invoked by uid 48); 8 Jan 2008 20:07:51 -0000 Date: Tue, 08 Jan 2008 20:08:00 -0000 From: "mhiramat at redhat dot com" To: systemtap@sources.redhat.com Message-ID: <20080108200751.5554.mhiramat@redhat.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug testsuite/5554] New: sytemtap.syscall failures on ia64. X-Bugzilla-Reason: AssignedTo Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: systemtap-owner@sourceware.org X-SW-Source: 2008-q1/txt/msg00020.txt.bz2 On ia64@RHEL5u1, some tests(alarm, forkwait, stat) in systemtap.syscall fails. Here are the log messages of those tests. ============================ 1) FAIL: alarm ============================ alarm: setitimer (ITIMER_REAL, [0.000000,1.000000], 0x60000fffffa734c0) = 0 alarm: rt_sigprocmask (SIG_BLOCK, [NULL], 0x60000fffffa73480, 8) = 0 alarm: rt_sigsuspend () = -4 (EINTR) alarm: setitimer (ITIMER_REAL, [0.000000,0.000000], 0x60000fffffa734c0) = 0 alarm: rt_sigprocmask (SIG_BLOCK, [SIGCHLD], 0x60000fffffa733f0, 8) = 0 alarm: rt_sigaction (SIGCHLD, {NULL}, 0x60000fffffa73470, 8) = 0 alarm: rt_sigprocmask (SIG_SETMASK, [SIGUSR1], 0x0000000000000000, 8) = 0 alarm: nanosleep ([1.000000000], 0x60000fffffa73360) = 0 alarm: nanosleep ([0.001234000], 0x0000000000000000) = 0 alarm: nanosleep ([0.000000789], 0x60000fffffa73500) = 0 alarm: nanosleep ([0.000000789], 0x0000000000000000) = 0 alarm: exit_group (0) = alarm: exit (0) = --------- EXPECTED and NOT MATCHED ---------- alarm: alarm \(1\) = 0 alarm: pause \(\) = alarm: alarm \(0\) = 0 alarm: nanosleep \(\[1.000000000\], [x0-9a-fA-F]+\) = 0 alarm: nanosleep \(\[0.001234000\], 0x[0]+\) = 0 alarm: nanosleep \(\[0.000000789\], [x0-9a-fA-F]+\) = 0 alarm: nanosleep \(\[0.000000789\], 0x[0]+\) = 0 FAIL: 64-bit alarm FAIL alarm ============================ 2) FAIL: forkwait ============================ forkwait: fork_kernel_thread (CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID) = 21905 forkwait: wait4 (21905, 0x60000fffff8a35a8, WNOHANG, 0x0000000000000000) = 0 forkwait: exit_group (0) = forkwait: exit (0) = --------- EXPECTED and NOT MATCHED ---------- forkwait: clone \(CLONE_CHILD_CLEARTID\|CLONE_CHILD_SETTID\) = [\-0-9]+ forkwait: wait4 \([\-0-9]+, [x0-9a-fA-F]+, WNOHANG, [x0-9a-fA-F]+\) = [\-0-9]+ FAIL: 64-bit forkwait FAIL forkwait ============================ 3) FAIL: stat ============================ stat: utimes ("foobar", [1.000000][1135641600.000000]) = stat: futimesat (AT_FDCWD, "foobar", [1.000000][1135641600.000000]) = 0 stat: utimes ("foobar", [1135690000.000000][1135700000.000000]) = stat: futimesat (AT_FDCWD, "foobar", [1135690000.000000][1135700000.000000]) = 0 stat: exit_group (0) = stat: exit (0) = --------- EXPECTED and NOT MATCHED ---------- stat: utime \("foobar", \[1970/01/01-00:00:01, 2005/12/27-00:00:00\]\) = 0 stat: utime \("foobar", \[2005/12/27-13:26:40, 2005/12/27-16:13:20\]\) = 0 FAIL: 64-bit stat FAIL stat === -- Summary: sytemtap.syscall failures on ia64. Product: systemtap Version: unspecified Status: NEW Severity: normal Priority: P2 Component: testsuite AssignedTo: systemtap at sources dot redhat dot com ReportedBy: mhiramat at redhat dot com http://sourceware.org/bugzilla/show_bug.cgi?id=5554 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.