From: Loic Dachary <loic@dachary.org>
To: Ceph Development <ceph-devel@vger.kernel.org>
Subject: teuthology and code coverage
Date: Tue, 13 Aug 2013 19:01:53 +0200 [thread overview]
Message-ID: <520A6681.9040804@dachary.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 3583 bytes --]
Hi,
When running teuthology from a laptop with the configuration below and
./virtualenv/bin/teuthology --archive=/tmp/teuthology try.yaml
it then fails on
./virtualenv/bin/teuthology-coverage -v --html-output /tmp/html -o /tmp/lcov --cov-tools-dir $(pwd)/coverage /tmp/teuthology
ERROR:teuthology.coverage:error generating coverage
Traceback (most recent call last):
File "/home/loic/software/ceph/teuthology/teuthology/coverage.py", line 145, in analyze
_analyze(args)
File "/home/loic/software/ceph/teuthology/teuthology/coverage.py", line 171, in _analyze
assert len(test_summaries) > 0
AssertionError
Traceback (most recent call last):
File "./virtualenv/bin/teuthology-coverage", line 9, in <module>
load_entry_point('teuthology==0.0.1', 'console_scripts', 'teuthology-coverage')()
File "/home/loic/software/ceph/teuthology/teuthology/coverage.py", line 145, in analyze
_analyze(args)
File "/home/loic/software/ceph/teuthology/teuthology/coverage.py", line 171, in _analyze
assert len(test_summaries) > 0
AssertionError
/tmp/teuthology looks like this:
./config.yaml
./summary.yaml
./owner
./pid
./teuthology.log
./orig.config.yaml
./remote
./remote/target1
./remote/target1/log
./remote/target1/log/ceph-osd.0.log.gz
./remote/target1/log/ceph.log.gz
./remote/target1/log/ceph-mon.c.log.gz
./remote/target1/log/ceph-osd.2.log.gz
./remote/target1/log/ceph-osd.1.log.gz
./remote/target1/log/ceph-mon.a.log.gz
./remote/target1/syslog
./remote/target1/syslog/kern.log
./remote/target1/syslog/misc.log
./remote/target1
./remote/target1/log
./remote/target1/log/ceph-osd.3.log.gz
./remote/target1/log/ceph-mds.a.log.gz
./remote/target1/log/ceph-osd.4.log.gz
./remote/target1/log/ceph.log.gz
./remote/target1/log/ceph-osd.5.log.gz
./remote/target1/log/ceph-mon.b.log.gz
./remote/target1/syslog
./remote/target1/syslog/kern.log
./remote/target1/syslog/misc.log
./data
./data/mon.b.tgz
./data/mon.c.tgz
./data/mon.a.tgz
with summary.yaml
duration: 1615.8156020641327
flavor: basic
owner: loic@dachary.org
success: true
and orig.config.yaml ( targets edited out )
nuke-on-error: true
overrides:
admin_socket:
branch: master
ceph:
branch: master
conf:
global:
ms inject delay max: 1
ms inject delay probability: 0.005
ms inject delay type: osd
ms inject socket failures: 2500
osd map cache size: 1
mon:
debug mon: 20
debug ms: 20
debug paxos: 20
mon min osdmap epochs: 2
osd:
debug filestore: 20
debug ms: 1
debug osd: 20
osd debug verify stray on activate: true
osd op thread timeout: 60
fs: xfs
log-whitelist:
- slow request
install:
ceph:
branch: master
roles:
- - mon.a
- mon.c
- osd.0
- osd.1
- osd.2
- - mon.b
- mds.a
- osd.3
- osd.4
- osd.5
- client.0
tasks:
- chef: null
- install: null
- ceph:
coverage: true
flavor: gcov
log-whitelist:
- wrongly marked me down
- objects unfound and apparently lost
- rados:
clients:
- client.0
objects: 500
op_weights:
delete: 10
read: 45
rollback: 50
snap_create: 50
snap_remove: 50
write: 45
ops: 4000
I guess I'm not placing the "flavor: gcov" where I should.
Cheers
--
Loïc Dachary, Artisan Logiciel Libre
All that is necessary for the triumph of evil is that good people do nothing.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 261 bytes --]
next reply other threads:[~2013-08-13 17:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-13 17:01 Loic Dachary [this message]
2013-08-14 7:38 ` teuthology and code coverage Josh Durgin
2013-08-14 8:06 ` 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=520A6681.9040804@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox