[dpdk-ci] [Bug 223] Using wrong/old commit id of the tree to apply the patch

[dpdk-ci] [Bug 223] Using wrong/old commit id of the tree to apply the patch

[bugzilla]

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.

[dpdk-ci] [Bug 223] Using wrong/old commit id of the tree to apply the patch

[bugzilla]

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

Jeremy Plsek (jplsek@iol.unh.edu) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|CONFIRMED                   |RESOLVED

--- Comment #2 from Jeremy Plsek (jplsek@iol.unh.edu) ---
Closing since this should have been resolved.

This is partially a separate issue, but some environments don't show commit
IDs, and that's because Jenkins sometimes runs the jobs in different workspaces
(Foo-Bar and Foo-Bar@2). Not sure how to resolve that. If this is important or
brought up again, a new ticket can be made.

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