public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "Spirakis, Charles" <charles.spirakis@intel.com>
To: <systemtap@sources.redhat.com>
Subject: Expected errors from make check?
Date: Tue, 30 Aug 2005 00:08:00 -0000	[thread overview]
Message-ID: <2CB9B46A0690824693581340E23B4E1004ED0027@scsmsx401.amr.corp.intel.com> (raw)

All --

Seems like there may be a path issue or something with the makefile
check/test scripts (see below). System is i686 running FC4 using the
elfutils 114 via SRPMS.

-- charles

[root@cspiraki-lnote src]# rpm -qa | grep kernel
kernel-devel-2.6.12-1.1447_FC4
kernel-2.6.12-1.1447_FC4
kernel-debuginfo-2.6.12-1.1447_FC4

[root@cspiraki-lnote src]# make check
...
FAIL: ./testsuite/buildok/eight.stp
FAIL: ./testsuite/buildok/eleven.stp
FAIL: ./testsuite/buildok/fifteen.stp
FAIL: ./testsuite/buildok/five.stp
FAIL: ./testsuite/buildok/four.stp
FAIL: ./testsuite/buildok/fourteen.stp
PASS: ./testsuite/buildok/nine.stp
FAIL: ./testsuite/buildok/one.stp
FAIL: ./testsuite/buildok/seven.stp
FAIL: ./testsuite/buildok/six.stp
FAIL: ./testsuite/buildok/sixteen.stp
FAIL: ./testsuite/buildok/ten.stp
FAIL: ./testsuite/buildok/thirteen.stp
FAIL: ./testsuite/buildok/three.stp
FAIL: ./testsuite/buildok/twelve.stp
FAIL: ./testsuite/buildok/two.stp
...
=============================================
15 of 93 tests failed
Please report to systemtap@sources.redhat.com
=============================================

[root@cspiraki-lnote testsuite]# more buildok-two.stp.err
Pass 4: compilation failed.  Try again with '-v' (verbose) option.

When I modify the .../testsuite/buildok/two.stp to add the -v option and
then run that manually:

[root@cspiraki-lnote src]# testsuite/buildok/two.stp
Created temporary directory "/tmp/stapu78IAg"
Searched '/usr/local/share/systemtap/tapset/2.6.12-1.1447_FC4/*.stp',
match count 0
Searched '/usr/local/share/systemtap/tapset/2.6.12/*.stp', match count 0
Searched '/usr/local/share/systemtap/tapset/2.6/*.stp', match count 0
Searched '/usr/local/share/systemtap/tapset/*.stp', match count 3
Pass 1: parsed user script and 3 library script(s).
Pass 2: analyzed user script.  1 probe(s), 10 function(s), 0 global(s).
Pass 3: translated to C into "/tmp/stapu78IAg/stap_0_1125360180.c"
Running /usr/bin/make -C "/lib/modules/2.6.12-1.1447_FC4/build"
M="/tmp/stapu78IAg" modules
make: Entering directory `/usr/src/kernels/2.6.12-1.1447_FC4-i686'
  CC [M]  /tmp/stapu78IAg/stap_0_1125360180.o
  Building modules, stage 2.
  MODPOST
  CC      /tmp/stapu78IAg/stap_0_1125360180.mod.o
  LD [M]  /tmp/stapu78IAg/stap_0_1125360180.ko
make: Leaving directory `/usr/src/kernels/2.6.12-1.1447_FC4-i686'
Pass 4: compiled into "stap_0_1125360180.ko"
Running /bin/rm -rf /tmp/stapu78IAg


             reply	other threads:[~2005-08-30  0:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-30  0:08 Spirakis, Charles [this message]
2005-08-30  1:00 ` Frank Ch. Eigler
2005-08-30  1:27 Peng Hongbo
2005-08-30  2:00 Spirakis, Charles
     [not found] <45305.7544692003$1125365259@news.gmane.org>
2005-08-30  2:14 ` Frank Ch. Eigler

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=2CB9B46A0690824693581340E23B4E1004ED0027@scsmsx401.amr.corp.intel.com \
    --to=charles.spirakis@intel.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).