All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josh Durgin <josh.durgin@inktank.com>
To: Loic Dachary <loic@dachary.org>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: code coverage and teuthology
Date: Mon, 14 Jan 2013 09:26:03 -0800	[thread overview]
Message-ID: <50F43FAB.2050609@inktank.com> (raw)
In-Reply-To: <50EF49C4.1020909@dachary.org>

On 01/10/2013 03:07 PM, Loic Dachary wrote:
> Hi,
>
> I successfully run teuthology with the proposed 3node_rgw.yaml [1] and changing the flavor from basic to gcov [2]. I hoped to use cov-init.sh ( https://github.com/ceph/teuthology/blob/master/coverage/cov-init.sh ) and then coverage.sh but I can't figure out how to make it work.
>
> Hints would be most appreciated ;-)

Looking at how it's run automatically might help:

https://github.com/ceph/teuthology/blob/master/teuthology/coverage.py#L88

> [1] 3node_rgw.yaml
>
> check-locks: false
> interactive-on-error: true
> overrides:
>    ceph:
>      branch: master
>      fs: xfs

You should also add 'coverage: true' for the ceph task overrides.
This way daemons are killed with SIGTERM, and the atexit function
that outputs coverage information will run.

Then you don't need your patch changing the flavor either.
For each task X, the docstring for teuthology.task.X.task documents
example usage and extra options like this.

Josh

> roles:
> - - mon.a
>    - mon.c
>    - osd.0
> - - mon.b
>    - mds.a
>    - osd.1
> - - client.0
> tasks:
> - ceph: null
> - rgw:
>    - client.0
> - interactive:
>
> targets:
> (snip)
>
> [2] http://gitbuilder.ceph.com/ceph-tarball-precise-x86_64-gcov/
>
> diff --git a/teuthology/task/ceph.py b/teuthology/task/ceph.py
> index b62bc1d..99d4f18 100644
> --- a/teuthology/task/ceph.py
> +++ b/teuthology/task/ceph.py
> @@ -1027,7 +1027,7 @@ def task(ctx, config):
>       dist = 'precise'
>       format = 'tarball'
>       arch = 'x86_64'
> -    flavor = 'basic'
> +    flavor = 'gcov'
>
>       # First element: controlled by user (or not there, by default):
>       # used to choose the right distribution, e.g. "oneiric".
> diff --git a/teuthology/task/kernel.py b/teuthology/task/kernel.py
> index 5c34433..54eaebb 100644
> --- a/teuthology/task/kernel.py
> +++ b/teuthology/task/kernel.py
> @@ -183,7 +183,7 @@ def download_deb(ctx, config):
>                   package='kernel',
>                   sha1=src,
>                   format='deb',
> -                flavor='basic',
> +                flavor='gcov',
>                   arch='x86_64',
>                   dist='precise',
>                   )
> @@ -408,7 +408,7 @@ def task(ctx, config):
>                   branch=role_config.get('branch'),
>                   tag=role_config.get('tag'),
>                   sha1=role_config.get('sha1'),
> -                flavor='basic',
> +                flavor='gcov',
>                   format='deb',
>                   dist='precise',
>                   arch='x86_64',
>


  reply	other threads:[~2013-01-14 17:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-10 23:07 code coverage and teuthology Loic Dachary
2013-01-14 17:26 ` Josh Durgin [this message]
2013-01-15 10:10   ` Loic Dachary
2013-01-15 17:21     ` Josh Durgin
2013-01-15 20:23       ` Dan Mick
2013-01-16 12:52       ` Loic Dachary

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=50F43FAB.2050609@inktank.com \
    --to=josh.durgin@inktank.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=loic@dachary.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.