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 918DAA00C2 for ; Wed, 22 Apr 2020 18:34:17 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 7D4E91C2F8; Wed, 22 Apr 2020 18:34:17 +0200 (CEST) Received: from inbox.dpdk.org (xvm-172-178.dc0.ghst.net [95.142.172.178]) by dpdk.org (Postfix) with ESMTP id 05EF61C2F0 for ; Wed, 22 Apr 2020 18:34:16 +0200 (CEST) Received: by inbox.dpdk.org (Postfix, from userid 33) id DB9FCA00C2; Wed, 22 Apr 2020 18:34:16 +0200 (CEST) From: bugzilla@dpdk.org To: ci@dpdk.org Date: Wed, 22 Apr 2020 16:34:16 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: lab X-Bugzilla-Component: job scripts X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: blo@iol.unh.edu X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: High X-Bugzilla-Assigned-To: ci@dpdk.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: resolution bug_status Message-ID: In-Reply-To: References: 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 431] Missing performance results in Patchwork checks, and possible false positives 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=3D431 Brandon Lo (blo@iol.unh.edu) changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|IN_PROGRESS |RESOLVED --- Comment #5 from Brandon Lo (blo@iol.unh.edu) --- Fixed. This issue is due to concurrent running tests. Our internal testing job would run a job to send a performance report email= to vendors for a given patch. The problem is that this email would be sent aft= er all of a given vendor's machines are done testing (vendor A), but it could occur before all of the machines of another vendor finishes (vendor B).=20 This results in all of the results from the first vendor (A) being sent, but the internal script will pick up the existing results created by the unfini= shed vendor B and send those out as well. This can be seen with email timings. An unfinished Mellanox report email co= uld have one single testbed's result in the email, and it will always be sent at the same time as another vendor's email (Intel for example).=20 The fix was to add support for sending a specific vendor's email only when = all of the given vendor's testbeds are finished testing.=20 We have tested this by using dry runs of the email sending script with successful separation of vendor testbed results. --=20 You are receiving this mail because: You are the assignee for the bug.=