-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathREADME
74 lines (46 loc) · 1.63 KB
/
README
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
Prerequisites
=============
Test suite for device-mapper thin provisioning targets. Uses Ruby
1.8.x.
You need a program called 'thin_repair' in your path. This hasn't
been released yet, so just sym link it to /bin/true.
You also need dt in your path.
And aio_stress (http://fsbench.filesystems.org/bench/aio-stress.c).
And blktrace.
And bonnie++.
Running
=======
Edit config.rb, adding suitable entries for you test machine.
Check things are ok with a dry run:
./run_tests
Once you're happy you can set the env var THIN_TESTS and run it for
real:
export THIN_TESTS=EXECUTE
./run_tests
You can select subsets of the tests via the test suite class, methods
or tags, for more info:
./run_tests --help
Examples,
Run all tests that have been tagged as quick:
./run_tests -T quick
Run all tests that have been tagged with some sort of target:
./run_tests -T /_target$/
Run all tests that have 'resize' in their name:
./run_tests -n /resize/
Run all tests in the MultiplePoolTests suite:
./run_tests -t MultiplePoolTests
Reports
=======
After you run some tests you can view the results and logs by pointing
your browser at reports/index.html.
If you wish to quickly serve these reports on port 8080 for access
from another machine.
./serve_reports
Udev
====
You may find that udev interferes with your tests. The typical
symptom is test scripts being unable to remove devices (because udev
has it open). The test suite does retry removal after a pause, which
avoids most cases of this.
One way to disable udev is:
mv /lib/udev/rules.d/80-udisks.rules /lib/udev/rules.d/80-udisks.rules.dieudevdie