public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: David Smith <dsmith@redhat.com>
To: naresh kamboju <naresh.kernel@gmail.com>
Cc: systemtap@sources.redhat.com,
	"Frank Ch. Eigler" <fche@redhat.com>,
	        wenji.huang@oracle.com,
	Masami Hiramatsu <mhiramat@redhat.com>,
	        David Howells <dhowells@redhat.com>
Subject: Re: Build Pass from file name hyphen->underscore
Date: Wed, 02 Dec 2009 19:37:00 -0000	[thread overview]
Message-ID: <4B16C1DE.4080005@redhat.com> (raw)
In-Reply-To: <f5a7b3810912020511o7f1caf5dld70e650b2721e3cc@mail.gmail.com>

On 12/02/2009 07:11 AM, naresh kamboju wrote:
> Hi,
> 
> I have been investigating SystemTap test suite, its sub modules and
> expected pass and expected failures.
> 
> As per my investigation I have noticed there are test cases name with
> – hyphen are not able to build. When I have changed it to underscore _
> it is able to build.
> As per stap, If you add ‘-‘ (hyphen) in the file name, then stap is
> able to consider as invalid module name.
> 
> BUILD_FAIL				BUILD_PASS
> aux_syscalls-embedded.stp -> aux_syscalls_embedded.stp
> 
> 
> There were almost 36 test cases in this category.
> Are considering these expected failures?

This doesn't make much sense to me.  Yes, '-' is an illegal character in
a module name, but that doesn't matter here.  Besides the fact that
aux_syscalls-embedded.stp just gets compiled and not actually inserted,
that isn't the module name.  Systemtap generated a random string of the
form 'stap_XXXXX...' for the module name (unless someone uses the '-m
NAME' option).

So, unless someone is doing 'stap -m aux_syscalls-embedded
aux_syscalls-embedded.stp', the above problem shouldn't exist.

Can you give us more details here about your system and the failure
messages you are getting?

-- 
David Smith
dsmith@redhat.com
Red Hat
http://www.redhat.com
256.217.0141 (direct)
256.837.0057 (fax)

  parent reply	other threads:[~2009-12-02 19:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-02 13:11 naresh kamboju
2009-12-02 19:27 ` Frank Ch. Eigler
2009-12-03  7:42   ` Regression on statistics Wenji Huang
2009-12-04  4:38     ` [PATCH] Fix regression in statistic operations Anton Vorontsov
2009-12-04  5:41       ` Wenji Huang
2009-12-02 19:37 ` David Smith [this message]
2009-12-03 15:18   ` Build Pass from file name hyphen->underscore naresh kamboju
2009-12-03 16:13     ` David Smith
2009-12-03 16:21       ` Masami Hiramatsu
2009-12-03 17:02         ` David Smith
2009-12-06 23:37     ` Frank Ch. Eigler
     [not found]       ` <f5a7b3811003291057q6ad8a5abqeaf3c71fb94b89ec@mail.gmail.com>
2010-03-29 18:41         ` 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=4B16C1DE.4080005@redhat.com \
    --to=dsmith@redhat.com \
    --cc=dhowells@redhat.com \
    --cc=fche@redhat.com \
    --cc=mhiramat@redhat.com \
    --cc=naresh.kernel@gmail.com \
    --cc=systemtap@sources.redhat.com \
    --cc=wenji.huang@oracle.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).