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| pw32086 [PATCH v3 7/8] app/eventdev: add service core configuration
Date: 11 Dec 2017 08:46:40 -0800	[thread overview]
Message-ID: <1f4ae4$ggvas@orsmga002.jf.intel.com> (raw)

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

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

_apply patch file failure_

Submitter: Pavan Bhagavatula <pbhagavatula@caviumnetworks.com>
Date: Mon, 11 Dec 2017 20:43:42 +0530
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:5b5e476e59a45aababa019f76d57d21b978400dc
                   Repo:dpdk-next-crypto, Branch:master, CommitID:cdc9b6b37ed6417b46165c341e6e03518837084d
                   Repo:dpdk-next-net, Branch:master, CommitID:efca9d9498ec183658e9ec78ff470663cdc6182e
                   Repo:dpdk-next-virtio, Branch:master, CommitID:4f761c94b520ce71c56be1c913e54a4179b81c43
                   Repo:dpdk, Branch:master, CommitID:224374cc0e3ca44af5141fb7035a97f338d00c18
                   
Apply patch file failed:
Repo: dpdk-next-virtio
32086:
patching file app/test-eventdev/evt_common.h
Hunk #1 FAILED at 94.
1 out of 1 hunk FAILED -- saving rejects to file app/test-eventdev/evt_common.h.rej
patching file app/test-eventdev/test_perf_atq.c
Hunk #1 FAILED at 239.
1 out of 1 hunk FAILED -- saving rejects to file app/test-eventdev/test_perf_atq.c.rej
patching file app/test-eventdev/test_perf_common.c
Hunk #1 succeeded at 274 (offset 7 lines).
patching file app/test-eventdev/test_perf_queue.c
Hunk #1 FAILED at 252.
1 out of 1 hunk FAILED -- saving rejects to file app/test-eventdev/test_perf_queue.c.rej


DPDK STV team

                 reply	other threads:[~2017-12-11 16:46 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='1f4ae4$ggvas@orsmga002.jf.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).