From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by sourceware.org (Postfix) with ESMTPS id 5B1E8385841F for ; Mon, 7 Mar 2022 19:04:18 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 5B1E8385841F Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=serhei.io Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=serhei.io Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 2E6E95C0278; Mon, 7 Mar 2022 14:04:18 -0500 (EST) Received: from imap47 ([10.202.2.97]) by compute5.internal (MEProxy); Mon, 07 Mar 2022 14:04:18 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=serhei.io; h=cc :cc:content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to; s=fm1; bh=PVHTj+YwdSVzJnpVQfSleelovE32PfJTXBneej 95SE4=; b=EKQDlSvUxBTZBeILhXz9BU7FdD0hzTFbChp3a/2OrUq509MNBEn10F xueWLhST/rDX6wVX8FwA/F86xTuWRdU15oppc83AgVNmPEFQj9khLFlRIuG76/NN wB9dLDVNW7faY2enumui9/BTJxhc4GP834CSmS7hC4tI0YAtHhuMctN7tixyks7z n4wZFsfB3u8XUSpCTmieCTD2EEfm09zXNcqigWQVZFhI07P2uCGkaBQ27/zL5PBD zGSR3SZv5y3l0DaYXSazpT3CLHgTgcCA5Bqt+7IADi9hmMulHclHsTH2+9iLA8VT fapn6yTzI+yjsHJV3ExXn+BrZwpn5Kfw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=PVHTj+YwdSVzJnpVQ fSleelovE32PfJTXBneej95SE4=; b=R7dqZh1bLc1bMf7cN8OlexmMU3Wb374/m guzJ17aHF0hbjWwDzAUNi5EQiO6OOET3AOEWkWe13PA5WGkcKsGP0Xbv0PoSJW9e dIHiGtKTW/Q4/uEIy84J7FZKqLpK/bm66gOxUh7guoTlbRSYAWbvGyyyOnxlWs7g lOCQHCNomOgflT/4OAHFtIYCTuOrVyt0buKgJN00as8a1yGVt9AXeSsf1syHuoUc Cymcj3yjZ/kVFVNwY3H7pTkJEokkhgdNw4zidLj47Wj/rUnZCQ5bc8sW4ZsD+NyM N87+fWise2K8TwvRPshk8dEQxxYHIVS8YfaUBDo5126sPE4WKV2vg== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddruddugedguddulecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesth dtredtreertdenucfhrhhomhepfdfuvghrhhgvihcuofgrkhgrrhhovhdfuceomhgvsehs vghrhhgvihdrihhoqeenucggtffrrghtthgvrhhnpeejtdelleffgfefveduledvjeevfe egvdejffejgfeljeelveffleetvdeukeehgfenucffohhmrghinhepghhnuhdrohhrghdp fedrudegrdeltddrvddtledpshgvrhhhvghirdhiohenucevlhhushhtvghrufhiiigvpe dtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehmvgesshgvrhhhvghirdhioh X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id E31652740108; Mon, 7 Mar 2022 14:04:17 -0500 (EST) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.5.0-alpha0-4778-g14fba9972e-fm-20220217.001-g14fba997 Mime-Version: 1.0 Message-Id: <699471ef-d43a-4d36-8ae9-5b2f657271a0@www.fastmail.com> In-Reply-To: <58451c27-bd3b-4305-b894-3862dfe76808@www.fastmail.com> References: <58451c27-bd3b-4305-b894-3862dfe76808@www.fastmail.com> Date: Mon, 07 Mar 2022 14:03:57 -0500 From: "Serhei Makarov" To: Bunsen Subject: Re: bunsen (re)design discussion #0: list of topics, review of terminology Content-Type: text/plain X-Spam-Status: No, score=-1.6 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, JMQ_SPF_NEUTRAL, KAM_BADIPHTTP, KAM_SHORT, NORMAL_HTTP_TO_IP, NUMERIC_HTTP_ADDR, RCVD_IN_DNSWL_LOW, SPF_HELO_PASS, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=no 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: Mon, 07 Mar 2022 19:04:19 -0000 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. 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 === (0) Review of Terminology Bunsen repo: collection of test result data managed by Bunsen source repo: Git repo with the source code of the project being tested project: identifier of the project being tested, e.g. 'gdb', 'systemtap' - One Bunsen repo can include data from multiple projects. - By default, Bunsen analysis is run on data from one project at a time. This can be overridden by providing a list of projects e.g. "--project=systemtap,systemtap-incomplete". - This is useful for a setup such as gcc-jenkins http://gcc.gnu.org/jenkins / http://3.14.90.209:8080/ which produces results for several projects such as gcc,ld,... in a single testsuite run. - This is also useful when we want to split out a category of data for separate analysis (e.g. projectX-incomplete for projectX testsuite runs that crashed partway through and therefore don't include full results for all testcases). testlog: test result logs (a file tree of plaintext files produced by a testsuite run) - For example, testlogs from a SystemTap testsuite run might include systemtap.{sum,log} from the DejaGNU testsuite, plus additional diagnostics such as systemtap.dmesg, stap-report, sysinfo. testrun: the parsed representation of a testsuite run, currently stored in JSON format - More details on what this includes in the next email. (May have further clarifications / definitions of terms in replies to this thread.) > All the best, > Serhei > http://serhei.io