From: William Cohen <wcohen@redhat.com>
To: "Nguyen, Thang P" <thang.p.nguyen@intel.com>
Cc: systemtap@sourceware.org
Subject: Re: Summary of nightly testing 20061016 (failed to retrieve return value location)
Date: Wed, 18 Oct 2006 15:57:00 -0000 [thread overview]
Message-ID: <45364EEE.7060708@redhat.com> (raw)
In-Reply-To: <9AE298E00BCF7B469C04BE82FCE78B8701AC14BF@scsmsx414.amr.corp.intel.com>
Nguyen, Thang P wrote:
> Hi Will,
>
> Sorry for the confusion. The test I used
>
> ./testsuite/systemtap.samples/tcptest.exp (tcptest.stp)
>
> Occasionally it fails due to TCP traffic, but not "$return" error.
>
>
> Thang
Okay so it fails on the machines here in the Red Hat office, but works on the
intel machines. Time to compare and find out what is different on the machines.
Were the tests run using the stap_testing script? This script configures the
installation in a local directory. What does the config line look like when
systemtap is built?
distro things are built on:
config:
architecture:
kernel:
binutils:
systemtap:
The local RH rawhide machine I got the failures on
distro things are built on: i686 rawhide
config:/home/wcohen/stap_testing_200610180830/src/configure
--with-elfutils=/home/wcohen/rh-rpms/BUILD/elfutils-0.124
--prefix=/home/wcohen/stap_testing_200610180830/install
architecture: i686
kernel: 2.6.18-1.2798.fc6PAE #1 SMP Mon Oct 16 14:54:22 EDT 2006 i686 i686 i386
GNU/Linux
binutils: ~/rh-rpms/BUILD/elfutils-0.124
systemtap: cvs checkout 20061018
-Will
next prev parent reply other threads:[~2006-10-18 15:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-18 15:41 Nguyen, Thang P
2006-10-18 15:57 ` William Cohen [this message]
2006-10-18 16:40 ` William Cohen
2006-10-18 19:26 ` William Cohen
-- strict thread matches above, loose matches on Subject: below --
2006-10-18 19:46 Nguyen, Thang P
2006-10-18 12:04 Nguyen, Thang P
2006-10-18 13:51 ` William Cohen
2006-10-18 14:08 ` bibo,mao
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=45364EEE.7060708@redhat.com \
--to=wcohen@redhat.com \
--cc=systemtap@sourceware.org \
--cc=thang.p.nguyen@intel.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).