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 880ECA00C2 for ; Tue, 27 Sep 2022 11:19:35 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 6682941133; Tue, 27 Sep 2022 11:19:35 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by mails.dpdk.org (Postfix) with ESMTP id B44C8410D0 for ; Tue, 27 Sep 2022 11:19:33 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1664270373; 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=yUZI0WyQ1h9j9nCTbuAJ59RizRCWrunFeuOkX5MzqCA=; b=NT9uYjBk5THgGmJcszihcDqjvA78jJRkCuxP4rhLcvdgmdksoMNUXSFOSHI/Pa/35Euj60 cgBtkfx3oVR82PJvPRIpMAwz+5KBXhMHJ/J1ecfG4jT+KDTL3ofvGfwywg3bXPo96M2WV+ QtSPEvxtNU4OpRX2AlN7sHHB5QCOrkA= Received: from mail-pg1-f198.google.com (mail-pg1-f198.google.com [209.85.215.198]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_128_GCM_SHA256) id us-mta-583-RJ1Q1IaWPP611jrVp2vl9Q-1; Tue, 27 Sep 2022 05:19:32 -0400 X-MC-Unique: RJ1Q1IaWPP611jrVp2vl9Q-1 Received: by mail-pg1-f198.google.com with SMTP id g66-20020a636b45000000b0043a256d3639so5480448pgc.12 for ; Tue, 27 Sep 2022 02:19:31 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; 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; bh=yUZI0WyQ1h9j9nCTbuAJ59RizRCWrunFeuOkX5MzqCA=; b=oIdLoSzX7hdKeCVwCEb/ap50BlmBRd4sWOebHdmYxgk84etjVeBbYQ+n/qWYpPH655 AMmeaYik/9XtPFMHuI/MjTx3bEypbfT/mAlyUP/xYNENJyedmC3FLNKkgKhTDud1FqdO /qC9ju9KKHkF4jlpLHR2w/BqHctucpFMJZv8d8Bv15sPJ7wpO0fkGqpJegv2pp5NxtNX fqSBLMByh6FkAuu1N/3Y0VC6LoxYJN6woRnJ5u3l8P1ejTzhcDjmOCTcaLCbMW2UwvqW 6kxoAKkmX9hHtf1Sj3CSW7e9vb0gYr80TQCZjuXgjq2MESiR0PxY5EoAxMVtnpwjbv8L PoPQ== X-Gm-Message-State: ACrzQf16DnMjYS++dz0TudoK/ssYJ+NyDflN+go0/DsCPRwXGiKPXV0U zP7LnZhYBcpxZG/idOapXebon9iZZp73R63FpNWkIDU50wGzkNhHl1wXfvkNlycTryl6kqQFHbV OpnonfGSZGGObXnihJA== X-Received: by 2002:a17:902:7786:b0:178:48c0:a083 with SMTP id o6-20020a170902778600b0017848c0a083mr26531955pll.125.1664270370994; Tue, 27 Sep 2022 02:19:30 -0700 (PDT) X-Google-Smtp-Source: AMsMyM4il9gOhOvV4rzodOk4vAgG5ftw6I/gfs40/nz3r0GqgnOOY6DebETyCu+GEv0sGqK/H1eTW+CNPTsObxfpsK4= X-Received: by 2002:a17:902:7786:b0:178:48c0:a083 with SMTP id o6-20020a170902778600b0017848c0a083mr26531940pll.125.1664270370721; Tue, 27 Sep 2022 02:19:30 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: David Marchand Date: Tue, 27 Sep 2022 11:19:19 +0200 Message-ID: Subject: Re: facing _apply patch failure_ warning To: "Naga Harish K, S V" , dpdklab Cc: "aconole@redhat.com" , "ahassick@iol.unh.edu" , "Jayatheerthan, Jay" , Jerin Jacob , "dev@dpdk.org" , ci@dpdk.org X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com 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 Hello, Please, don't top post, I reordered your reply to keep the context in a logical order. On Tue, Sep 27, 2022 at 11:06 AM Naga Harish K, S V wrote: > > From: David Marchand > > On Mon, Sep 26, 2022 at 9:54 AM Naga Harish K, S V > > > I am facing _apply patch failure_ warning for one of my patchsets a= s > > below. > > > > > > https://lab.dpdk.org/results/dashboard/patchsets/23622/ > > > > > > http://mails.dpdk.org/archives/test-report/2022-September/309233.html > > > > > > Looks like the patch is being applied for dpdk branch, but the patchs= et is for > > =E2=80=9Cdpdk-next-eventdev=E2=80=9D branch. > > > > Testing locally, the script seems to correctly identify the branch: > > $ ./tools/pw_maintainers_cli.py --pw-server > > https://patchwork.dpdk.org/api/1.2 --pw-project dpdk --pw-token XXX lis= t- > > trees --type series 24817 dpdk-next-eventdev > > > > Not sure what went wrong. > > > > > > > > Can you help in applying the patch to correct branch (dpdk-next- > > eventdev)? > > > > I manually triggered a test of this patch against this branch. > > Hi David, > Thanks for triggering test. > The "_apply patch failure_" warning still shows for the patch. Is this fi= ne? I guess the UNH CI does not send a report clearing a previous error. This might be something to fix (ping @UNH, low priority in any case). In any case, this warning is not a reason to block your patch. --=20 David Marchand