From: David Disseldorp <ddiss@suse.de>
To: fstests@vger.kernel.org
Subject: [PATCH 0/2] report: optionally gzip xunit output
Date: Mon, 14 Sep 2026 23:46:10 +1000 [thread overview]
Message-ID: <20260914140710.111641-1-ddiss@suse.de> (raw)
I collect fstests xunit reports for (possible) later analysis. The XML
compresses quite well: for an auto group run with a handful of failures,
uncompressed xunit is typically 10x larger than a gzipped result.xml.
This mostly trivial patchset adds a new xunit-gzip report type. The same
can be achieved via e.g.
./check -R xunit ... && gzip <REPORT_DIR>/result.xml
check | 2 +-
common/report | 97 +++++++++++++++++++++++++++++----------------------
2 files changed, 57 insertions(+), 42 deletions(-)
next reply other threads:[~2026-09-14 14:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-14 13:46 David Disseldorp [this message]
2026-09-14 13:46 ` [PATCH 1/2] report: put failure cdata collection in a helper fn David Disseldorp
2026-09-14 13:46 ` [PATCH 2/2] report: add xunit-gzip report type David Disseldorp
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260914140710.111641-1-ddiss@suse.de \
--to=ddiss@suse.de \
--cc=fstests@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox