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 D9D3444098; Wed, 22 May 2024 17:47:33 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id B594F402CE; Wed, 22 May 2024 17:47:33 +0200 (CEST) Received: from mail-ot1-f49.google.com (mail-ot1-f49.google.com [209.85.210.49]) by mails.dpdk.org (Postfix) with ESMTP id 9AAB4400D6 for ; Wed, 22 May 2024 17:47:32 +0200 (CEST) Received: by mail-ot1-f49.google.com with SMTP id 46e09a7af769-6f12eda7c7fso2989150a34.2 for ; Wed, 22 May 2024 08:47:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iol.unh.edu; s=unh-iol; t=1716392852; x=1716997652; darn=dpdk.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=s3oNPfCvSEHH4SBkIaYxl3TbAVtZMTOlbiEw+I9QUDI=; b=DP4SnXFlnUODNNTiWJkDDvenyNUAHVSB6oXeEr7YHdDUgXOQ5UvqSbGHkTSRpA5G7Q zKNycgJDhLIaLMRfZOrlWj7rR/5Pj9HuzXs3aaMq1WTTePfIs8JSBskP686Ox/5OMxKD qrM91YuonWRQaKdsRDmSYeqBXRGMzs4D/yz6o= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1716392852; x=1716997652; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=s3oNPfCvSEHH4SBkIaYxl3TbAVtZMTOlbiEw+I9QUDI=; b=MTYHaXJJ9AIMc05kCTyoZXyeHjDT1UnYWYg7SgKcyPlmR3JjQNMAxn4PTSYsf+Dk8S 4545oc92J9XzQHoDh97AbBEazfNyNEd5Q2KXgowN8y1qengt/CxLvOF8aoMi+ZbQXofr kzVmLfOjVkDwCFBgqYrpcMykw0EwHQpXHnYubYPtWSh2EWlZpi0YMwLoGB3RYaCM5wkz SJ7UHtXrSHngt3nMEcpuXhYlSn41r2Z9sg0suLu9mD0BXC8NusflQpIc1l4STbkdm44n 8cGEakk8HS0GXQzTRCwTuz8yLarujCvld2j14WaHh/0N/R/Hnm3K2qzJefN9e8SLmfrA uaYw== X-Gm-Message-State: AOJu0YzzTtK7MyntB6LMqo5h7a3k7BMYBhOcKQE6qwXt/jlkD6YccGG9 KEzNg4mQgy6ANo3EFjeV4Z3SaggdEuj2c7oo5YQ4FilJY/6ZosJD19A+zQ1qAe2psx1AXUP4PKp HAVH0K8d9RiCE7S+fsGvg11jyGLszs9gPm0UnPA== X-Google-Smtp-Source: AGHT+IEBzyskNDWg2jByPhH0L4VIPu3BGnO04ZKZ9swqw6VuiOh5r1E81E24f9CeWrxo7cfgbZ3Uqy/q2EqwdtVTgNU= X-Received: by 2002:a05:6830:1e2c:b0:6f1:2ff3:5abf with SMTP id 46e09a7af769-6f667261b3emr2509208a34.19.1716392851792; Wed, 22 May 2024 08:47:31 -0700 (PDT) MIME-Version: 1.0 References: <2926485.SvYEEZNnvj@thomas> In-Reply-To: <2926485.SvYEEZNnvj@thomas> From: Patrick Robb Date: Wed, 22 May 2024 11:47:21 -0400 Message-ID: Subject: Re: check-meson.py in CI To: Thomas Monjalon Cc: ci@dpdk.org, Ferruh Yigit , Aaron Conole , Ali Alnubani , Adam Hassick , Cody Cheng Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 On Wed, May 22, 2024 at 6:17=E2=80=AFAM Thomas Monjalon wrote: > > 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. Okay sounds good. > >