* [dpdk-ci] [Bug 209] Main tree is not up to date when patch sent, which cause merge error
@ 2019-02-12 17:10 bugzilla
0 siblings, 0 replies; only message in thread
From: bugzilla @ 2019-02-12 17:10 UTC (permalink / raw)
Bug ID: 209
Summary: Main tree is not up to date when patch sent, which
cause merge error
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?
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2019-02-12 17:10 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-02-12 17:10 [dpdk-ci] [Bug 209] Main tree is not up to date when patch sent, which cause merge error bugzilla
DPDK CI discussions
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://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/ https://inbox.dpdk.org/ci \
Example config snippet for mirrors.
Newsgroup available over NNTP:
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git