mirror of
https://github.com/ceph/ceph
synced 2025-03-11 02:39:05 +00:00
Ceph is a distributed object, block, and file storage platform
837ab3c7f8
2012-11-18T11:11:53.032 INFO:teuthology.orchestra.run.out:174 [failed, exit status 1] - output mismatch (see 174.out.bad) 2012-11-18T11:11:53.035 INFO:teuthology.orchestra.run.out:--- 174.out 2012-11-18 09:40:51.869769691 -0800 2012-11-18T11:11:53.035 INFO:teuthology.orchestra.run.out:+++ 174.out.bad 2012-11-18 11:11:51.017195883 -0800 2012-11-18T11:11:53.036 INFO:teuthology.orchestra.run.out:@@ -1,11 +1,5 @@ 2012-11-18T11:11:53.036 INFO:teuthology.orchestra.run.out: QA output created by 174 2012-11-18T11:11:53.036 INFO:teuthology.orchestra.run.out:-# testing 8 32 65 3 1 1 0 fail .... 2012-11-18T11:11:53.036 INFO:teuthology.orchestra.run.out:-# streaming 2012-11-18T11:11:53.036 INFO:teuthology.orchestra.run.out:-# sync AGs... 2012-11-18T11:11:53.036 INFO:teuthology.orchestra.run.out:-# checking stream AGs... 2012-11-18T11:11:53.036 INFO:teuthology.orchestra.run.out:-+ expected failure, matching AGs 2012-11-18T11:11:53.036 INFO:teuthology.orchestra.run.out:-# testing 8 32 65 3 1 0 1 fail .... 2012-11-18T11:11:53.036 INFO:teuthology.orchestra.run.out:-# streaming 2012-11-18T11:11:53.036 INFO:teuthology.orchestra.run.out:-# sync AGs... 2012-11-18T11:11:53.037 INFO:teuthology.orchestra.run.out:-# checking stream AGs... 2012-11-18T11:11:53.037 INFO:teuthology.orchestra.run.out:-+ expected failure, matching AGs 2012-11-18T11:11:53.037 INFO:teuthology.orchestra.run.out:+umount: /tmp/cephtest/scratch_mnt.0ZO5vZAvBE: device is busy. 2012-11-18T11:11:53.037 INFO:teuthology.orchestra.run.out:+ (In some cases useful info about processes that use 2012-11-18T11:11:53.037 INFO:teuthology.orchestra.run.out:+ the device is found by lsof(8) or fuser(1)) 2012-11-18T11:11:53.037 INFO:teuthology.orchestra.run.out:+failed to unmount /dev/rbd2 |
||
|---|---|---|
| clusters | ||
| suites | ||
| .gitignore | ||
| README | ||
ceph-qa-suite ------------- clusters/ - some predefined cluster layouts suites/ - sets of collections We have several collections, each a subdirectory within suites/*/. Each collection directory consists of a set facets. The basic idea is that, for each collection, the set of tests to run consists of all combinations of taking one yaml fragment from each facet. For example, given the files suite/collection/ suite/collection/foo/ suite/collection/foo/clusters/ suite/collection/foo/clusters/fixed-3.yaml suite/collection/foo/clusters/fixed-9.yaml suite/collection/foo/tasks/ suite/collection/foo/tasks/a suite/collection/foo/tasks/b suite/collection/foo/tasks/c suite/collection/bar/ suite/collection/bar/clusters/fixed-3.yaml suite/collection/bar/tasks/ suite/collection/bar/tasks/d suite/collection/bar/tasks/e teuthology-suite would run tasks a, b, and c on both fixed-3 and fixed-9 clusters. It would also run tasks d and e on the fixed-3 cluster. Note that the 'clusters' and 'tasks' terminology is actually meaningless here. All teuthology-suite does is stick the yaml fragments together (one from each facet) and run teuthology on the result (optionally combined with any additional fragments passed on the command line). In practice, we can keep common/shared task and cluster definitions in the top-level clusters/ (which are otherwise ignored), and symlink to them from the collections that want to use them. The teuthology code can be found in https://github.com/ceph/teuthology.git