ceph/qa
Rishabh Dave ce942f250a qa/cephfs: delete path from cmd args after use
A new path is obtained every iteration which is appended to command
arguments. After the command has been executed successfully, delete the
the  path from command's arguments so that the command's arguments don't
have two paths in next iteration and it works as expected.

Fixes: https://tracker.ceph.com/issues/56416
Signed-off-by: Rishabh Dave <ridave@redhat.com>
2022-07-06 17:12:58 +05:30
..
archs
btrfs
cephfs Rename/re-symlink whitelist_*.yaml 2022-05-24 14:14:04 -06:00
client
clusters
config qa/config: override bluestore_zero_block_detection default for rados suite tests 2022-05-27 13:36:18 -05:00
crontab teuthology-cronjobs: master->main 2022-05-25 08:01:11 -04:00
debug
distros
erasure-code
libceph
machine_types schedule_subset.sh: Default to ceph.git 2022-06-08 16:13:29 -04:00
mds
mgr_ttl_cache
mon/bootstrap
mon_election
msgr
nightlies
objectstore
objectstore_cephfs
objectstore_debug bluestore: Revert "os/bluestore: Add CoDel to BlueStore for Bufferbloat mitigation" 2022-04-25 12:33:45 -07:00
overrides Rename/re-symlink whitelist_*.yaml 2022-05-24 14:14:04 -06:00
packages
qa_scripts
rbd
releases
rgw
rgw_bucket_sharding
rgw_frontend
rgw_pool_type
standalone
suites Merge pull request #46078 from kotreshhr/fuse-directory-dacs-issue 2022-06-07 22:45:05 +05:30
tasks qa/cephfs: delete path from cmd args after use 2022-07-06 17:12:58 +05:30
timezone
workunits Merge pull request #46539 from adk3798/master-main-cleanup2 2022-06-07 20:51:06 -04:00
.gitignore
.qa
CMakeLists.txt
find-used-ports.sh
loopall.sh
Makefile
mypy.ini
README
run_xfstests_qemu.sh
run_xfstests-obsolete.sh
run_xfstests.sh
run-standalone.sh
runallonce.sh
runoncfuse.sh
runonkclient.sh
setup-chroot.sh
test_import.py
tox.ini qa: fix teuthology master branch ref 2022-06-02 12:27:02 +02:00
valgrind.supp

ceph-qa-suite
-------------

clusters/    - some predefined cluster layouts
suites/      - set suite

The suites directory has a hierarchical collection of tests.  This can be
freeform, but generally follows the convention of

  suites/<test suite name>/<test group>/...

A test is described by a yaml fragment.

A test can exist as a single .yaml file in the directory tree.  For example:

 suites/foo/one.yaml
 suites/foo/two.yaml

is a simple group of two tests.

A directory with a magic '+' file represents a test that combines all
other items in the directory into a single yaml fragment.  For example:

 suites/foo/bar/+
 suites/foo/bar/a.yaml
 suites/foo/bar/b.yaml
 suites/foo/bar/c.yaml

is a single test consisting of a + b + c.

A directory with a magic '%' file represents a test matrix formed from
all other items in the directory.  For example,

 suites/baz/%
 suites/baz/a.yaml
 suites/baz/b/b1.yaml
 suites/baz/b/b2.yaml
 suites/baz/c.yaml
 suites/baz/d/d1.yaml
 suites/baz/d/d2.yaml

is a 4-dimensional test matrix.  Two dimensions (a, c) are trivial (1
item), so this is really 2x2 = 4 tests, which are

  a + b1 + c + d1
  a + b1 + c + d2
  a + b2 + c + d1
  a + b2 + c + d2

A directory with a magic '$' file, or a directory whose name ends with '$',
represents a test where one of the non-magic items is chosen randomly.  For
example, both

 suites/foo/$
 suites/foo/a.yaml
 suites/foo/b.yaml
 suites/foo/c.yaml

and

 suites/foo$/a.yaml
 suites/foo$/b.yaml
 suites/foo$/c.yaml

is a single test, either a, b or c.  This can be used in conjunction with the
'%' file in the same (see below) or other directories to run a series of tests
without causing an unwanted increase in the total number of jobs run.

Symlinks are okay.

One particular use of symlinks is to combine '%' and the latter form of '$'
feature.  Consider supported_distros directory containing fragments that define
os_type and os_version:

 supported_distros/%
 supported_distros/centos.yaml
 supported_distros/rhel.yaml
 supported_distros/ubuntu.yaml

A test that links supported_distros as distros (a name that doesn't end with
'$') will be run three times: on centos, rhel and ubuntu.  A test that links
supported_distros as distros$ will be run just once: either on centos, rhel or
ubuntu, chosen randomly.

The teuthology code can be found in https://github.com/ceph/teuthology.git