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 2E2BA41EBD for ; Fri, 17 Mar 2023 15:59:53 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 29CEA42FBE; Fri, 17 Mar 2023 15:59:53 +0100 (CET) Received: from linux.microsoft.com (linux.microsoft.com [13.77.154.182]) by mails.dpdk.org (Postfix) with ESMTP id ED72D40395 for ; Fri, 17 Mar 2023 15:59:50 +0100 (CET) Received: by linux.microsoft.com (Postfix, from userid 1086) id 4425E20C343B; Fri, 17 Mar 2023 07:59:50 -0700 (PDT) DKIM-Filter: OpenDKIM Filter v2.11.0 linux.microsoft.com 4425E20C343B DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.microsoft.com; s=default; t=1679065190; bh=UNtiUZ/112yjBVqLL25Kb5xUmwG9gVQdswDT1mq4QL4=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=oo4p0ORHgq82pn5OloTReZZuPLIa0GMZvwpFF7lG3g5pf3gszZVfm1SvcJD7RY3po Q+GGNfVv6jsKBHVSoSFSBlklrygRmTzUEVWX9SHbebemJCsptdy6LXSqJBMdas2eiK ZYmh5tn6PJMQgebl+6sMAcGyuEkCmPBvqnt19kb4= Date: Fri, 17 Mar 2023 07:59:50 -0700 From: Tyler Retzlaff To: "Huang, ChenyuX" Cc: David Marchand , "Gao, DaxueX" , "ci@dpdk.org" , Aaron Conole , Thomas Monjalon Subject: Re: Diagnosing CI Failures Question Message-ID: <20230317145950.GB29683@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net> References: <20230316165126.GB8277@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) 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 Fri, Mar 17, 2023 at 04:27:24AM +0000, Huang, ChenyuX wrote: > There is a problem with the ci machine and it has been repaired. No problem with the new report Is there a way to "re-run" existing patch sets through the ci/intel-Functional tests? or is the only way to re-submit the same series to dev@dpdk.org? Additionally, in the case of failures how do we extract artifacts for diagnosis? for large tree-wide changes it's quite difficult to rely entirely on code review to guess what caused a failure. Thanks! > > > Huang, Chenyu > BRS > > > -----Original Message----- > > From: David Marchand > > Sent: Friday, March 17, 2023 1:00 AM > > To: Tyler Retzlaff ; Gao, DaxueX > > ; Huang, ChenyuX > > Cc: ci@dpdk.org; Aaron Conole ; Thomas Monjalon > > > > Subject: Re: Diagnosing CI Failures Question > > > > Hi Tyler, > > > > On Thu, Mar 16, 2023 at 5:51 PM Tyler Retzlaff > > wrote: > > > > > > I am a little lost how I investigate failures that come from the > > > ci/intel-Functional tests. I'm still learning and about how to best > > > utilize these resources. > > > > > > Is there a way I can get access to the artifacts from the failure? I > > > notice this set of tests is most often the one that fails. > > > > > > Are the tests run here publicly available somehow? If so I would lobby > > > to onboard them to my internal lab to save time by running it prior to > > > submission. > > > > > > I'm also a bit concerned that this exact same failure is produced for > > > two entirely separate patch series, but without more detail it's hard > > > to tell if that is just a coincidence. > > > > Tyler, I am lost too... those failures started to appear overnight. > > This comes from the Intel CI. > > I have neither log or nor aware of how to reproduce this. > > Let's ask Intel people who were Cc'd on the report... > > > > > > Daxue, Huang, please, can you enlighten us on what is wrong with this series? > > For the context, see: > > http://mails.dpdk.org/archives/test-report/2023-March/371507.html > > > > > > Thanks. > > > > -- > > David Marchand >