From: "dsmith at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug server/15872] New: on rawhide, we're getting odd client.exp test failures
Date: Wed, 21 Aug 2013 14:16:00 -0000 [thread overview]
Message-ID: <bug-15872-6586@http.sourceware.org/bugzilla/> (raw)
http://sourceware.org/bugzilla/show_bug.cgi?id=15872
Bug ID: 15872
Summary: on rawhide, we're getting odd client.exp test failures
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: server
Assignee: systemtap at sourceware dot org
Reporter: dsmith at redhat dot com
On rawhide, we're seeing some odd results from systemtap.server/client.exp. A
semi-random failure will occur when compiling a module. I typically get one
failure per run, but the failure moves around between tests.
The server reports the module name it compiled, but the module never makes it
back to the client:
====
executing: stap -p4 --unprivileged ./systemtap.server/hello.stp
--use-server=pipa01.englab.brq.redhat.com:54698
spawn stap -p4 --unprivileged ./systemtap.server/hello.stp
--use-server=pipa01.englab.brq.redhat.com:54698
stap_fd27dfa1dcd4afdc7d275807057a3d88_927.ko
PASS: Compile module using server with --unprivileged
'stap_fd27dfa1dcd4afdc7d275807057a3d88_927.ko'
/bin/ls: cannot access stap_fd27dfa1dcd4afdc7d275807057a3d88_927.ko: No such
file or directory
/bin/ls: cannot access stap_fd27dfa1dcd4afdc7d275807057a3d88_927.ko.sgn: No
such file or directory
FAIL: Module was created with --unprivileged
FAIL: Module was signed with --unprivileged
====
Dave Brolley has done some debugging on this issue, and found that the client
is getting a SIGHUP from somewhere.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2013-08-21 14:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-21 14:16 dsmith at redhat dot com [this message]
2013-08-21 14:20 ` [Bug server/15872] " brolley 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=bug-15872-6586@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sourceware.org \
/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).