From: "mhiramat at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug testsuite/5544] New: testing systemtap.stress/current.stp shutdown by eof
Date: Fri, 04 Jan 2008 20:04:00 -0000 [thread overview]
Message-ID: <20080104200317.5544.mhiramat@redhat.com> (raw)
On ia64, sometimes systemtap.stress/current.stp test fails due to eof.
---
Pass 1: parsed user script and 38 library script(s) in 242usr/5sys/248real ms.
Pass 2: analyzed script: 863 probe(s), 3 function(s), 0 embed(s), 1 global(s) in
3936usr/589sys/4533real ms.
Pass 3: translated to C into "/tmp/stap4Yg92X/stap_cbe6e75d38cbeaf3605ce980bfb64
fb1_298670.c" in 28usr/2sys/30real ms.
Pass 4: compiled C into "stap_cbe6e75d38cbeaf3605ce980bfb64fb1_298670.ko" in 418
7usr/227sys/4232real ms.
Pass 5: starting run.
systemtap starting probe
PASS: systemtap.stress/current.stp startup
PASS: systemtap.stress/current.stp load generation
WARNING: Number of errors: 0, skipped probes: 595
systemtap ending probe
count = 4030760
sum = 23622172
min = 2
max = 15
avg = 5
systemtap test success
systemtap test success
Pass 5: run completed in 23usr/152sys/11225real ms.
FAIL: systemtap.stress/current.stp shutdown (eof)
---
But the test itself succeeded.
I found the WARNING message was outputted before ending probe's message.
And stap_run procedure could not handle this pattern.
--
Summary: testing systemtap.stress/current.stp shutdown by eof
Product: systemtap
Version: unspecified
Status: NEW
Severity: minor
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=5544
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2008-01-04 20:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-04 20:04 mhiramat at redhat dot com [this message]
2008-01-04 20:06 ` [Bug testsuite/5544] " mhiramat at redhat dot com
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=20080104200317.5544.mhiramat@redhat.com \
--to=sourceware-bugzilla@sourceware.org \
--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).