linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Michael Petlan <mpetlan@redhat.com>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>,
	"linux-perf-users@vger.kernel.org"
	<linux-perf-users@vger.kernel.org>
Subject: Re: [PATCH 3/9] perf test: new testsuite: perf annotate tests
Date: Tue, 15 Dec 2015 13:03:58 +0100	[thread overview]
Message-ID: <20151215120358.GD5074@krava.brq.redhat.com> (raw)
In-Reply-To: <1449514394.24573.253.camel@redhat.com>

On Mon, Dec 07, 2015 at 07:53:14PM +0100, Michael Petlan wrote:
> This commit adds tests for perf annotate tool.
> 
> The structure of the base_something dirs is the following:
> 
> base_something/
> 	settings.sh
> 		- a script mentioned to be sourced within the tests
> 	setup.sh
> 		- if present, necessary for setup of the subset
> 	test_*.sh
> 		- various tests of the subset
> 	cleanup.sh
> 		- a cleanup script that should remove logs, etc.
> 
> All the tests should be stand-alone.  So if needed, it is enough to
> cd to the proper base_directory and run the test.  Sometimes, setup
> is needed to be run first.
> 
> Example:
> 
> cd testsuite/base_annotate
> ./setup.sh
> ./test_basic.sh

hum, would it be better to allow running separate tests via
perf test suite like:

  $ perf test suite base_annotate

you'd need pass argv,argc into tests functions,
which shouldn't be big deal

jirka

  parent reply	other threads:[~2015-12-15 12:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-07 18:53 [PATCH 3/9] perf test: new testsuite: perf annotate tests Michael Petlan
2015-12-15 12:03 ` Jiri Olsa
2015-12-15 12:03 ` Jiri Olsa [this message]
2015-12-15 12:04 ` Jiri Olsa
2015-12-15 12:04 ` Jiri Olsa
2015-12-16 11:51   ` Michael Petlan
     [not found] <cover.1458134357.git.mpetlan@redhat.com>
2016-03-16 13:54 ` Michael Petlan

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=20151215120358.GD5074@krava.brq.redhat.com \
    --to=jolsa@redhat.com \
    --cc=acme@redhat.com \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mpetlan@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 NNTP newsgroup(s).