From: bugzilla@dpdk.org
To: ci@dpdk.org
Subject: [dpdk-ci] [Bug 209] Main tree is not up to date when patch sent, which cause merge error
Date: Tue, 12 Feb 2019 17:10:58 +0000 [thread overview]
Message-ID: <bug-209-149@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=209
Bug ID: 209
Summary: Main tree is not up to date when patch sent, which
cause merge error
Product: lab
Version: unspecified
Hardware: All
OS: All
Status: CONFIRMED
Severity: normal
Priority: Normal
Component: dashboard
Assignee: ci@dpdk.org
Reporter: ferruh.yigit@intel.com
CC: jplsek@iol.unh.edu
Target Milestone: ---
In the task "https://lab.dpdk.org/results/dashboard/patchsets/4534/"
the patch submitted same day repo updated, and patches are based on updated
repo but it seems failed to apply.
Are we updating the repo before testing each patch? If not should we?
Or how can be prevented above error with a completely valid patch?
Thanks,
ferruh
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2019-02-12 17:10 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-209-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).