DPDK CI discussions
 help / color / Atom feed
From: bugzilla@dpdk.org
To: ci@dpdk.org
Subject: [dpdk-ci] [Bug 223] Using wrong/old commit id of the tree to apply the patch
Date: Tue, 12 Mar 2019 15:01:04 +0000
Message-ID: <bug-223-149@http.bugs.dpdk.org/> (raw)

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

            Bug ID: 223
           Summary: Using wrong/old commit id of the tree to apply the
                    patch
           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: ---

1)
https://lab.dpdk.org/results/dashboard/patchsets/4835/

Patch has been sent on March 11, 2019
maintainers: claim responsibility for timer lib
https://patches.dpdk.org/patch/51083/

Applied on
dpdk (0b8572a0c101778d259b822bc39008d8298df4dc)

https://git.dpdk.org/dpdk/commit/?id=0b8572a0c101778d259b822bc39008d8298df4dc
committer       Ferruh Yigit <ferruh.yigit@intel.com>   2019-02-08 19:27:07
+0100

This tree is old, it is from 8 February, but the patch is from March 11

btw, I am not clear why applying this patch failed.


2)
There was another I found, which I can't find now, interestingly.
It was a patch after test folder moved, but again it was trying to apply into
an old tree before folder moved and giving the apply error.

This defect is to confirm the tree used to apply is up-to-date alway.

Thanks,

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

             reply index

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-12 15:01 bugzilla [this message]
2019-11-19 17:07 ` bugzilla

Reply instructions:

You may reply publically 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-223-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

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