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 0A7194326D; Thu, 2 Nov 2023 11:44:58 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 0383840282; Thu, 2 Nov 2023 11:44:58 +0100 (CET) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by mails.dpdk.org (Postfix) with ESMTP id E117840262 for ; Thu, 2 Nov 2023 11:44:56 +0100 (CET) Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 2205A5C01CA; Thu, 2 Nov 2023 06:44:56 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Thu, 02 Nov 2023 06:44:56 -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:sender:subject:subject:to:to; s=fm3; t= 1698921896; x=1699008296; bh=dWjXJxUAmVD6S11AFFrM3+7gn7gDlI7mWaa pwx9Ww08=; b=bJqDVn5BQZ2fwagqSh6Bxo2ZhagFTGRN4Wh2wwJ/CFyU8cxodRV J+uwsFh6+KxHl9Cj0lnKzLPSC/8bCFiGkAA/cZHlY8POdIen6Goo28s3pG7FCJMM 2Zw1eHZj0WB/Mj9bUMl95mAy0oAhrjoHOakS3Lp7lcKbRs8yX3I+zBOZYqftbt23 QbGdOAfFwabnsppWbeNf9JC9z3QsbW6rizQ98NPF9NisnLFsaHiNgo21eDpqlME1 ijqcAxfNFHrXpDNJvrnMaoTN9kNIcc/4orajPrD5litfPPwE2mNPxiz3kheIOm1U 0xVeQIr8uuU5bHT5SOX+l6O9bww2sgQzQeA== 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:sender:subject:subject:to:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t= 1698921896; x=1699008296; bh=dWjXJxUAmVD6S11AFFrM3+7gn7gDlI7mWaa pwx9Ww08=; b=J8lMMQxYtxvZ+jE3SwEhShoUFQhm67HBdBpki+MFhviBjU3k2EG t2BU+Yq06CqRZmsBGOJ5GD/HdEhpGj9+0tzHQK+TV2vNU8k3UV6/ClTf34WU8IEg LORXNcmAARIj26yF33KtDea9VAocuoVPzZCDwNXbejZmMhYT1mvak2GOb14a15Q6 VQunYxbBP0Kbo/LvTxwgRA69LfV1b3RERO16HvhJU+i8KNa6JaXo5GAUWz+AsEqI PxPjB95CQX58OSEYvUEZQbjOAF3Hlc0puLrjDdNcd1n/KyWkDvX5Eor5qPFw0whD /Q/4Pew8NHMNsLw0AfHdBAtqCjcv11/Gz3w== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedruddtiedgudelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvvefufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhm rghsucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenuc ggtffrrghtthgvrhhnpedtjeeiieefhedtfffgvdelteeufeefheeujefgueetfedttdei kefgkeduhedtgfenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfh hrohhmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvght X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 2 Nov 2023 06:44:54 -0400 (EDT) From: Thomas Monjalon To: Aaron Conole Cc: Michael Santana , ci@dpdk.org, Dumitru Ceara , David Marchand , Ilya Maximets , ci@dpdk.org Subject: Re: [RFC 2/2] recheck: Add a recheck parser for patchwork comments Date: Thu, 02 Nov 2023 11:44:53 +0100 Message-ID: <1912626.taCxCBeP46@thomas> In-Reply-To: References: <20231027130609.3035396-1-aconole@redhat.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" 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 01/11/2023 20:16, Aaron Conole: > Michael Santana writes: > > I like this workflow. The only thing that I do not like is that you > > have to check every comment on every patch. That seems like an > > expensive operation, but honestly I do not think there is a better way > > to accomplish this. So if there is no better way to do it then it's > > okay, let's move forward with it > > There isn't a different way to do it for now, but I hope to switch to > using the events API which should mean we only look at the most recent > events that come in. What prevent us to use the events API?