DPDK CI discussions
 help / color / Atom feed
* [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)
  To: ci

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.

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, back to index

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

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 \
		ci@dpdk.org
	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