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 32AFC41EB1 for ; Thu, 16 Mar 2023 18:00:01 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 2D87740DF6; Thu, 16 Mar 2023 18:00:01 +0100 (CET) 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 99EA640DDC for ; Thu, 16 Mar 2023 17:59:59 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1678985999; 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=DRu662RBzVo41e5SadA1nzPBA9qw1DlruFdqfqVBN+k=; b=QNXpYjbtkO0DXW04uqKqukxas8cGHfC5SPSUdJuvAc9Hdfcib824L1qAoYjCqk21fXu5KA EN+Mkc3m7eRgQHx/2g9N92TpniZ/e5AcdE57gzTa9UGJLZePd7iJj/A+OhUotflQVsJw+d 7+e76mz7U5mdcKNJdg+gnuo0HeWzwZw= Received: from mail-pl1-f199.google.com (mail-pl1-f199.google.com [209.85.214.199]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-669-QzMCK0s4P7GdT8gcMznZgQ-1; Thu, 16 Mar 2023 12:59:57 -0400 X-MC-Unique: QzMCK0s4P7GdT8gcMznZgQ-1 Received: by mail-pl1-f199.google.com with SMTP id z9-20020a170902708900b0019f271f33aeso1283939plk.9 for ; Thu, 16 Mar 2023 09:59:56 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1678985996; 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=DRu662RBzVo41e5SadA1nzPBA9qw1DlruFdqfqVBN+k=; b=cEUUzzQPJd0l/1pvTyvUc+MFij8StUo3buFGc9kMu5cPf1730T4Phm+2CSv/wBRy9t vKdlRHaO+6A+AIf6gD48850fGIWT4FdlUfO0ETB4aEgWAIGTWbGvEB7bfqn9Un5VCK/2 SA3e5ilr/skb2ZFZ5gZippkLSDM8S+R46c9MAb3Wk+TDsqeC1sJCLot4/BpGJxUdnoTV G6db45vEt7bL4f8To9EOLVCaOCZeQNkzNLB36zG9lyMhwRxGSDoVFpnbKWpEAchsF9zx vMJPIECwEtjroKCrFznQih8mv+4k8Ne9nl0yz+D2fv+lVeyCI5moIoUI18DGLgiqlBeT RQrg== X-Gm-Message-State: AO0yUKUFMFzIcpa9k2Cqg39jwggQ2X4wABW/n/Mz7iAvVqvl7WVowl7e v9MWfeyQEx1R9HR+3UaV3M/mcfSVTStDdvd+9sKqV7phy3vkeGnRtMU0ekBNB3YgC1mlFxmOTE+ o+urDtb7wL4HC77aGZw== X-Received: by 2002:a17:90a:ca08:b0:23b:349d:a159 with SMTP id x8-20020a17090aca0800b0023b349da159mr21405pjt.3.1678985995782; Thu, 16 Mar 2023 09:59:55 -0700 (PDT) X-Google-Smtp-Source: AK7set/63XVIK4PILyYdEyhPrVP152nHMW2CeQtCLNteJaGiwKHjFEYCD345Cex/kT3QnUDwN0cLEJyRjSNh0MVft7E= X-Received: by 2002:a17:90a:ca08:b0:23b:349d:a159 with SMTP id x8-20020a17090aca0800b0023b349da159mr21393pjt.3.1678985995469; Thu, 16 Mar 2023 09:59:55 -0700 (PDT) MIME-Version: 1.0 References: <20230316165126.GB8277@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net> In-Reply-To: <20230316165126.GB8277@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net> From: David Marchand Date: Thu, 16 Mar 2023 17:59:44 +0100 Message-ID: Subject: Re: Diagnosing CI Failures Question To: Tyler Retzlaff , "Gao, DaxueX" , "Huang, ChenyuX" Cc: ci@dpdk.org, Aaron Conole , Thomas Monjalon 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 Hi Tyler, On Thu, Mar 16, 2023 at 5:51=E2=80=AFPM 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 serie= s? For the context, see: http://mails.dpdk.org/archives/test-report/2023-March/371507.html Thanks. --=20 David Marchand