From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id F3CCEA051C for ; Fri, 26 Jun 2020 15:37:35 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id CAFF01BF60; Fri, 26 Jun 2020 15:37:35 +0200 (CEST) Received: from inbox.dpdk.org (xvm-172-178.dc0.ghst.net [95.142.172.178]) by dpdk.org (Postfix) with ESMTP id 19EF61B951 for ; Fri, 26 Jun 2020 15:37:35 +0200 (CEST) Received: by inbox.dpdk.org (Postfix, from userid 33) id E2268A051D; Fri, 26 Jun 2020 15:37:34 +0200 (CEST) From: bugzilla@dpdk.org To: ci@dpdk.org Date: Fri, 26 Jun 2020 13:37:34 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: lab X-Bugzilla-Component: job scripts X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: lylavoie@iol.unh.edu X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: ci@dpdk.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter cc target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All MIME-Version: 1.0 Subject: [dpdk-ci] [Bug 493] Failures reported by Intel CI for series 10551 X-BeenThere: ci@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK CI discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ci-bounces@dpdk.org Sender: "ci" https://bugs.dpdk.org/show_bug.cgi?id=3D493 Bug ID: 493 Summary: Failures reported by Intel CI for series 10551 Product: lab Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: Normal Component: job scripts Assignee: ci@dpdk.org Reporter: lylavoie@iol.unh.edu CC: dpdklab@iol.unh.edu Target Milestone: --- Actively being worked on the ci@dpdk.org email list, creating a bug here for tracking... #################################################################### #################################################################### >From Zhaoyan Chen Hi, David, For your question, "Is it normal to see all patches with the exact same test report?" Yes, we always test a series, rather than a single patch. You can see the e= xact same report on any patch in a series. (it's convenient, you don't need backward to sear= ch the header of the series, then check result) " One thing that comes to mind, do we have dpdk headers installed system- > wide on the Intel CI server(s)?" Sure, we do. We don't see any problem on other patch compilation, so far. b= ut it's strange that your V2 and V3 is same, but v3 test is failed. (code base is same). So= I will try to re-run your series(v3), and check what's changed on CI system between the 2 days. = Is that helpful? Regards, Zhaoyan Chen #################################################################### #################################################################### >From David Marchand > Hi, David, > > For your question, "Is it normal to see all patches with the exact same t= est > report?" > Yes, we always test a series, rather than a single patch. You can see the > exact same report > on any patch in a series. (it's convenient, you don't need backward to se= arch > the header of the series, then check result) Convenience is subject to interpretation :-). Other CI systems send a single report which is more sane for me. > > " One thing that comes to mind, do we have dpdk headers installed system- > > wide on the Intel CI server(s)?" > > Sure, we do. We don't see any problem on other patch compilation, so far.= but > it's strange > that your V2 and V3 is same, but v3 test is failed. (code base is same). = So I > will try to re-run > your series(v3), and check what's changed on CI system between the 2 days= . Is > that helpful? Just to be sure. By this, you mean that you have some dpdk headers installed on the CI system in /usr? Having those headers most likely exacerbates races with dpdk headers copy in the building directory. This could be where my series failed. #################################################################### #################################################################### >From Thomas Monjalon > On Fri, Jun 26, 2020 at 5:03 AM Chen, Zhaoyan wr= ote: > > > > Hi, David, > > > > For your question, "Is it normal to see all patches with the exact same > test report?" > > Yes, we always test a series, rather than a single patch. You can see t= he > exact same report > > on any patch in a series. (it's convenient, you don't need backward to > search > > the header of the series, then check result) > > Convenience is subject to interpretation :-). > Other CI systems send a single report which is more sane for me. I think these tests have 2 purposes: - sending quick error feedback to the author - check that all is green before merging In both cases we don't need to have the same report duplicated, because we check for failures in all patches anyway. I suggest sending the series report only on the last patch of the series. --=20 You are receiving this mail because: You are the assignee for the bug.=