From: firstname.lastname@example.org To: email@example.com Subject: [dpdk-ci] [Bug 195] "Applied on" commit id and "baseline" commit id issues Date: Mon, 28 Jan 2019 19:40:24 +0000 Message-ID: <firstname.lastname@example.org/> (raw) 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: email@example.com Reporter: firstname.lastname@example.org CC: email@example.com 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.
next reply index Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-01-28 19:40 bugzilla [this message] 2019-02-05 18:00 ` bugzilla
Reply instructions: You may reply publically to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --firstname.lastname@example.org/ \ --email@example.com \ --firstname.lastname@example.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
DPDK CI discussions Archives are clonable: git clone --mirror http://inbox.dpdk.org/ci/0 ci/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 ci ci/ http://inbox.dpdk.org/ci \ email@example.com public-inbox-index ci Newsgroup available over NNTP: nntp://inbox.dpdk.org/inbox.dpdk.ci AGPL code for this site: git clone https://public-inbox.org/ public-inbox