public inbox for bunsen@sourceware.org
 help / color / mirror / Atom feed
From: "Serhei Makarov" <me@serhei.io>
To: "Keith Seitz" <keiths@redhat.com>, Bunsen <bunsen@sourceware.org>
Subject: Re: [PATCH] bunsenql: Add r-dejagnu-summary
Date: Thu, 30 Jun 2022 10:05:12 -0400	[thread overview]
Message-ID: <48734b83-bb79-4f82-97d4-d589d540f056@www.fastmail.com> (raw)
In-Reply-To: <20220629160317.16735-1-keiths@redhat.com>



On Wed, Jun 29, 2022, at 12:03 PM, Keith Seitz via Bunsen wrote:
> This patch adds a bunsenql equivalent of my previous "bunsen +summarize"
> script. This can be used to output DejaGNU-like summaries for tests.
>
> This script supports limiting tests based on glob expression (although
> it does not support multiple glob expressions like +summarize) and
> "verbose" output which will output all (sub)test results. It supports both
> text and JSON output templates.
>
> The script does not use any of the pipeline-created summaries. It computes
> results directly from the data. This is useful to verify that results were
> properly imported and could be used to compare against the DejaGNU
> .sum file's summary section.
Patch looks good to me, for what it's worth.
I think it's no problem for you to just commit it since the scripts
in fche's branch are currently independent apart from
using a common SQL db.

I agree that regenerating the DejaGNU summary section
to compare against the original file is a very useful check.

      reply	other threads:[~2022-06-30 14:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-29 16:03 Keith Seitz
2022-06-30 14:05 ` Serhei Makarov [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=48734b83-bb79-4f82-97d4-d589d540f056@www.fastmail.com \
    --to=me@serhei.io \
    --cc=bunsen@sourceware.org \
    --cc=keiths@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).