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 8661E432C9; Tue, 7 Nov 2023 18:05:05 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 21B21402D4; Tue, 7 Nov 2023 18:05:05 +0100 (CET) Received: from mail-oo1-f43.google.com (mail-oo1-f43.google.com [209.85.161.43]) by mails.dpdk.org (Postfix) with ESMTP id 5DEEE402A1 for ; Tue, 7 Nov 2023 18:05:03 +0100 (CET) Received: by mail-oo1-f43.google.com with SMTP id 006d021491bc7-586b512ba0aso2735532eaf.3 for ; Tue, 07 Nov 2023 09:05:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iol.unh.edu; s=unh-iol; t=1699376702; x=1699981502; darn=dpdk.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=owe+hq1e1Wmo/kbrmcqsokLgTyqjrI7RYW+iNe86p5Y=; b=UmpiFu7NXTYcYMOxFp5X1lgr9CkCfjg1kn8JrTjnNQGwk2jknXja8j5AGpgKM91ck4 tKRxHZAQWxB4133hNqlZ030F+2Cf9s4w1E2DA9KCpwrSGpec9Swr7gRB6SHh5k2wWKyv kPFi28sRDExlXnzQvArBF7YSPpr6ov0n3jyc0= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1699376702; x=1699981502; h=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=owe+hq1e1Wmo/kbrmcqsokLgTyqjrI7RYW+iNe86p5Y=; b=CryZVdmjMw+4/zN2RShaambml7k3tBLj5YIcLI5MHPsEC/7hHB1ic+ushXnPKOOVCO CyzpRFNeUBZMniCy2pfUbkZutQwhu/HiLbBWKZYhtSTyLh/tOCS0AIok3sPifnHPDbxD AwTcKp4KHO/NWx1pSuh/0Xz5+P14zOn9D4g9XWXLGxU9EzAWGCEftIgyM4ihAMwPGR5J qXAjKp8Xe8tdO2n4QEiERKvdZBLM+FFH6bLj2l2pxycefyN60k1n/S7irAP48wmruwiP ulf2/nAoY6+wAH5VAUDobu1K5RMHeClCCUGiieTu8VUdxBlTnztaOz1bujSEz86aYljA KAwA== X-Gm-Message-State: AOJu0YyV/I/rLaZbQGsdt3I5TMXwc0zt0bXFuTGyDbWAXgnldY390d3I Be6G5e4QCXim8UtcA+shUvvfo9MM0oF8iXBWcmZF/g== X-Google-Smtp-Source: AGHT+IGYGP0M3Iw9vhYifrFPkzZauwKmANuyaql19C4uKxQ7rRt79w9YoYz5mrnb5mAHdOnVi9MdBlA1Er8X3KeSIcs= X-Received: by 2002:a4a:ba05:0:b0:581:d5a6:da4a with SMTP id b5-20020a4aba05000000b00581d5a6da4amr28010268oop.1.1699376702567; Tue, 07 Nov 2023 09:05:02 -0800 (PST) MIME-Version: 1.0 References: <20231103062606.2632012-1-chaoyong.he@corigine.com> <2c06ff10-528b-43d7-8dbb-555ce6f971d1@amd.com> <92831614-6ddc-4bc0-a0c8-4fa6e41f5799@amd.com> In-Reply-To: From: Patrick Robb Date: Tue, 7 Nov 2023 12:04:51 -0500 Message-ID: Subject: Re: [PATCH 00/11] Add basic flow support for corenic firmware To: Chaoyong He Cc: Ferruh Yigit , dpdklab , oss-drivers , "dev@dpdk.org" Content-Type: multipart/alternative; boundary="000000000000b25b90060992f87a" X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org --000000000000b25b90060992f87a Content-Type: text/plain; charset="UTF-8" Sorry, now I understand what is causing confusion. When a retest is requested, that retest is done on the original dpdk artifact we created for the patchseries. We don't pull again, re-apply, and then rerun the testing. I think that is the behavior you were expecting, Ferruh. We have discussed whether this is an important option to support in future iterations of the retest-request feature. One idea is to add another option in the retest request schema which allows for the requester to indicate they want the patch re-applied onto the newer branch, and testing rerun with that new dpdk. It's good to see that this is a use case which would see application. Will be aiming to add this support in the future. --000000000000b25b90060992f87a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Sorry, now I understand what is causing c= onfusion. When a retest is requested, that retest is done on the original d= pdk artifact we created for the patchseries. We don't pull again, re-ap= ply, and then rerun the testing. I think that is the behavior you were expe= cting, Ferruh.=C2=A0

We have discussed=C2=A0whether this= is an important option to support in future iterations of the retest-reque= st feature. One idea is to add another option in the retest request schema = which allows for the requester to indicate they want the patch re-applied o= nto the newer branch, and testing rerun with that new dpdk. It's good t= o see that this is a use case which would see application. Will be aiming t= o add this support in the future.=C2=A0=C2=A0
--000000000000b25b90060992f87a--