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 C88B8385841F for ; Mon, 7 Mar 2022 19:00:00 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org C88B8385841F 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 DD1DC5C0338; Mon, 7 Mar 2022 13:59:58 -0500 (EST) Received: from imap47 ([10.202.2.97]) by compute5.internal (MEProxy); Mon, 07 Mar 2022 13:59:58 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=serhei.io; h=cc :cc:content-transfer-encoding:content-type:date:date:from:from :in-reply-to:message-id:mime-version:reply-to:sender:subject :subject:to:to; s=fm1; bh=bfYS/2beJ04hdQ4MOUVGIFs+a8LHhHas9CgM8p 1iNGE=; b=M1krO4oaiQAcsgbw+dC3PqjYXuY6Sds3pSIZjZPEpo1p2cFcLQepQH KqU8DzfOVWdaweHSwlAvmPMXaQe9eiz0lXJP7/UBSmsPikuqphD1AiWlpVJaS+t8 ldSfOegGhkd3YVrugNLdT0Jc+8YUB31W/yXx7Vftjfi+aMuxUN/q2iw5Bkujzsj2 KZ1ipKowXek8PoQr+ClRaDJA9efBPmsnUaijVgmRAkFr8MN86uWMnMbmYtFtluG5 h8yfuyQZ6n5HL+brT98MIu0Sf7ytgans0AzaOMJUoYCmJa9IN9raOZ+o2HchH3DP falDHYV8ZM8l4XaKTNJPhOd56+s1uDog== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:from:from:in-reply-to:message-id :mime-version: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=bfYS/2 beJ04hdQ4MOUVGIFs+a8LHhHas9CgM8p1iNGE=; b=krQY371QbkyV/e01Mi7QOY w2J3QtISABW7IfGOGBqcB0nQiB8LUZFxgr3hNiXXNwGTaKB1jJvxYgebdsO3mssr ewXkVmnPk95h0Ro2uwAVPY8sbbBIdIvZ2v0G6AyHmsH5H4wd1pKc0DJVuPXEVCnv gDDiGVKGHZr5mXZAnGTFqempJ+Zds5CEA7eT0Ykp+4udvkOIXz51ONUZY+xmPmtx ZQw5MbzmA+r7512eR54pc4wtIhaXNKVOVe0xD/6FcCDYzteVw5xYDbxzfOUvxZ9U 1x90UD7YGaDIV2HCsC/Y3bEur3NloPMlKM9RKvrx0AAKwhr7/n1uAHTPVwVA6Sjw == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddruddugedguddukecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkfffhvffutgfgsehtqh ertderreejnecuhfhrohhmpedfufgvrhhhvghiucforghkrghrohhvfdcuoehmvgesshgv rhhhvghirdhioheqnecuggftrfgrthhtvghrnhepgfeuieetheekveelhfefteffgfevke ejtdeivdefkedugfeiffevhfdvieeuheetnecuffhomhgrihhnpehgnhhurdhorhhgpdef rddugedrledtrddvtdelpdhsvghrhhgvihdrihhonecuvehluhhsthgvrhfuihiivgeptd enucfrrghrrghmpehmrghilhhfrhhomhepmhgvsehsvghrhhgvihdrihho X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id 8701E2740067; Mon, 7 Mar 2022 13:59:58 -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: <58451c27-bd3b-4305-b894-3862dfe76808@www.fastmail.com> Date: Mon, 07 Mar 2022 13:59:05 -0500 From: "Serhei Makarov" To: Bunsen Subject: bunsen (re)design discussion #0: list of topics, review of terminology Content-Type: text/plain;charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-1.7 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:00:03 -0000 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 s= everal public emails like this one as I sort through various concerns. Initial list of topics I need to cover is below. Incidentally, it approx= imately matches the sequence in which Bunsen concepts would need to be i= ntroduced in a Bunsen man page or tutorial. (0) Review of Terminology (1) Testrun Representation =C2=A0 - version identifiers (source_commit, package_nvr) & sorting =C2=A0 - configuration & whether to allow 'arbitrary' metadata (2) Repository Layout =C2=A0 - splitting testruns across branches, fche's suggestion =C2=A0 - speculation: should we adopt SQLite? or borrow ideas from Djang= o ORM? (3) Analysis Pipeline =C2=A0 - splitting querying from analysis from formatting =C2=A0 - Index class represents the result of a query =C2=A0 - Table class represents data for formatting (as plaintext, HTML,= etc.) =C2=A0 - configuration file format: borrowing from the 'Makefile' metaph= or to describe items of data and reports Bunsen produces, and how to ref= resh each item when its dependencies change =3D=3D=3D (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. =C2=A0=C2=A0 - By default, Bunsen analysis is run on data from one proje= ct at a time. This can be overridden by providing a list of projects e.g= . "--project=3Dsystemtap,systemtap-incomplete". =C2=A0=C2=A0 - 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 s= everal projects such as gcc,ld,... in a single testsuite run. =C2=A0=C2=A0 - This is also useful when we want to split out a category = of data for separate analysis (e.g. projectX-incomplete for projectX tes= tsuite runs that crashed partway through and therefore don't include ful= l 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 sys= temtap.{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 th= is thread.) All the best, Serhei http://serhei.io