From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id CEE974408F; Wed, 22 May 2024 12:17:57 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id A65144026B; Wed, 22 May 2024 12:17:57 +0200 (CEST) Received: from fhigh4-smtp.messagingengine.com (fhigh4-smtp.messagingengine.com [103.168.172.155]) by mails.dpdk.org (Postfix) with ESMTP id 5AD56400D6 for ; Wed, 22 May 2024 12:17:56 +0200 (CEST) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailfhigh.nyi.internal (Postfix) with ESMTP id A9D281140191; Wed, 22 May 2024 06:17:55 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Wed, 22 May 2024 06:17:55 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm1; t=1716373075; x=1716459475; bh=O/zf9WKef9t6fP2riFqdRqVOoE6oVNW2hCl1z33zbQw=; b= rlCapU+NZayfd8qhtnubdCArfLuKTn69dXjnH/4gid4HJTNCInIE+nC5EbvjqVqM wNn88synhRTDYkFaeXjklb2n8yCxUWRRejhTFpcEq7+HlG2UHw6lxis/M0w06puu M9VIE8gR/4aarZPB8RaPyMxWZaYdjUXHEaa42VRtWxnfmeoRbqTqIlDTdWFnnRg/ NYMfkXLpbPUDV0WGI1YXi+jRpd/NGoQaWLYgZp6ZotJDAamBaKSjc4LiDpyuxykI Nk3HV1EcMj+GV1HFYNEJkkJSld/HJum/aBZfyNsuYdXMl9o2mxHr4WRmSwvYFqcK Qfp1gG0/RZpikFJS3RDq1A== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t=1716373075; x= 1716459475; bh=O/zf9WKef9t6fP2riFqdRqVOoE6oVNW2hCl1z33zbQw=; b=l ktjSoD5AP7b/lKRXlJwiOPZRUZw9eIUX06ZGc012Y7qoupUqMAZ8SJ9g1EU2xTPT 8M6JlFzhrgtmbulma1et6bSF239s8zEUJ2DOEo/hqvbHZRYReb80UaT7lT343xAe 1R/O5DjXOCWn4S8B2kEU18/9JBTDG7ZpWwOtQDKY/ilJ41Bx7CBT2WN8IwkYejw6 Cu4JVYnpROnbwy1p0+nENuIfdeRB5N9OOY0Q7/hGuEa/Wm66+wgA9lnAL3G2EzQU G6zp4rx+FDdfDn/zJAc1d/eUsOU8azRgfmMxkQjQWrvZThI0iCA6svenFOGgCber Gx1g6xf9rq9ofIDY3h+cA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrvdeigecutefuodetggdotefrodftvfcurf hrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecuuegr ihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjug hrpefhvfevufffkfgjfhgggfgtsehtufertddttdejnecuhfhrohhmpefvhhhomhgrshcu ofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecuggftrf grthhtvghrnhepjeduveehieevuddutdevfffgtdegkeeuveejffejgedtgeegkefgvdeu gfefkeejnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomh epthhhohhmrghssehmohhnjhgrlhhonhdrnhgvth X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 22 May 2024 06:17:54 -0400 (EDT) From: Thomas Monjalon To: Patrick Robb Cc: ci@dpdk.org, Ferruh Yigit , Aaron Conole , Ali Alnubani , Adam Hassick , Cody Cheng Subject: Re: check-meson.py in CI Date: Wed, 22 May 2024 12:17:52 +0200 Message-ID: <2926485.SvYEEZNnvj@thomas> In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="utf-8" X-BeenThere: ci@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK CI discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ci-bounces@dpdk.org Hello, 21/05/2024 23:32, Patrick Robb: > Hi all, > > Ferruh has requested that we start running the > ./devtools/check-meson.py script in CI testing. Questions: > > 1. Should it be similar to how Ali runs checkpatches.sh, in that it > would have it's own patchwork context (check-meson)? I think the one > difference is that it can run just 1x/series, instead of on each > individual patch file. checkpatches.sh runs on each patch from mail check-meson.py does not understand patches, so it must be run after patches are applied. It may be nice to run it after each patch, but it is your choice. > 2. Who should run it? It would be a simple addition for the community > lab, but if there is some compelling reason for it running alongside > checkpatch, let me know Ali. We don't apply patches on dpdk.org. It would be more convenient to integrate it inside UNH pipeline please.