Open schlad opened 4 years ago
First trivial PR to get some comments: https://github.com/osandov/blktests/pull/62
For xunit I would wonder how to build the structure of tags. I'll propose something later on as I already run blktests in the CI and have working xunit examples.
Hi, sorry about the delay, I've been away for a few weeks. What's the use case for this feature? Is it too difficult to parse the existing format and translate it to another format after the fact?
Absolutely no problem. Thanks for checking this 'issue' and thanks for your comments.
The use case: I would like to be able to generate test run summary in a single file, so that any usage of blktests in CI-like systems would be easier.
Parsing/translating existing format into any other format is sure trivial, however I would hope having top file (let it be text) combining all test results could help, if one runs blktests against many TEST_DEVS.
I would also hope, maybe naively, that allowing to generate the test run summary could help realizing problems as the one fixed in: commit ccf7dc4140706351b482b858378e62ef897ed01c Author: Klaus Jensen k.jensen@samsung.com Date: Wed Apr 22 09:44:36 2020 +0200
Fix unintentional skipping of tests
I'm working on this right now; I aim at having as little changes to the check file as possible, so that we could possibly have something working in blktests soon and then I/we could improve on this further.
I try to add following "formats" to begin with: text, xunit.
It should produce single file report under $OUTPUT/
for text: "text report generated on Mon May 11 11:23:17 CEST 2020
nodev loop/001 status pass description scan loop device partitions runtime 0.489s date 2020-05-11 11:23:17 exit_status 0
nodev loop/007 status pass description update loop device capacity with filesystem runtime 0.949s date 2020-05-11 11:23:18 exit_status 0
..."