From: Loic Dachary <loic@dachary.org>
To: Ceph Development <ceph-devel@vger.kernel.org>
Subject: teuthology and code coverage revisited
Date: Tue, 05 Mar 2013 00:40:22 +0100 [thread overview]
Message-ID: <513530E6.4000705@dachary.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1524 bytes --]
Hi,
The "ceph code coverage" ( http://dachary.org/?p=1788 ) guide to collecting code coverage using teuthology was updated to take into account the fact that teuthology now uses packages ( the install: task ). But it is still incomplete because I'm not sure how to collect the coverage data.
For test purposes I used the simplest yaml file:
check-locks: false
roles:
- - mon.a
- mon.c
- osd.0
- - mon.b
- osd.1
tasks:
- install:
- ceph:
branch: master
coverage: true
flavor: gcov
fs: xfs
and it completes successfully. The method I learnt to collect code coverage back in january relied on a ceph-sha1 file being created in the --archive but it's no longer there. Reading
https://github.com/ceph/teuthology/commit/2653b5a07b880c202800c939efcd1ccaaf254841#L0R72
prompted me to try to add coverage: true :
check-locks: false
roles:
- - mon.a
- mon.c
- osd.0
- - mon.b
- osd.1
tasks:
- install:
coverage: true
- ceph:
branch: master
coverage: true
flavor: gcov
fs: xfs
but it fails with
CommandFailedError: Command failed on 10.20.0.7 with status 1: 'rmdir -- /tmp/cephtest/ubuntu@teuthology-2013-03-04_21-03-19'
DEBUG:teuthology.run_tasks:Exception was not quenched, exiting: Exception: failed to fetch package version from http://gitbuilder.ceph.com/ceph-deb-quantal-x86_64-gcov/ref/master/version
INFO:teuthology.run:Summary data:
I would very much appreciate a hint.
Cheers
--
Loïc Dachary, Artisan Logiciel Libre
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next reply other threads:[~2013-03-04 23:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-04 23:40 Loic Dachary [this message]
2013-03-05 17:30 ` teuthology and code coverage revisited Josh Durgin
2013-03-05 23:05 ` 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=513530E6.4000705@dachary.org \
--to=loic@dachary.org \
--cc=ceph-devel@vger.kernel.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.