From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: passt.top; dmarc=pass (p=quarantine dis=none) header.from=redhat.com Authentication-Results: passt.top; dkim=pass (1024-bit key; unprotected) header.d=redhat.com header.i=@redhat.com header.a=rsa-sha256 header.s=mimecast20190719 header.b=KVMXk414; dkim-atps=neutral Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by passt.top (Postfix) with ESMTPS id 948995A0271 for ; Wed, 03 Sep 2025 23:14:58 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1756934097; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=wg97eMkYrQvFk3cZ8vFsuObjyIZG7SwpfGlSuHkvz3k=; b=KVMXk414Yz2y4wSIG0J4D6eFA+Y1O9V0J/nST43FQ117GBYkC51apy4c69rSMxLd5RJw+m 7+QuTrCKsBQ826sMmmB+WnMLQmR/sBFxcIhs/jxEA2cYYv5f8wEdxKeBLL1QNt0Koq71um JVswRnbmV820pllrEHyy8Na5QydJIf4= Received: from mail-wm1-f70.google.com (mail-wm1-f70.google.com [209.85.128.70]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-517-cb6ZuPk4M6GzSLtVWdpMLQ-1; Wed, 03 Sep 2025 17:14:56 -0400 X-MC-Unique: cb6ZuPk4M6GzSLtVWdpMLQ-1 X-Mimecast-MFC-AGG-ID: cb6ZuPk4M6GzSLtVWdpMLQ_1756934095 Received: by mail-wm1-f70.google.com with SMTP id 5b1f17b1804b1-45b869d3572so1895575e9.1 for ; Wed, 03 Sep 2025 14:14:55 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1756934094; x=1757538894; h=content-transfer-encoding:mime-version:organization:references :in-reply-to:message-id:subject:cc:to:from:date:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=wg97eMkYrQvFk3cZ8vFsuObjyIZG7SwpfGlSuHkvz3k=; b=fA2zcFWsZ+cCyuvL/4S3FrvkIPcXCw4gen3c/ffz12nybBUlLdaXRrXwuewB+0DlaD SWIAs0C2E2uitOzURFRcm2j3m5OLrQ+OocpVoxo8BWFPE+xFUQ/a5pLUFtIEsfGygN/9 CDsiNhjU5hygOdTEnOMN6C0kX0n3YBKbnKVmu+NeWdvcqDM05PyNuym2sxadB7Svlkmf AKXBt+o6XGem/vPv8ggYNLNGeekjY83HP4hC3ZDKb4dShBQEn5hiqjrl7jbSjLWx9byf EgsE3jkbdqv6KkkN9l+ptk8sNd4MMQQnP5VaPK9ywbnF3Qq0aDUeuANTD7z5QhEPv6EI VmxQ== X-Gm-Message-State: AOJu0YyX2lXvCb7sfl7ACcybP8yT7VRL8o3KtsjU6d+3Y3SBtj1Np63F IOoWW2r6x+8e5fUGHPxBrEiVOnQ78kftPDKM2tk1bCeBi5x7QpKn2emPcL+ZBYKTfnsMaOaiOfn kxL5OlggXmLqkg/urbJ9r/CHwENRSxsnTsDFZMLjG7V79EJLFIn+jHxP81cmrcg== X-Gm-Gg: ASbGnct6wVmevpBjnSzaI9WAdHAYgOAzoRb68CJZMuhU+IJgYSRxHVjf/bY74iwTRVg lwf4HhncevsiI+UuHuF0m8jdQzZlMT3TASHa8XyOej6YjJErd219vOSHB/mHdVUWet5U3EdaXXg +CdH2ioKH19N74j0GRkUJ6odUkd3w2oO0yhNmDVioE1PCrZ9Any3DnqMVuvidSYSzSCVz/IpBu/ J0YLd6ulnFyiqL+jP/AEQSImTbPuMaZy0EWXgN7v6QfqgPhIIdQc2Okbx8g6tfKM36Ze4KJ3JK3 jMvZMWZhmfOUdqDSG6p8IRAiD2r2mDrC1m+gIhmrZdZACrW41lNBy5R3XTtvgkKpz68K X-Received: by 2002:a05:600c:c4ac:b0:458:a992:6f1e with SMTP id 5b1f17b1804b1-45b85526106mr157896485e9.5.1756934094073; Wed, 03 Sep 2025 14:14:54 -0700 (PDT) X-Google-Smtp-Source: AGHT+IG4qq3LeiPjQ7D1FZzvsH4XUeeyHxIDQ2IvKeyl22qrignuTGg6Nqw4mBfgIKj0/WhM7NpqJg== X-Received: by 2002:a05:600c:c4ac:b0:458:a992:6f1e with SMTP id 5b1f17b1804b1-45b85526106mr157896395e9.5.1756934093657; Wed, 03 Sep 2025 14:14:53 -0700 (PDT) Received: from maya.myfinge.rs (ifcgrfdd.trafficplex.cloud. [176.103.220.4]) by smtp.gmail.com with ESMTPSA id 5b1f17b1804b1-45dcfc414f4sm3998515e9.0.2025.09.03.14.14.53 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 03 Sep 2025 14:14:53 -0700 (PDT) Date: Wed, 3 Sep 2025 23:14:35 +0200 From: Stefano Brivio To: David Gibson Subject: Re: [PATCH v6 0/4] New proof-of-concept based exeter tests Message-ID: <20250903231435.11a1bdab@elisabeth> In-Reply-To: <20250901042515.138861-1-david@gibson.dropbear.id.au> References: <20250901042515.138861-1-david@gibson.dropbear.id.au> Organization: Red Hat X-Mailer: Claws Mail 4.2.0 (GTK 3.24.49; x86_64-pc-linux-gnu) MIME-Version: 1.0 X-Mimecast-Spam-Score: 0 X-Mimecast-MFC-PROC-ID: 4Jg9Vz2m-SZzATd396iskrXbHcTVA9EICc3ZgMR6BlI_1756934095 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-ID-Hash: VWCUARJTLGV55TX73OMLK6V5WHBMES5D X-Message-ID-Hash: VWCUARJTLGV55TX73OMLK6V5WHBMES5D X-MailFrom: sbrivio@redhat.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: passt-dev@passt.top X-Mailman-Version: 3.3.8 Precedence: list List-Id: Development discussion and patches for passt Archived-At: Archived-At: List-Archive: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On Mon, 1 Sep 2025 14:25:11 +1000 David Gibson wrote: > Here's a new approach to building passt tests with exeter. This new > one no longer uses Avocado in the default case, although it would > still be possible to manually run the exeter based tests with Avocado. > > Here's another draft of my work on testing passt with Avocado and the > exeter library I recently created. It includes Cleber's patch adding > some basic Avocado tests and builds on that. > > For now this only does simple tests, to show how the integration could > work. It adds some new trivial "smoke tests" and converts the linter > and build checks to exeter. More complex tests will require building > the sinte/pesto library we've discussed. A lot of the work for that > already exists in my earlier exeter test series, but it will need some > rework to split it into a separate component. > > v6: > * Use exeter's new metadata support to print nicer test names Thanks, it looks much more readable now. And to me it looks ready to merge, but I hit something during testing that I'm not quite sure how to solve, assuming it can be considered an issue at all. Initially, I hadn't upgraded my local copy of exeter, so even smoke tests would fail, until it occurred to me that of course I needed to drop the 'exeter' directory and 'make exeter' again. It's an issue we conceptually already have with mbuto (even though it didn't get breaking changes for months now) and with Podman to some extent. With exeter, I guess we're going to hit that kind of issue pretty frequently at least in the near future. So I was wondering: should we enforce some form of up-to-date check from test/Makefile? I'm personally fine without it and, given that I plan to update test/README.md soon anyway ('make' under test/ is not mentioned at all), I can mention this kind of problem as well, so it shouldn't be a big deal for others. But I wanted to know if you have thoughts or proposals on the matter, before applying this. -- Stefano