[PATCH blktests RFC 0/2] check: support "set -e" strict error-checking

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



In bash script development, it is a good practices to handle errors
strictly using "set -e" or "set -o errexit". When this option is
enabled, bash exits immediately upon encountering an error. There have
been discussions about implementing this strict error-checking mechanism
in blktests test cases [1]. Recently, these discussions were revisited,
and it has been proposed to enable this strict error-checking for a
limited subset of test cases [2].

This series supports the "set -e" strict error-checking based on the
discussion. The first patch modifies the check script to allow "set -e"
in each test case. The second patch adds the feature to detect the
test case exit by the error-checking and abort the test script run.

[1] https://github.com/linux-blktests/blktests/issues/89
[2] https://lore.kernel.org/linux-block/ckctv7ioomqpxe2iwcg6eh6fvtzamoihnmwxvavd7lanr4y2y6@fbznem3nvw3w/

Shin'ichiro Kawasaki (2):
  check: allow strict error-checking by "set -e" in each test case
  check: abort test run when a test case exits by "set -e"
    error-checking

 check | 47 ++++++++++++++++++++++++++++++++++-------------
 1 file changed, 34 insertions(+), 13 deletions(-)

-- 
2.49.0





[Index of Archives]     [Linux RAID]     [Linux SCSI]     [Linux ATA RAID]     [IDE]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Device Mapper]

  Powered by Linux