From: Chuck Lever <chuck.lever@oracle.com>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: Tso Ted <tytso@mit.edu>,
kdevops@lists.linux.dev, fstests <fstests@vger.kernel.org>,
Linux FS Devel <linux-fsdevel@vger.kernel.org>
Subject: Re: Automation of parsing of fstests xunit xml to kicdb kernel-ci
Date: Thu, 17 Apr 2025 12:53:56 -0400 [thread overview]
Message-ID: <fcf7af77-1f2e-4b07-abb2-f7c0740ebdfc@oracle.com> (raw)
In-Reply-To: <aAEp8Z6VIXBluMbB@bombadil.infradead.org>
On 4/17/25 12:18 PM, Luis Chamberlain wrote:
> We're at the point that we're going to start enablish automatic push
> of tests for a few filesystems with kdevops. We now have automatic
> collection of results, parsing of them, etc. And so the last step
> really, is to just send results out to kicdb [0].
>
> Since we have the xml file, I figured I'd ask if anyone has already
> done the processing of this file to kicdb, because it would be easier
> to share the same code rather than re-invent. We then just need to
> describe the source, kdevops, version, etc.
>
> If no one has done this yet, we can give it a shot and we can post
> here the code once ready.
>
> [0] https://docs.kernelci.org/kcidb/submitter_guide/
>
> Luis
>
https://git.nowheycreamery.com/anna/xfstestsdb.git is one possible
solution.
--
Chuck Lever
next prev parent reply other threads:[~2025-04-17 16:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-17 16:18 Automation of parsing of fstests xunit xml to kicdb kernel-ci Luis Chamberlain
2025-04-17 16:53 ` Chuck Lever [this message]
2025-04-17 16:54 ` Luis Chamberlain
2025-04-17 16:54 ` Luis Chamberlain
2025-04-18 14:54 ` Gustavo Padovan
2025-04-18 19:28 ` Luis Chamberlain
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=fcf7af77-1f2e-4b07-abb2-f7c0740ebdfc@oracle.com \
--to=chuck.lever@oracle.com \
--cc=fstests@vger.kernel.org \
--cc=kdevops@lists.linux.dev \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=tytso@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).