automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: gaetan.rivet@6wind.com
Subject: [dpdk-test-report] |FAILURE| pw23997 [PATCH] app/testpmd: configure event display
Date: 28 Apr 2017 05:55:57 -0700	[thread overview]
Message-ID: <ffb989$2cbuke@orsmga002.jf.intel.com> (raw)

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

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

_apply patch file failure_

Submitter: Gaetan Rivet <gaetan.rivet@6wind.com>
Date: Fri, 28 Apr 2017 12:10:26 +0200
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
                   Repo:dpdk-next-crypto, Branch:master, CommitID:813b86268aa62bf0ecf7d0c54977b0130d410852
                   Repo:dpdk-next-net, Branch:master, CommitID:5bcfa8495adc048804a3b1f35602b8bf93ce334a
Apply patch file failed:
Repo: dpdk
23997:
patching file app/test-pmd/parameters.c
patching file app/test-pmd/testpmd.c
patching file app/test-pmd/testpmd.h
patching file doc/guides/testpmd_app_ug/run_app.rst
Hunk #1 FAILED at 473.
1 out of 1 hunk FAILED -- saving rejects to file doc/guides/testpmd_app_ug/run_app.rst.rej

Repo: dpdk-next-crypto
23997:
patching file app/test-pmd/parameters.c
patching file app/test-pmd/testpmd.c
patching file app/test-pmd/testpmd.h
patching file doc/guides/testpmd_app_ug/run_app.rst
Hunk #1 FAILED at 473.
1 out of 1 hunk FAILED -- saving rejects to file doc/guides/testpmd_app_ug/run_app.rst.rej

Repo: dpdk-next-net
23997:
patching file app/test-pmd/parameters.c
patching file app/test-pmd/testpmd.c
patching file app/test-pmd/testpmd.h
patching file doc/guides/testpmd_app_ug/run_app.rst
Hunk #1 FAILED at 473.
1 out of 1 hunk FAILED -- saving rejects to file doc/guides/testpmd_app_ug/run_app.rst.rej

Repo: dpdk-next-virtio
23997:
patching file app/test-pmd/parameters.c
patching file app/test-pmd/testpmd.c
patching file app/test-pmd/testpmd.h
patching file doc/guides/testpmd_app_ug/run_app.rst
Hunk #1 FAILED at 473.
1 out of 1 hunk FAILED -- saving rejects to file doc/guides/testpmd_app_ug/run_app.rst.rej

Repo: dpdk-next-eventdev
23997:
patching file app/test-pmd/parameters.c
Hunk #1 FAILED at 202.
Hunk #2 succeeded at 493 (offset -6 lines).
Hunk #3 FAILED at 603.
Hunk #4 FAILED at 1039.
3 out of 4 hunks FAILED -- saving rejects to file app/test-pmd/parameters.c.rej
patching file app/test-pmd/testpmd.c
Hunk #1 succeeded at 263 with fuzz 1 (offset -18 lines).
Hunk #2 FAILED at 1817.
1 out of 2 hunks FAILED -- saving rejects to file app/test-pmd/testpmd.c.rej
patching file app/test-pmd/testpmd.h
Hunk #1 FAILED at 307.
1 out of 1 hunk FAILED -- saving rejects to file app/test-pmd/testpmd.h.rej
patching file doc/guides/testpmd_app_ug/run_app.rst
Hunk #1 FAILED at 473.
1 out of 1 hunk FAILED -- saving rejects to file doc/guides/testpmd_app_ug/run_app.rst.rej


DPDK STV team

                 reply	other threads:[~2017-04-28 12:56 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='ffb989$2cbuke@orsmga002.jf.intel.com' \
    --to=sys_stv@intel.com \
    --cc=gaetan.rivet@6wind.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).