* [dpdk-ci] [Bug 195] "Applied on" commit id and "baseline" commit id issues
@ 2019-01-28 19:40 bugzilla
2019-02-05 18:00 ` bugzilla
0 siblings, 1 reply; 2+ messages in thread
From: bugzilla @ 2019-01-28 19:40 UTC (permalink / raw)
To: ci
https://bugs.dpdk.org/show_bug.cgi?id=195
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 the
commit id of the baseline used.
However, since introducing retesting of patchsets, there is a possibility that
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 occurs.
Add a "baseline" commit id to each individual test run (instead of representing
the whole patchset).
This may be a more noticeable issue once subtree testing comes into play.
--
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2019-02-05 18:00 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-01-28 19:40 [dpdk-ci] [Bug 195] "Applied on" commit id and "baseline" commit id issues bugzilla
2019-02-05 18:00 ` bugzilla
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).