From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <bugzilla@dpdk.org>
Received: by dpdk.org (Postfix, from userid 33)
 id 984941B136; Tue, 12 Feb 2019 18:10:58 +0100 (CET)
From: bugzilla@dpdk.org
To: ci@dpdk.org
Date: Tue, 12 Feb 2019 17:10:58 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: lab
X-Bugzilla-Component: dashboard
X-Bugzilla-Version: unspecified
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ferruh.yigit@intel.com
X-Bugzilla-Status: CONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: Normal
X-Bugzilla-Assigned-To: ci@dpdk.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform
 op_sys bug_status bug_severity priority component assigned_to reporter cc
 target_milestone
Message-ID: <bug-209-149@http.bugs.dpdk.org/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.dpdk.org/
Auto-Submitted: auto-generated
X-Auto-Response-Suppress: All
MIME-Version: 1.0
Subject: [dpdk-ci] [Bug 209] Main tree is not up to date when patch sent,
 which cause merge error
X-BeenThere: ci@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK CI discussions <ci.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/ci>,
 <mailto:ci-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/ci/>
List-Post: <mailto:ci@dpdk.org>
List-Help: <mailto:ci-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/ci>,
 <mailto:ci-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Feb 2019 17:10:58 -0000

https://bugs.dpdk.org/show_bug.cgi?id=3D209

            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

--=20
You are receiving this mail because:
You are the assignee for the bug.=