From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by dpdk.org (Postfix, from userid 33) id 3EEBBD0B2; Mon, 28 Jan 2019 20:40:24 +0100 (CET) From: bugzilla@dpdk.org To: ci@dpdk.org Date: Mon, 28 Jan 2019 19:40:24 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: lab X-Bugzilla-Component: dashboard X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jplsek@iol.unh.edu X-Bugzilla-Status: CONFIRMED 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 195] "Applied on" commit id and "baseline" commit id issues 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: , X-List-Received-Date: Mon, 28 Jan 2019 19:40:24 -0000 https://bugs.dpdk.org/show_bug.cgi?id=3D195 Bug ID: 195 Summary: "Applied on" commit id and "baseline" commit id issues Product: lab Version: unspecified Hardware: All OS: All Status: CONFIRMED Severity: normal Priority: Normal Component: dashboard Assignee: ci@dpdk.org Reporter: jplsek@iol.unh.edu CC: jplsek@iol.unh.edu Target Milestone: --- Patches get applied on the baseline. This is shown on the dashboard for each patchset. The "baseline" represents both the commit id the patch was applied on and t= he commit id of the baseline used. However, since introducing retesting of patchsets, there is a possibility t= hat the baseline has changed (since these are not saved), thus the results being different than what the "baseline" on the dashboard actually means. Essentially to fix the confusion: Rename "baseline" to "applied on" (since this information is saved when generating the tarball), similar to when an apply error or build error occu= rs. Add a "baseline" commit id to each individual test run (instead of represen= ting the whole patchset). This may be a more noticeable issue once subtree testing comes into play. --=20 You are receiving this mail because: You are the assignee for the bug.=