public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: fstests <fstests@vger.kernel.org>,
	"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Which dashboard do most fs developers use for the fstests results?
Date: Wed, 4 Jan 2023 09:11:21 -0800	[thread overview]
Message-ID: <Y7WzOXfIjmh1R4RO@magnolia> (raw)
In-Reply-To: <701ca299-2595-c310-7c8a-2d58c65b2d4d@gmx.com>

On Thu, Dec 22, 2022 at 08:08:51PM +0800, Qu Wenruo wrote:
> 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.

Yep.  https://djwong.org/fstests/

Source: https://djwong.org/docs/fstmatrix.tar.xz

The tarball contains source to build four debian packages (poorly).  One
for the database itself (fugly slow sqlite); one that gets installed in
a test VM to collect, package, and submit fstests results to a
webserver; one to be the web service endpoint that accepts tarballs and
integrates the results into the database; and one to present a web
frontend and an rss feed based on db contents.

No auditing has been done on /any/ of it.  No authentication is
required.  Please don't bomb my machine.

> 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

Yes, that would be useful to cross-reference problems I see against
whatever Ted and Josef are running.  Granted I could do that today with
Josef's dashboard, but ... I don't.

>   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.

Probably smarter than building your own web dashboard, but I don't have
any experience with either of those tools.

--D

>   If you guys can share such dashboards, we would have better chances
>   to learn from each other.
> 
> Thanks,
> Qu

      reply	other threads:[~2023-01-04 17:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-22 12:08 Which dashboard do most fs developers use for the fstests results? Qu Wenruo
2023-01-04 17:11 ` Darrick J. Wong [this message]

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=Y7WzOXfIjmh1R4RO@magnolia \
    --to=djwong@kernel.org \
    --cc=fstests@vger.kernel.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=quwenruo.btrfs@gmx.com \
    /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