Re: [PATCH blktests v2 0/3] introduce command trace feature

[Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>]

On May 16, 2026 / 21:07, Shin'ichiro Kawasaki wrote:
> Some blktests test cases have deep nesting, making their behavior
> difficult to understand. For example, the nvme test group has many
> helper functions that set sysfs attribute values and call nvme-cli
> commands. Understanding these behaviors is essential for debugging test
> case failures.
> 
> This series adds a new 'command trace' feature to blktests. The first
> patch introduces a new --cmd-trace (or -t) option to record commands
> executed during test runs. The second and third patches add a new helper
> function _set_attr(), which traces both the value and file name of sysfs
> attribute writes.
> 
> With this series, blktests users can use the option to generate a
> .cmdtrace file that records all commands executed during a test case
> run. By grepping the .cmdtrace file, users can check writes to sysfs
> attributes and nvme-cli command invocations. The example below shows how
> nvme targets are set up for the nvme/008 test case with rdma transport.

FYI, I applied this series.