From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: fstests <fstests@vger.kernel.org>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Which dashboard do most fs developers use for the fstests results?
Date: Thu, 22 Dec 2022 20:08:51 +0800 [thread overview]
Message-ID: <701ca299-2595-c310-7c8a-2d58c65b2d4d@gmx.com> (raw)
Hi,
Recently I'm setting up my dashboard for my fstests results.
My initial inspiration comes from Josef's static pages:
http://toxicpanda.com/
Generated by the following project:
https://github.com/josefbacik/fstest-results
Then I build a similar script (using junit reporting from fstests
instead), not much results yet, but all tests will be done on aarch64 VMs:
https://h.anonymoususers.xyz:8443/results/
Generated by my poorly crafted project:
https://github.com/adam900710/fstests_result_webui
And I'm pretty sure other developers have their own dashboards.
Darrick mentioned he has his own dashboard, and Theodore mentioned he
hit several btrfs test failures.
I'm wondering if it's possible to share the dashboards for each other?
Shared dashboards have the following advantage:
- Let guys from other fses to have more reports
Ted's reports is very valuable for our btrfs guys.
If we have the access the dashboard to grab the needed info,
we're definitely going to improve our runs.
- Learn better ways to build the dashboard
I learned a lot from Josef's script, and also learned a lot from
the fstests junit report.
But I'm also wondering if there is some better ways.
One possible solution I'm still exploring is InflexDB + Grafana.
If you guys can share such dashboards, we would have better chances
to learn from each other.
Thanks,
Qu
next reply other threads:[~2022-12-22 12:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-22 12:08 Qu Wenruo [this message]
2023-01-04 17:11 ` Which dashboard do most fs developers use for the fstests results? Darrick J. Wong
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=701ca299-2595-c310-7c8a-2d58c65b2d4d@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@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