automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: erik.g.carrillo@intel.com
Subject: [dpdk-test-report] |FAILURE| pw36982 [PATCH v10 1/9] eventtimer: introduce event timer adapter
Date: 11 Apr 2018 03:11:21 -0700	[thread overview]
Message-ID: <0590c7$1cp8v8@orsmga001.jf.intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1382 bytes --]

Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/36982

_apply patch file failure_

Submitter: Erik Carrillo <erik.g.carrillo@intel.com>
Date: Tue,  3 Apr 2018 16:44:23 -0500
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:8cafb78bb4d7a724c41aefc326d9eae79c6fb6e7
                   Repo:dpdk-next-crypto, Branch:master, CommitID:28adae99e7b19063b6f18b6f0371495fc9bd59bc
                   Repo:dpdk-next-net, Branch:master, CommitID:03315a784aeb337e55f5859b3624cfb006ae0cc6
                   Repo:dpdk-next-virtio, Branch:master, CommitID:6c7026928154594b62348b7c56ed36317b19812e
                   Repo:dpdk, Branch:master, CommitID:bef5a2d629d536a82c81c02b84684da828c0e37f
                   
Apply patch file failed:
Repo: dpdk-next-eventdev
36982:
patching file lib/librte_eventdev/Makefile
Hunk #1 FAILED at 28.
1 out of 1 hunk FAILED -- saving rejects to file lib/librte_eventdev/Makefile.rej
The next patch would create the file lib/librte_eventdev/rte_event_timer_adapter.h,
which already exists!  Assume -R? [n] 
Apply anyway? [n] 
Skipping patch.
1 out of 1 hunk ignored
patching file lib/librte_eventdev/rte_eventdev.h
Reversed (or previously applied) patch detected!  Assume -R? [n] 
Apply anyway? [n] 
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file lib/librte_eventdev/rte_eventdev.h.rej


DPDK STV team

                 reply	other threads:[~2018-04-11 10:11 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly 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='0590c7$1cp8v8@orsmga001.jf.intel.com' \
    --to=sys_stv@intel.com \
    --cc=erik.g.carrillo@intel.com \
    --cc=test-report@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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).