From: Keith Seitz <keiths@redhat.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: Serhei Makarov <me@serhei.io>, Bunsen <bunsen@sourceware.org>
Subject: Re: [RFC] GDB sanity test
Date: Thu, 21 Apr 2022 09:31:22 -0700 [thread overview]
Message-ID: <ef6175d1-de72-1a9e-98c5-f6129f01433a@redhat.com> (raw)
In-Reply-To: <20220421151824.GD21143@redhat.com>
On 4/21/22 08:18, Frank Ch. Eigler wrote:
>> Any other ideas how we might want to do this?
>
> If this kind of ongoing sanity checking were valuable -- comparing
> final .sum "# of FOOBAR" counts from dejagnu to parser output data,
> then the parser could do that itself every time it runs, as a
> confirmatory self-check.
Yeah, that's not a horrible idea... We still need some sort of sanity
or CI test, but it would likely be much simpler. Like just include
{project}.{log,sum} files for gdb and systemtap (and ...) and run
those as tests.
>> The one obvious missing bit is being able to easily invoke tests. Right now,
>> I just rely on "python3 -m pytest tests" to run all tests. Maybe a makefile
>> or shell script to do this would be appropriate.
>
> In the fche/bunsenql branch, there is now autoconf/automake machinery that
> lets you run "configure; make; make check" and run the bulk of your test
> in the automake style.
I saw, thanks!
So the question I have is: if I want to progress my goals w/bunsen, what
should I be doing now to help out, if anything, and where should I be
doing it (bunsenql, master)?
Keith
prev parent reply other threads:[~2022-04-21 16:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 19:01 Keith Seitz
2022-04-19 20:33 ` Serhei Makarov
2022-04-20 15:32 ` Keith Seitz
2022-04-21 15:18 ` Frank Ch. Eigler
2022-04-21 16:31 ` Keith Seitz [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=ef6175d1-de72-1a9e-98c5-f6129f01433a@redhat.com \
--to=keiths@redhat.com \
--cc=bunsen@sourceware.org \
--cc=fche@redhat.com \
--cc=me@serhei.io \
/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).