From: bugzilla@dpdk.org
To: ci@dpdk.org
Subject: [dpdk-ci] [Bug 231] when a sub-tree used as base, two different commit id displayed in logs
Date: Tue, 26 Mar 2019 15:32:10 +0000 [thread overview]
Message-ID: <bug-231-149@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=231
Bug ID: 231
Summary: when a sub-tree used as base, two different commit id
displayed in logs
Product: lab
Version: unspecified
Hardware: All
OS: All
Status: CONFIRMED
Severity: normal
Priority: Normal
Component: job scripts
Assignee: ci@dpdk.org
Reporter: ferruh.yigit@intel.com
CC: jplsek@iol.unh.edu
Target Milestone: ---
For example, for: https://lab.dpdk.org/results/dashboard/tarballs/3908/
In header it has:
Tarball Info
dpdk-next-net (ad2f55539b3e266326f9d7627e3afc3230d9d267)
But in test result it has:
Baseline
dpdk (1534cc6ab1d93041dcbb0bb6c7f1e111578dffd4)
Two different tree and commit ids, can you please check this?
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2019-03-26 15:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly 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 \
--in-reply-to=bug-231-149@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=ci@dpdk.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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).