automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: pablo.de.lara.guarch@intel.com
Subject: [dpdk-test-report] |FAILURE| pw25586 [PATCH 09/22] app/crypto-perf: move IV to crypto op private data
Date: 23 Jun 2017 08:15:58 -0700	[thread overview]
Message-ID: <63cbe6$13b8hpe@fmsmga002.fm.intel.com> (raw)

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

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

_apply patch file failure_

Submitter: Pablo de Lara <pablo.de.lara.guarch@intel.com>
Date: Wed, 21 Jun 2017 08:47:18 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:c687cebe095b2ea325aa012e2834b830f1f74eba
                   Repo:dpdk-next-crypto, Branch:master, CommitID:059751bf14a4bfb782c0d226e1c278d1bb082d69
                   Repo:dpdk-next-net, Branch:master, CommitID:efe576f0d5cc4cd93317c7833f387cb64d2abcf1
                   Repo:dpdk-next-virtio, Branch:master, CommitID:da5129d9b6b53375667690970f6824565c1f1443
                   Repo:dpdk, Branch:master, CommitID:8a04cb6125896e9ea25a4d15a316f0d873822c7b
                   
Apply patch file failed:
Repo: dpdk
25586:
patching file app/test-crypto-perf/cperf_ops.c
patching file app/test-crypto-perf/cperf_ops.h
patching file app/test-crypto-perf/cperf_test_latency.c
Hunk #1 FAILED at 68.
Hunk #2 FAILED at 280.
Hunk #3 succeeded at 339 (offset -5 lines).
Hunk #4 succeeded at 371 (offset -5 lines).
2 out of 4 hunks FAILED -- saving rejects to file app/test-crypto-perf/cperf_test_latency.c.rej
patching file app/test-crypto-perf/cperf_test_throughput.c
patching file app/test-crypto-perf/cperf_test_vector_parsing.c
patching file app/test-crypto-perf/cperf_test_vectors.c
patching file app/test-crypto-perf/cperf_test_verify.c

Repo: dpdk-next-crypto
25586:
patching file app/test-crypto-perf/cperf_ops.c
patching file app/test-crypto-perf/cperf_ops.h
patching file app/test-crypto-perf/cperf_test_latency.c
Hunk #1 FAILED at 68.
Hunk #2 FAILED at 280.
Hunk #3 succeeded at 339 (offset -5 lines).
Hunk #4 succeeded at 371 (offset -5 lines).
2 out of 4 hunks FAILED -- saving rejects to file app/test-crypto-perf/cperf_test_latency.c.rej
patching file app/test-crypto-perf/cperf_test_throughput.c
patching file app/test-crypto-perf/cperf_test_vector_parsing.c
patching file app/test-crypto-perf/cperf_test_vectors.c
patching file app/test-crypto-perf/cperf_test_verify.c

Repo: dpdk-next-net
25586:
patching file app/test-crypto-perf/cperf_ops.c
patching file app/test-crypto-perf/cperf_ops.h
patching file app/test-crypto-perf/cperf_test_latency.c
Hunk #1 FAILED at 68.
Hunk #2 FAILED at 280.
Hunk #3 succeeded at 339 (offset -5 lines).
Hunk #4 succeeded at 371 (offset -5 lines).
2 out of 4 hunks FAILED -- saving rejects to file app/test-crypto-perf/cperf_test_latency.c.rej
patching file app/test-crypto-perf/cperf_test_throughput.c
patching file app/test-crypto-perf/cperf_test_vector_parsing.c
patching file app/test-crypto-perf/cperf_test_vectors.c
patching file app/test-crypto-perf/cperf_test_verify.c

Repo: dpdk-next-virtio
25586:
patching file app/test-crypto-perf/cperf_ops.c
patching file app/test-crypto-perf/cperf_ops.h
patching file app/test-crypto-perf/cperf_test_latency.c
Hunk #1 FAILED at 68.
Hunk #2 FAILED at 280.
Hunk #3 succeeded at 339 (offset -5 lines).
Hunk #4 succeeded at 371 (offset -5 lines).
2 out of 4 hunks FAILED -- saving rejects to file app/test-crypto-perf/cperf_test_latency.c.rej
patching file app/test-crypto-perf/cperf_test_throughput.c
patching file app/test-crypto-perf/cperf_test_vector_parsing.c
patching file app/test-crypto-perf/cperf_test_vectors.c
patching file app/test-crypto-perf/cperf_test_verify.c

Repo: dpdk-next-eventdev
25586:
patching file app/test-crypto-perf/cperf_ops.c
patching file app/test-crypto-perf/cperf_ops.h
patching file app/test-crypto-perf/cperf_test_latency.c
Hunk #1 FAILED at 68.
Hunk #2 FAILED at 280.
Hunk #3 succeeded at 339 (offset -5 lines).
Hunk #4 succeeded at 371 (offset -5 lines).
2 out of 4 hunks FAILED -- saving rejects to file app/test-crypto-perf/cperf_test_latency.c.rej
patching file app/test-crypto-perf/cperf_test_throughput.c
patching file app/test-crypto-perf/cperf_test_vector_parsing.c
patching file app/test-crypto-perf/cperf_test_vectors.c
patching file app/test-crypto-perf/cperf_test_verify.c


DPDK STV team

             reply	other threads:[~2017-06-23 15:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-23 15:15 sys_stv [this message]
2017-06-30  4:26 sys_stv

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='63cbe6$13b8hpe@fmsmga002.fm.intel.com' \
    --to=sys_stv@intel.com \
    --cc=pablo.de.lara.guarch@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).