From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by sourceware.org (Postfix) with ESMTPS id 4705A3856DFA for ; Thu, 21 Apr 2022 16:31:28 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 4705A3856DFA Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-86-0x4CXM8gN5OyK7gYuPmXqg-1; Thu, 21 Apr 2022 12:31:26 -0400 X-MC-Unique: 0x4CXM8gN5OyK7gYuPmXqg-1 Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.rdu2.redhat.com [10.11.54.1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 40422800B28; Thu, 21 Apr 2022 16:31:26 +0000 (UTC) Received: from [10.2.17.182] (unknown [10.2.17.182]) by smtp.corp.redhat.com (Postfix) with ESMTPS id DC69F409B3E9; Thu, 21 Apr 2022 16:31:25 +0000 (UTC) Message-ID: Date: Thu, 21 Apr 2022 09:31:22 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.8.0 Subject: Re: [RFC] GDB sanity test To: "Frank Ch. Eigler" Cc: Serhei Makarov , Bunsen References: <20220419190117.903678-1-keiths@redhat.com> <21b838a8-1744-4c3b-8f41-f2c44ffcc9e3@www.fastmail.com> <41037236-1123-9d34-178e-65a840ff3617@redhat.com> <20220421151824.GD21143@redhat.com> From: Keith Seitz In-Reply-To: <20220421151824.GD21143@redhat.com> X-Scanned-By: MIMEDefang 2.84 on 10.11.54.1 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Language: en-US Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-7.0 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, NICE_REPLY_A, RCVD_IN_DNSWL_LOW, SPF_HELO_NONE, SPF_NONE, TXREP autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: bunsen@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Bunsen mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Apr 2022 16:31:29 -0000 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