Simon Xu

Error:test_validate_cache(WriteCacheBenchmarks): NoMethodError: undefined method `wait_until_clean' for # /root/device-mapper-test-suite/lib/dmtest/tests/writecache/benchmarks.rb:55:in `block (3 levels) in ' /root/device-mapper-test-suite/lib/dmtest/ensure_elapsed.rb:13:in `ensure_elapsed_time' /root/device-mapper-test-suite/lib/dmtest/writecache-stack.rb:71:in `block in activate_top_level' /root/device-mapper-test-suite/lib/dmtest/ensure_elapsed.rb:13:in `ensure_elapsed_time' /root/device-mapper-test-suite/lib/dmtest/device-mapper/lexical_operators.rb:15:in `block in with_dev' /root/device-mapper-test-suite/lib/dmtest/prelude.rb:6:in `bracket' /root/device-mapper-test-suite/lib/dmtest/device-mapper/lexical_operators.rb:13:in `with_dev' /root/device-mapper-test-suite/lib/dmtest/writecache-stack.rb:69:in...

dmtest should create ~/.dmtest/log and ~/.dmtest/reports directories automatically, it can be pretty confusing for new users. ``` $ dmtest run --suite thin-provisioning -t BasicTests Loaded suite thin-provisioning BasicTests dd_benchmark...PASS ext4_weirdness...PASS...

Document says "A metadata dev of 1G, and data dev of 4G is sufficient.", but it doesn't work with a 1G meta dev (/dev/loop0) and a 4G data dev (/dev/loop1):...

``` $ git show --summary commit b0b8aeb66aaa44f09b76035077e14969769519e0 (HEAD -> master, origin/master, origin/HEAD) Author: Joe Thornber Date: Mon Oct 7 14:14:21 2019 +0100 [cache/tools_tests] cache_writeback doesn't work if you update the...

$ git status `#` On branch master nothing to commit, working directory clean $ git log -n1 commit cd8cbd1a80f429b1e4e93874a9d5836f6caf42a2 Author: Joe Thornber [email protected] Date: Fri May 15 21:52:23 2015 +0100...

A lot of git-related testcases fail with "Errno::EBUSY: Device or resource busy - ./kernel_builds"

2

For instance, WriteboostTestsBackingDevice_git_extract_cache_quick.log: D, [2015-05-11T16:21:38.793363 #14423] DEBUG -- : executing: 'blockdev --getsz /dev/disk/by-id/scsi-35000cca01646b624-part1' D, [2015-05-11T16:21:38.803996 #14423] DEBUG -- : stdout: 41943040 D, [2015-05-11T16:21:38.804441 #14423] DEBUG -- : executing: 'blockdev --getsz...

ProcessControl::ExitError: command failed

8

When I run tests, I get a lot of "ProcessControl::ExitError: command failed", e.g. [root@mybox device-mapper-test-suite]# dmtest run --suite cache --profile mix Loaded suite cache Started BackgroundWritebackTests clean_data_never_gets_written_back...FAIL dirty_data_always_gets_written_back...FAIL BurstyWriteTests git_extract_cache_16...FAIL...

Could not find 'device_mapper_test_suite' (>= 0)

2

I installed device-mapper-test-suite (5ea215e6b26a44afafafbcec484fda8ee2de6051) following the instructions in README.md. $ which dmtest /usr/local/rvm/gems/ruby-1.9.3-p551/bin/dmtest But 'dmtest' fails to run: $ dmtest /usr/local/rvm/rubies/ruby-1.9.3-p551/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:315:in `to_specs': Could not find 'device_mapper_test_suite' (>= 0) among 38...