public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: Hien Nguyen <hien@us.ibm.com>
To: SystemTAP <systemtap@sources.redhat.com>
Subject: nightly test result of systemtap in ppc64
Date: Mon, 10 Apr 2006 18:30:00 -0000	[thread overview]
Message-ID: <443AA436.9040802@us.ibm.com> (raw)

Translator summary of failed tests
FAIL: /root/stap_testing_200604101559/src/testsuite/buildok/indent.stp

/tmp/stapUqKBHd/stap_17486.c: In function `function__generic_indent':
/tmp/stapUqKBHd/stap_17486.c:376: warning: long long int format, int64_t 
arg (arg 4)
/tmp/stapUqKBHd/stap_17486.c:376: warning: long long int format, int64_t 
arg (arg 6)
/tmp/stapUqKBHd/stap_17486.c:376: warning: long long int format, int64_t 
arg (arg 4)
/tmp/stapUqKBHd/stap_17486.c:376: warning: long long int format, int64_t 
arg (arg 6)

FAIL: /root/stap_testing_200604101559/src/testsuite/buildok/printf.stp
/tmp/stap5WbDIE/stap_17538.c: In function `probe_0':
/tmp/stap5WbDIE/stap_17538.c:205: warning: long long int format, int64_t 
arg (arg 4)
/tmp/stap5WbDIE/stap_17538.c:205: warning: long long int format, int64_t 
arg (arg 5)


FAIL: /root/stap_testing_200604101559/src/testsuite/buildok/syscall.stp
[....]
In function `probe_114':
/tmp/stapHw1Dhz/stap_17579.c:76840: warning: long long int format, 
int64_t arg (arg 4)
/tmp/stapHw1Dhz/stap_17579.c:76840: warning: long long int format, 
int64_t arg (arg 4)
/tmp/stapHw1Dhz/stap_17579.c: In function `probe_116':
/tmp/stapHw1Dhz/stap_17579.c:77271: warning: long long int format, 
int64_t arg (arg 4)
/tmp/stapHw1Dhz/stap_17579.c:77271: warning: long long int format, 
int64_t arg (arg 5)
[...]

FAIL: /root/stap_testing_200604101559/src/testsuite/buildok/twenty.stp
prologue found function 'vfs_readdir' = 0xc0000000000d9d0c
finding location for local 'file' near address c0000000000d9d0c, module 
bias 0
semantic error: write to target variable not permitted: identifier 
'$file' at ../src/testsuite/buildok/twenty.stp:7:2

FAIL: /root/stap_testing_200604101559/src/testsuite/buildok/twentythree.stp

prologue found function 'free_task' = 0xc00000000005bc38
finding location for local 'tsk' near address c00000000005bc38, module 
bias 0
finding location for local 'tsk' near address c00000000005bc38, module 
bias 0
semantic error: write to target variable not permitted: identifier 
'$tsk' at ../src/testsuite/buildok/twentythree.stp:7:2

=============================================
5 of 140 tests failed
Please report to systemtap@sources.redhat.com
=============================================



Test suite summary of failed tests
FAIL: ./systemtap.maps/ix_hist.stp unexpected EOF
FAIL: syscalls-run (48)
 === systemtap Summary ===

# of expected passes            133
# of unexpected failures        2
# of untested testcases         1

             reply	other threads:[~2006-04-10 18:30 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-10 18:30 Hien Nguyen [this message]
2006-04-10 20:19 ` Hien Nguyen
2006-04-10 20:28   ` Roland McGrath
2006-04-10 20:42   ` Frank Ch. Eigler
2006-04-10 20:53     ` Roland McGrath
2006-04-10 21:05     ` Martin Hunt
  -- strict thread matches above, loose matches on Subject: below --
2006-05-15 20:44 Hien Nguyen
2006-05-09 18:46 Stone, Joshua I
2006-05-10 16:19 ` Hien Nguyen
2006-05-09 18:19 Stone, Joshua I
2006-05-09 18:29 ` Hien Nguyen
2006-05-09 17:59 Stone, Joshua I
2006-05-09 18:02 ` Hien Nguyen
2006-05-09 17:28 Hien Nguyen
2006-04-24 18:16 Nightly " Hien Nguyen
2006-04-24 18:55 ` Frank Ch. Eigler
2006-04-24 22:18   ` Hien Nguyen
2006-05-01 21:53     ` Hien Nguyen
     [not found]       ` <20060503021650.GC11017@redhat.com>
     [not found]         ` <4458FFA2.3090802@us.ibm.com>
2006-05-07 22:52           ` Frank Ch. Eigler
2006-03-27 19:35 Hien Nguyen

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=443AA436.9040802@us.ibm.com \
    --to=hien@us.ibm.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).