automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: pbhagavatula@caviumnetworks.com
Subject: [dpdk-test-report] |FAILURE| pw31773 [PATCH 1/4] app/eventdev: modify ethdev setup to support Tx
Date: 29 Nov 2017 23:27:50 -0800	[thread overview]
Message-ID: <a2ed28$1588ums@fmsmga002.fm.intel.com> (raw)

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

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

_apply patch file failure_

Submitter: Pavan Bhagavatula <pbhagavatula@caviumnetworks.com>
Date: Thu, 30 Nov 2017 12:54:06 +0530
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:d84aad650401a122cb75bd5811e49b03ef3dc49d
                   Repo:dpdk-next-crypto, Branch:master, CommitID:224374cc0e3ca44af5141fb7035a97f338d00c18
                   Repo:dpdk-next-net, Branch:master, CommitID:607d383d3cc56d7666584f5b1b7625e385b592c4
                   Repo:dpdk-next-virtio, Branch:master, CommitID:4f761c94b520ce71c56be1c913e54a4179b81c43
                   Repo:dpdk, Branch:master, CommitID:224374cc0e3ca44af5141fb7035a97f338d00c18
                   
Apply patch file failed:
Repo: dpdk
31773:
patching file app/test-eventdev/test_perf_common.c
Hunk #1 FAILED at 92.
Hunk #2 succeeded at 114 (offset -12 lines).
Hunk #3 FAILED at 231.
Hunk #4 FAILED at 493.
Hunk #5 FAILED at 527.
Hunk #6 FAILED at 590.
5 out of 6 hunks FAILED -- saving rejects to file app/test-eventdev/test_perf_common.c.rej
patching file app/test-eventdev/test_perf_common.h
Hunk #1 succeeded at 43 (offset -2 lines).
Hunk #2 succeeded at 73 (offset -2 lines).
Hunk #3 FAILED at 163.
1 out of 3 hunks FAILED -- saving rejects to file app/test-eventdev/test_perf_common.h.rej

Repo: dpdk-next-crypto
31773:
patching file app/test-eventdev/test_perf_common.c
Hunk #1 FAILED at 92.
Hunk #2 succeeded at 114 (offset -12 lines).
Hunk #3 FAILED at 231.
Hunk #4 FAILED at 493.
Hunk #5 FAILED at 527.
Hunk #6 FAILED at 590.
5 out of 6 hunks FAILED -- saving rejects to file app/test-eventdev/test_perf_common.c.rej
patching file app/test-eventdev/test_perf_common.h
Hunk #1 succeeded at 43 (offset -2 lines).
Hunk #2 succeeded at 73 (offset -2 lines).
Hunk #3 FAILED at 163.
1 out of 3 hunks FAILED -- saving rejects to file app/test-eventdev/test_perf_common.h.rej

Repo: dpdk-next-net
31773:
patching file app/test-eventdev/test_perf_common.c
Hunk #1 FAILED at 92.
Hunk #2 succeeded at 114 (offset -12 lines).
Hunk #3 FAILED at 231.
Hunk #4 FAILED at 493.
Hunk #5 FAILED at 527.
Hunk #6 FAILED at 590.
5 out of 6 hunks FAILED -- saving rejects to file app/test-eventdev/test_perf_common.c.rej
patching file app/test-eventdev/test_perf_common.h
Hunk #1 succeeded at 43 (offset -2 lines).
Hunk #2 succeeded at 73 (offset -2 lines).
Hunk #3 FAILED at 163.
1 out of 3 hunks FAILED -- saving rejects to file app/test-eventdev/test_perf_common.h.rej

Repo: dpdk-next-virtio
31773:
patching file app/test-eventdev/test_perf_common.c
Hunk #1 FAILED at 92.
Hunk #3 FAILED at 231.
Hunk #4 FAILED at 493.
Hunk #5 FAILED at 527.
Hunk #6 FAILED at 590.
5 out of 6 hunks FAILED -- saving rejects to file app/test-eventdev/test_perf_common.c.rej
patching file app/test-eventdev/test_perf_common.h
Hunk #1 succeeded at 43 (offset -2 lines).
Hunk #2 succeeded at 73 (offset -2 lines).
Hunk #3 FAILED at 163.
1 out of 3 hunks FAILED -- saving rejects to file app/test-eventdev/test_perf_common.h.rej

Repo: dpdk-next-eventdev
31773:
patching file app/test-eventdev/test_perf_common.c
Hunk #1 FAILED at 92.
Hunk #2 succeeded at 114 (offset -12 lines).
Hunk #3 FAILED at 231.
Hunk #4 FAILED at 493.
Hunk #5 FAILED at 527.
Hunk #6 FAILED at 590.
5 out of 6 hunks FAILED -- saving rejects to file app/test-eventdev/test_perf_common.c.rej
patching file app/test-eventdev/test_perf_common.h
Hunk #1 succeeded at 43 (offset -2 lines).
Hunk #2 succeeded at 73 (offset -2 lines).
Hunk #3 FAILED at 163.
1 out of 3 hunks FAILED -- saving rejects to file app/test-eventdev/test_perf_common.h.rej


DPDK STV team

                 reply	other threads:[~2017-11-30  7:27 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='a2ed28$1588ums@fmsmga002.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).