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| pw25475 [PATCH v5 3/7] vdev: implement parse bus operation
Date: 26 Jun 2017 18:45:48 -0700	[thread overview]
Message-ID: <e81775$12mvkv8@fmsmga001.fm.intel.com> (raw)

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

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

_apply patch file failure_

Submitter: Gaetan Rivet <gaetan.rivet@6wind.com>
Date: Wed, 21 Jun 2017 01:30:35 +0200
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:c687cebe095b2ea325aa012e2834b830f1f74eba
                   Repo:dpdk-next-crypto, Branch:master, CommitID:d90d576825aed49bc69eb5547017f064f776afb1
                   Repo:dpdk-next-net, Branch:master, CommitID:6c63442519d4c649b89003c48d13e3058ab361a6
                   Repo:dpdk-next-virtio, Branch:master, CommitID:da5129d9b6b53375667690970f6824565c1f1443
                   Repo:dpdk, Branch:master, CommitID:68918a3b1c03b642dfdcf13568790de55982e64c
                   
Apply patch file failed:
Repo: dpdk
25475:
patching file lib/librte_eal/common/eal_common_vdev.c
Hunk #1 succeeded at 102 (offset -2 lines).
Hunk #2 succeeded at 139 (offset -2 lines).
Hunk #3 FAILED at 391.
1 out of 3 hunks FAILED -- saving rejects to file lib/librte_eal/common/eal_common_vdev.c.rej

Repo: dpdk-next-crypto
25475:
patching file lib/librte_eal/common/eal_common_vdev.c
Hunk #1 succeeded at 102 (offset -2 lines).
Hunk #2 succeeded at 139 (offset -2 lines).
Hunk #3 FAILED at 391.
1 out of 3 hunks FAILED -- saving rejects to file lib/librte_eal/common/eal_common_vdev.c.rej

Repo: dpdk-next-net
25475:
patching file lib/librte_eal/common/eal_common_vdev.c
Hunk #1 succeeded at 102 (offset -2 lines).
Hunk #2 succeeded at 139 (offset -2 lines).
Hunk #3 FAILED at 391.
1 out of 3 hunks FAILED -- saving rejects to file lib/librte_eal/common/eal_common_vdev.c.rej

Repo: dpdk-next-virtio
25475:
patching file lib/librte_eal/common/eal_common_vdev.c
Hunk #1 succeeded at 102 (offset -2 lines).
Hunk #2 succeeded at 139 (offset -2 lines).
Hunk #3 FAILED at 391.
1 out of 3 hunks FAILED -- saving rejects to file lib/librte_eal/common/eal_common_vdev.c.rej

Repo: dpdk-next-eventdev
25475:
patching file lib/librte_eal/common/eal_common_vdev.c
Hunk #1 succeeded at 102 (offset -2 lines).
Hunk #2 succeeded at 139 (offset -2 lines).
Hunk #3 FAILED at 391.
1 out of 3 hunks FAILED -- saving rejects to file lib/librte_eal/common/eal_common_vdev.c.rej


DPDK STV team

             reply	other threads:[~2017-06-27  1:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-27  1:45 sys_stv [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-06-21 10:34 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='e81775$12mvkv8@fmsmga001.fm.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).