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| pw25143 [PATCH v4 10/19] bus: introduce bus scan policies
Date: 08 Jun 2017 08:07:06 -0700	[thread overview]
Message-ID: <e81775$12gfqs4@fmsmga001.fm.intel.com> (raw)

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

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

_apply patch file failure_

Submitter: Gaetan Rivet <gaetan.rivet@6wind.com>
Date: Thu,  8 Jun 2017 01:56:56 +0200
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:a93a816c27484017b86af9d19566218a846251f1
                   Repo:dpdk-next-crypto, Branch:master, CommitID:bc6ebd8c3e7391d3d0d909a9a068caf0f2171103
                   Repo:dpdk-next-net, Branch:master, CommitID:cc9b164786c61feb814f32d799393656815a3305
                   Repo:dpdk-next-virtio, Branch:master, CommitID:101a00a4811479e7f66829e523c9138288831b39
                   Repo:dpdk, Branch:master, CommitID:c6dfeecb1581103c2a6cd95c8158e8bff18b9667
                   
Apply patch file failed:
Repo: dpdk
25143:
patching file lib/librte_eal/common/include/rte_bus.h
Hunk #1 succeeded at 82 with fuzz 1 (offset -55 lines).
Hunk #2 FAILED at 164.
1 out of 2 hunks FAILED -- saving rejects to file lib/librte_eal/common/include/rte_bus.h.rej

Repo: dpdk-next-crypto
25143:
patching file lib/librte_eal/common/include/rte_bus.h
Hunk #1 succeeded at 82 with fuzz 1 (offset -55 lines).
Hunk #2 FAILED at 164.
1 out of 2 hunks FAILED -- saving rejects to file lib/librte_eal/common/include/rte_bus.h.rej

Repo: dpdk-next-net
25143:
patching file lib/librte_eal/common/include/rte_bus.h
Hunk #1 succeeded at 82 with fuzz 1 (offset -55 lines).
Hunk #2 FAILED at 164.
1 out of 2 hunks FAILED -- saving rejects to file lib/librte_eal/common/include/rte_bus.h.rej

Repo: dpdk-next-virtio
25143:
patching file lib/librte_eal/common/include/rte_bus.h
Hunk #1 succeeded at 82 with fuzz 1 (offset -55 lines).
Hunk #2 FAILED at 164.
1 out of 2 hunks FAILED -- saving rejects to file lib/librte_eal/common/include/rte_bus.h.rej

Repo: dpdk-next-eventdev
25143:
patching file lib/librte_eal/common/include/rte_bus.h
Hunk #1 succeeded at 82 with fuzz 1 (offset -55 lines).
Hunk #2 FAILED at 164.
1 out of 2 hunks FAILED -- saving rejects to file lib/librte_eal/common/include/rte_bus.h.rej


DPDK STV team

             reply	other threads:[~2017-06-08 15:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-08 15:07 sys_stv [this message]
2017-06-20  1:21 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$12gfqs4@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).