From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: nelio.laranjeiro@6wind.com
Subject: [dpdk-test-report] |FAILURE| pw20292 [PATCH 3/3] doc: update release notes for mlx5
Date: 12 Feb 2017 22:54:26 -0800 [thread overview]
Message-ID: <e81775$10vaqa2@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2289 bytes --]
Test-Label: Intel compilation
Test-Status: FAILURE
http://dpdk.org/patch/20292
_apply patch file failure_
Submitter: =?utf-8?q?N=C3=A9lio_Laranjeiro?= <nelio.laranjeiro@6wind.com>
Date: Thu, 9 Feb 2017 09:32:01 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:656973204976b3f7fc7b0b993e2f1a47afbf151a
Repo:dpdk-next-crypto, Branch:master, CommitID:e62cd3c8f784edc612cc16d1485a45e0f44c2e16
Repo:dpdk-next-net, Branch:master, CommitID:47aa9d4e0d0cc308f41f2ae17d629b869112ad71
Repo:dpdk-next-virtio, Branch:master, CommitID:a69de21ee881adb095667a15a28fbf5044e22a28
Repo:dpdk, Branch:master, CommitID:47aa9d4e0d0cc308f41f2ae17d629b869112ad71
Apply patch file failed:
Repo: dpdk
20292:
patching file doc/guides/nics/mlx5.rst
patching file doc/guides/rel_notes/release_17_02.rst
Hunk #1 succeeded at 133 (offset 2 lines).
Hunk #2 FAILED at 469.
1 out of 2 hunks FAILED -- saving rejects to file doc/guides/rel_notes/release_17_02.rst.rej
Repo: dpdk-next-crypto
20292:
patching file doc/guides/nics/mlx5.rst
patching file doc/guides/rel_notes/release_17_02.rst
Hunk #1 succeeded at 133 (offset 2 lines).
Hunk #2 FAILED at 469.
1 out of 2 hunks FAILED -- saving rejects to file doc/guides/rel_notes/release_17_02.rst.rej
Repo: dpdk-next-net
20292:
patching file doc/guides/nics/mlx5.rst
patching file doc/guides/rel_notes/release_17_02.rst
Hunk #1 succeeded at 133 (offset 2 lines).
Hunk #2 FAILED at 469.
1 out of 2 hunks FAILED -- saving rejects to file doc/guides/rel_notes/release_17_02.rst.rej
Repo: dpdk-next-virtio
20292:
patching file doc/guides/nics/mlx5.rst
Hunk #1 succeeded at 242 (offset -1 lines).
Hunk #2 succeeded at 270 (offset -1 lines).
patching file doc/guides/rel_notes/release_17_02.rst
Hunk #1 succeeded at 114 (offset -17 lines).
Hunk #2 FAILED at 469.
1 out of 2 hunks FAILED -- saving rejects to file doc/guides/rel_notes/release_17_02.rst.rej
Repo: dpdk-next-eventdev
20292:
patching file doc/guides/nics/mlx5.rst
patching file doc/guides/rel_notes/release_17_02.rst
Hunk #1 succeeded at 133 (offset 2 lines).
Hunk #2 FAILED at 469.
1 out of 2 hunks FAILED -- saving rejects to file doc/guides/rel_notes/release_17_02.rst.rej
DPDK STV team
next reply other threads:[~2017-02-13 6:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-13 6:54 sys_stv [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-02-09 12:35 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$10vaqa2@fmsmga001.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=nelio.laranjeiro@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).