For those who interested in blktests: A pull request is now under review [1] which suggests to improve SKIP_REASON handling. Some test cases or test groups have rather large number of test run requirements and then they may have multiple skip reasons. However, blktests can report only single skip reason. To know all of the skip reasons, we need to repeat skip reason resolution and blktests run. This is a troublesome work. With the suggested code change, all of the skip reasons will be printed at one shot run. Handy. On the other hand, it will change the way to set SKIP_REASON in requirement check functions. A new helper function will be used in place of substittion to the SKIP_REASON variable. Just in case you are interested in, take a look in the pull request. [1] https://github.com/osandov/blktests/pull/96 -- Shin'ichiro Kawasaki
