From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: pbhagavatula@caviumnetworks.com
Subject: [dpdk-test-report] |FAILURE| pw33575 [PATCH v5 05/11] event/octeontx: update octeontx eventdev selftest ops
Date: 17 Jan 2018 16:13:05 -0800 [thread overview]
Message-ID: <a797f1$m5et7@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3560 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/33575
_apply patch file failure_
Submitter: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
Date: Thu, 11 Jan 2018 15:51:56 +0530
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:9f723abd4c9366625e7392f1e66234e9e120dea5
Repo:dpdk-next-crypto, Branch:master, CommitID:eb228b9064587fb979abf1ee2ebc6f735019c88f
Repo:dpdk-next-net, Branch:master, CommitID:b5660f95e192b8b51a010aa3ca354aadaf85a966
Repo:dpdk-next-virtio, Branch:master, CommitID:9158926a0f24e9b8cccfe97211fa72d52a6f6a36
Repo:dpdk, Branch:master, CommitID:c281b4fc71ddefe809994be10f53b87e1ba6c669
Apply patch file failed:
Repo: dpdk
33575:
patching file drivers/event/octeontx/Makefile
Hunk #1 FAILED at 42.
Hunk #2 succeeded at 26 (offset -28 lines).
1 out of 2 hunks FAILED -- saving rejects to file drivers/event/octeontx/Makefile.rej
patching file drivers/event/octeontx/ssovf_evdev.c
Hunk #1 succeeded at 595 (offset -18 lines).
patching file drivers/event/octeontx/ssovf_evdev.h
Hunk #1 FAILED at 57.
Hunk #2 succeeded at 163 (offset -33 lines).
1 out of 2 hunks FAILED -- saving rejects to file drivers/event/octeontx/ssovf_evdev.h.rej
Repo: dpdk-next-crypto
33575:
patching file drivers/event/octeontx/Makefile
Hunk #1 FAILED at 42.
Hunk #2 succeeded at 26 (offset -28 lines).
1 out of 2 hunks FAILED -- saving rejects to file drivers/event/octeontx/Makefile.rej
patching file drivers/event/octeontx/ssovf_evdev.c
Hunk #1 succeeded at 595 (offset -18 lines).
patching file drivers/event/octeontx/ssovf_evdev.h
Hunk #1 FAILED at 57.
Hunk #2 succeeded at 163 (offset -33 lines).
1 out of 2 hunks FAILED -- saving rejects to file drivers/event/octeontx/ssovf_evdev.h.rej
Repo: dpdk-next-net
33575:
patching file drivers/event/octeontx/Makefile
Hunk #1 FAILED at 42.
Hunk #2 succeeded at 26 (offset -28 lines).
1 out of 2 hunks FAILED -- saving rejects to file drivers/event/octeontx/Makefile.rej
patching file drivers/event/octeontx/ssovf_evdev.c
Hunk #1 succeeded at 595 (offset -18 lines).
patching file drivers/event/octeontx/ssovf_evdev.h
Hunk #1 FAILED at 57.
Hunk #2 succeeded at 163 (offset -33 lines).
1 out of 2 hunks FAILED -- saving rejects to file drivers/event/octeontx/ssovf_evdev.h.rej
Repo: dpdk-next-virtio
33575:
patching file drivers/event/octeontx/Makefile
Hunk #1 FAILED at 42.
1 out of 2 hunks FAILED -- saving rejects to file drivers/event/octeontx/Makefile.rej
patching file drivers/event/octeontx/ssovf_evdev.c
Hunk #1 succeeded at 623 (offset 10 lines).
patching file drivers/event/octeontx/ssovf_evdev.h
Hunk #1 FAILED at 57.
Hunk #2 succeeded at 191 (offset -5 lines).
1 out of 2 hunks FAILED -- saving rejects to file drivers/event/octeontx/ssovf_evdev.h.rej
Repo: dpdk-next-eventdev
33575:
patching file drivers/event/octeontx/Makefile
Hunk #1 FAILED at 42.
Hunk #2 FAILED at 54.
2 out of 2 hunks FAILED -- saving rejects to file drivers/event/octeontx/Makefile.rej
patching file drivers/event/octeontx/ssovf_evdev.c
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file drivers/event/octeontx/ssovf_evdev.c.rej
patching file drivers/event/octeontx/ssovf_evdev.h
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
2 out of 2 hunks ignored -- saving rejects to file drivers/event/octeontx/ssovf_evdev.h.rej
DPDK STV team
reply other threads:[~2018-01-18 0:13 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='a797f1$m5et7@fmsmga001.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=pbhagavatula@caviumnetworks.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).