David Teigland ad9cbe2714 tests: direct control of lvm1 usage in tests ... Using lvm1 metadata with lvmetad is not generally allowed, but nothing has prevented creating new lvm1 metadata with lvmetad (missing error checking in pvcreate/vgcreate.) Various tests are using lvm1 with lvmetad and happen to work because of the missing error checks. This commit fixes the tests so they won't fail when the lvm1/lvmetad error checking is fixed. A new variable LVM_TEST_LVM1 is defined and is used in the scripts to decide if lvm1 metadata should be tested. LVM_TEST_LVM1 is not defined when lvmetad is being tested, and the combination of LVM_TEST_LVM1 and LVM_TEST_LVMETAD can be used to verify the desired lvmetad+lvm1 behavior.		2016-03-03 14:43:19 -06:00
..
api	tests: add SKIP_WITH_LVMLOCKD	2016-02-23 09:28:48 -06:00
dbus	lvmdbusd testing: Add validatestate.py utility	2016-02-25 16:43:55 -06:00
lib	tests: direct control of lvm1 usage in tests	2016-03-03 14:43:19 -06:00
shell	tests: direct control of lvm1 usage in tests	2016-03-03 14:43:19 -06:00
unit	doc: change fsf address	2016-01-21 12:11:37 +01:00
.gitignore	gitignore: Remove redundant test dir entry	2012-06-08 23:34:15 +01:00
Makefile.in	makefile: handle dm-version-expected	2016-03-01 16:03:02 +01:00