summaryrefslogtreecommitdiff
path: root/tests/t_ext_jnl_rm
Commit message (Collapse)AuthorAgeFilesLines
* tests: use make rules to run tests in parallelAndreas Dilger2012-05-291-5/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | Change the e2fsck/mke2fs/tune2fs/e2image/debugfs regression tests to be driven by Makefile rules instead of by a script loop. This allows the tests to be run in parallel like a build and reduces testing time significantly. One major change to the tests themselves is to printing the test name, description, and status together after the test has passed or failed, to avoid mixing lines from the tests. The other major change is to use unique temporary filenames for each test, which was mostly handled already via b4db1e4c7461a50e18c9fd135b9f1ba6f27e4390, but in some cases temporary files are changed to use $test_name.tmp to avoid any collision between running tests. On my old 2-CPU system it reduced the testing time from 160s to 40s. Much of the savings is from the MMP test delays running in parallel. It still takes the time of the slowest test, f_mmp_garbage, though there will be ongoing benefit in the future as more tests are added since the wallclock time will not increase linearly for each test. Tests were run with various combinations of "make -j", and "make -j2" through "make -j44" repeatedly without any test failures. Signed-off-by: Andreas Dilger <adilger@whamcloud.com> Signed-off-by: Theodore Ts'o <tytso@mit.edu>
* tune2fs: kill external journal if device not foundAndreas Dilger2011-09-241-0/+28
Continue to remove the external journal device even if the device cannot be found. Add a test to verify that the journal device/UUID are actually removed from the superblock. It isn't possible to use a real journal device for testing without loopback devices and such (it must be a block device) and this would invite complexity and failures in the regression test. Signed-off-by: Andreas Dilger <adilger@whamcloud.com> Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>