From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) by sourceware.org (Postfix) with ESMTPS id 887AB3858D28 for ; Sat, 9 Apr 2022 02:23:15 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 887AB3858D28 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.west.internal (Postfix) with ESMTP id C75903201DDB; Fri, 8 Apr 2022 22:23:12 -0400 (EDT) Received: from imap50 ([10.202.2.100]) by compute5.internal (MEProxy); Fri, 08 Apr 2022 22:23:13 -0400 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=32Gcim1F9NUN1HmLIyXCI84yj9cFzeZG0Qwjrt zRVE4=; b=ilGcO9ThxBA2Ldje+e5W2I3VXyb8PJEr4L+MDRXLBxrSFQ8gXFmRtM 4cNYquVzBIlh0BwdydbjIgVFAWrfWY/azx6ekyJCNTg9GTJNCasGmAImCRDUrSPH vzlY8VKdXC0G2cykY8dOi3nulS1FbGpYqSeC9PK+1RPZFeaEMXtDGRPBYVYU06Ty QswDsG1vPg72GaxCyZVpjJVowdcd2JEk99UeVgdn1n6JOlmyKzVTXMeA67epYIi4 Jkdizxna/vO8dnIqu1pbpKE/qCdb2kjxBraJwKIz7x4TaljyG9kOQ0q7Q1aAaOCw XTZsfjJAP/SMfQkGFOQBakJggdFpg+hQ== 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=fm3; bh=32Gcim1F9NUN1HmLI yXCI84yj9cFzeZG0QwjrtzRVE4=; b=SLgO1onqBrkDrY4WvMHdHzUWBEazUbFJg bAUEBXEP+lWK6/aqIOIOYX9+yjuUak7XV8MGtyBCbuYjj9b7MERjMYsJwsXpQfpK wWB7gb64AAPx/latw+NCLGUCWAhzQlZCODQhQYc5A8C3HjUy5UsyAHVXhvipJS1i ojM0tSxXgyZjybR1IevY+eN9MgCOoIqBWVPnfkD+PymzgfhIVl5YWr8Qn/qoX5Rp xYdlKe4y2KFZsjTdkqNt601UiafnwBq6Yro5y+jr8nRl4kJU4JLKt5e841jKwfJm aQJ6yAQ659VvYCDQPQWZ6h3ZVRDfTKPrxzew4lxetk6+TciXucefA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrudekuddgheehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvffutgesthdtredtreertdenucfhrhhomhepfdfuvghr hhgvihcuofgrkhgrrhhovhdfuceomhgvsehsvghrhhgvihdrihhoqeenucggtffrrghtth gvrhhnpeefjefggfegffduheeitdeltdegjedtkefgueelhedutdfggedvgffhjeekiefg tdenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehmvg esshgvrhhhvghirdhioh X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id CDA5A1920089; Fri, 8 Apr 2022 22:23:11 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.7.0-alpha0-386-g4174665229-fm-20220406.001-g41746652 Mime-Version: 1.0 Message-Id: In-Reply-To: <20220409015645.GF23295@redhat.com> References: <58451c27-bd3b-4305-b894-3862dfe76808@www.fastmail.com> <699471ef-d43a-4d36-8ae9-5b2f657271a0@www.fastmail.com> <1dda2480-ebb8-489a-8151-09c7e75764e1@redhat.com> <20220409015645.GF23295@redhat.com> Date: Fri, 08 Apr 2022 22:22:50 -0400 From: "Serhei Makarov" To: "Frank Ch. Eigler" Cc: "Keith Seitz" , Bunsen Subject: Re: bunsen (re)design discussion #0: list of topics, review of terminology Content-Type: text/plain X-Spam-Status: No, score=-3.3 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, JMQ_SPF_NEUTRAL, RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H5, RCVD_IN_MSPIKE_WL, SPF_HELO_PASS, SPF_PASS, 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: Sat, 09 Apr 2022 02:23:17 -0000 On Fri, Apr 8, 2022, at 9:56 PM, Frank Ch. Eigler wrote: > Hi - > >> > 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. [...] > > That should be straightforward with the new git/sqlite scheme too. > One can freeze a git repo for fixed testing, or one can edit one > under testsuite control. And one can easily query the resulting > datasets for expected values. Should be no problem at all for at > least the analysis side of the house. Sure, indeed sticking a frozen sample db into the testsuite might be essential if we end up designing a schema that is an API, then end up evolving the schema in a way that requires migrations, then an existing copy of the db will be an important data source to test against. On the other hand, if the db is a purely transient structure (we can always re-create it from either pure or indexed testlog data, and 'migration' amounts to re-creating any analysis structures that are obsolete) then need to test against a frozen db is somewhat less. Step 1 of the testing is then to create a db, then run various tests against it. That is, if the implied design promise that db-regeneration is indeed quick and easy pans out on larger datasets :-P In any case, after digesting Frank's sample code for sqlite migration, I have a clearer idea of what pieces to adopt in a way that keeps continuity with the existing functionality. I'll do my own quick-experiment-in-a-separate branch to clarify what I want from the structure. -- All the best, Serhei