From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: kamilx.chalupnik@intel.com
Subject: [dpdk-test-report] |FAILURE| pw37127 [PATCH] app/bbdev: remove improper WARNING printouts
Date: 12 Apr 2018 09:28:19 -0700 [thread overview]
Message-ID: <ca5293$1c8b61@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3287 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/37127
_apply patch file failure_
Submitter: KamilX Chalupnik <kamilx.chalupnik@intel.com>
Date: Wed, 4 Apr 2018 16:06:00 +0200
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:419cb5e1e61f9ef3e2a84154f1f837c777512efa
Repo:dpdk-next-crypto, Branch:master, CommitID:38193ec5c89ecb0f3fd5b25acd06a855ba7537c9
Repo:dpdk-next-net, Branch:master, CommitID:9206fe199d2fc11e5a209774eb2c1ac0109141de
Repo:dpdk-next-virtio, Branch:master, CommitID:c8c60f75abfc331b9e018c6ae6f06c7cdd9bc7b4
Repo:dpdk, Branch:master, CommitID:34fbfa585cbfa5e3e1de5b0137e91ecfdc87e4f9
Apply patch file failed:
Repo: dpdk
37127:
patching file app/test-bbdev/test_bbdev_perf.c
Hunk #1 succeeded at 138 (offset -23 lines).
Hunk #2 FAILED at 1166.
1 out of 2 hunks FAILED -- saving rejects to file app/test-bbdev/test_bbdev_perf.c.rej
patching file app/test-bbdev/test_bbdev_vector.c
Hunk #1 succeeded at 642 (offset -2 lines).
Hunk #2 succeeded at 661 (offset -2 lines).
Hunk #3 succeeded at 722 (offset -2 lines).
Hunk #4 succeeded at 742 (offset -2 lines).
Hunk #5 succeeded at 827 (offset -2 lines).
Repo: dpdk-next-crypto
37127:
patching file app/test-bbdev/test_bbdev_perf.c
Hunk #1 succeeded at 138 (offset -23 lines).
Hunk #2 FAILED at 1166.
1 out of 2 hunks FAILED -- saving rejects to file app/test-bbdev/test_bbdev_perf.c.rej
patching file app/test-bbdev/test_bbdev_vector.c
Hunk #1 succeeded at 642 (offset -2 lines).
Hunk #2 succeeded at 661 (offset -2 lines).
Hunk #3 succeeded at 722 (offset -2 lines).
Hunk #4 succeeded at 742 (offset -2 lines).
Hunk #5 succeeded at 827 (offset -2 lines).
Repo: dpdk-next-net
37127:
patching file app/test-bbdev/test_bbdev_perf.c
Hunk #1 succeeded at 138 (offset -23 lines).
Hunk #2 FAILED at 1166.
1 out of 2 hunks FAILED -- saving rejects to file app/test-bbdev/test_bbdev_perf.c.rej
patching file app/test-bbdev/test_bbdev_vector.c
Hunk #1 succeeded at 642 (offset -2 lines).
Hunk #2 succeeded at 661 (offset -2 lines).
Hunk #3 succeeded at 722 (offset -2 lines).
Hunk #4 succeeded at 742 (offset -2 lines).
Hunk #5 succeeded at 827 (offset -2 lines).
Repo: dpdk-next-virtio
37127:
patching file app/test-bbdev/test_bbdev_perf.c
Hunk #1 succeeded at 138 (offset -23 lines).
Hunk #2 FAILED at 1166.
1 out of 2 hunks FAILED -- saving rejects to file app/test-bbdev/test_bbdev_perf.c.rej
patching file app/test-bbdev/test_bbdev_vector.c
Hunk #1 succeeded at 642 (offset -2 lines).
Hunk #2 succeeded at 661 (offset -2 lines).
Hunk #3 succeeded at 722 (offset -2 lines).
Hunk #4 succeeded at 742 (offset -2 lines).
Hunk #5 succeeded at 827 (offset -2 lines).
Repo: dpdk-next-eventdev
37127:
patching file app/test-bbdev/test_bbdev_perf.c
Hunk #1 succeeded at 138 (offset -23 lines).
Hunk #2 FAILED at 1166.
1 out of 2 hunks FAILED -- saving rejects to file app/test-bbdev/test_bbdev_perf.c.rej
patching file app/test-bbdev/test_bbdev_vector.c
Hunk #1 succeeded at 642 (offset -2 lines).
Hunk #2 succeeded at 661 (offset -2 lines).
Hunk #3 succeeded at 722 (offset -2 lines).
Hunk #4 succeeded at 742 (offset -2 lines).
Hunk #5 succeeded at 827 (offset -2 lines).
DPDK STV team
reply other threads:[~2018-04-12 16:28 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='ca5293$1c8b61@fmsmga001.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=kamilx.chalupnik@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).