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 1BF443858D28 for ; Thu, 7 Apr 2022 16:58:05 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 1BF443858D28 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-614-QpNLmsnGO_-4BXvzRYTvDA-1; Thu, 07 Apr 2022 12:58:03 -0400 X-MC-Unique: QpNLmsnGO_-4BXvzRYTvDA-1 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.rdu2.redhat.com [10.11.54.5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 01092899ECB; Thu, 7 Apr 2022 16:58:03 +0000 (UTC) Received: from [10.2.18.31] (unknown [10.2.18.31]) by smtp.corp.redhat.com (Postfix) with ESMTPS id E7D307C4E; Thu, 7 Apr 2022 16:58:01 +0000 (UTC) Message-ID: <1dda2480-ebb8-489a-8151-09c7e75764e1@redhat.com> Date: Thu, 7 Apr 2022 09:57:59 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.7.0 Subject: Re: bunsen (re)design discussion #0: list of topics, review of terminology To: Serhei Makarov , Bunsen References: <58451c27-bd3b-4305-b894-3862dfe76808@www.fastmail.com> <699471ef-d43a-4d36-8ae9-5b2f657271a0@www.fastmail.com> From: Keith Seitz In-Reply-To: <699471ef-d43a-4d36-8ae9-5b2f657271a0@www.fastmail.com> X-Scanned-By: MIMEDefang 2.79 on 10.11.54.5 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=-6.4 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, RCVD_IN_MSPIKE_H5, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_NONE, TXREP, T_SCC_BODY_TEXT_LINE 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, 07 Apr 2022 16:58:06 -0000 On 3/7/22 11:03, Serhei Makarov wrote: > On Mon, Mar 7, 2022, at 1:59 PM, Serhei Makarov wrote: >> ... > (once more, with proper word-wrapping for plaintext mailers; apologies) > > I'm in the process of re-evaluating and re-working some core aspects > of the Bunsen code, with input from Frank Ch. Eigler. This will result > in several public emails like this one as I sort through various > concerns. This is excellent, and while the timing might be uncomfortably "late" for my tastes, I am very glad to see this formalization happening. I am hoping to put Bunsen into production use later this year. > Initial list of topics I need to cover is below. Incidentally, it > approximately matches the sequence in which Bunsen concepts would need > to be introduced in a Bunsen man page or tutorial. > > (0) Review of Terminology > (1) Testrun Representation > - version identifiers (source_commit, package_nvr) & sorting > - configuration & whether to allow 'arbitrary' metadata > (2) Repository Layout > - splitting testruns across branches, fche's suggestion > - speculation: should we adopt SQLite? or borrow ideas from Django ORM? > (3) Analysis Pipeline > - splitting querying from analysis from formatting > - Index class represents the result of a query > - Table class represents data for formatting (as plaintext, HTML, etc.) > - configuration file format: borrowing from the 'Makefile' metaphor > to describe items of data and reports Bunsen produces, and how to > refresh each item when its dependencies change Missing: Test suite. We've touched on this before, and I just want to reiterate: THIS IS VITAL to prevent someone (realistically *me*) from breaking your work. IIUC SystemTap and GDB are the only two projects currently using (or attempting to use) Bunsen. I'd like to (minimally) see some end-to-end test suite available. Last year my main goal was to improve GDB's DejaGNU parser so that it could output identical results to DejaGNU's summary. [This is the +summarize script.] That was the first testing feature that I wanted. The next is to verify log output/cursor positions. This is another fundamental feature of the service I want to implement, comparing test .log output between arbitrary testruns. I have a list of wish-list items/cleanups that I'd like to see addressed, but I'll save those for a more appropriate time. > (0) Review of Terminology Nice! I'm good with this. Keithp