From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: jasvinder.singh@intel.com
Subject: [dpdk-test-report] |FAILURE| pw23242 [PATCH v10 2/2] test/test: add unit test for CRC computation
Date: 09 Apr 2017 19:55:37 -0700 [thread overview]
Message-ID: <e81775$11opeh3@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3019 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/23242
_apply patch file failure_
Submitter: Jasvinder Singh <jasvinder.singh@intel.com>
Date: Wed, 5 Apr 2017 15:58:46 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:7cd3013644c38feeb698f3a3610a273b3d2a354e
Repo:dpdk-next-crypto, Branch:master, CommitID:909712510060d458abdb1ac9a9360352b177aad8
Repo:dpdk-next-net, Branch:master, CommitID:0c6bfd67c67a4a4bff428aca6171a3fbff4f69b4
Repo:dpdk-next-virtio, Branch:master, CommitID:9c77b848b1c1edf31343e70776f7767350047d01
Repo:dpdk, Branch:master, CommitID:a4dad8a0c1f4c93f53e2bc3982e957ae5e00bcb0
Apply patch file failed:
Repo: dpdk
23242:
patching file MAINTAINERS
Hunk #1 FAILED at 484.
1 out of 1 hunk FAILED -- saving rejects to file MAINTAINERS.rej
patching file test/test/Makefile
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file test/test/Makefile.rej
The next patch would create the file test/test/test_crc.c,
which already exists! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored
Repo: dpdk-next-crypto
23242:
patching file MAINTAINERS
Hunk #1 FAILED at 484.
1 out of 1 hunk FAILED -- saving rejects to file MAINTAINERS.rej
patching file test/test/Makefile
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file test/test/Makefile.rej
The next patch would create the file test/test/test_crc.c,
which already exists! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored
Repo: dpdk-next-net
23242:
patching file MAINTAINERS
Hunk #1 FAILED at 484.
1 out of 1 hunk FAILED -- saving rejects to file MAINTAINERS.rej
patching file test/test/Makefile
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file test/test/Makefile.rej
The next patch would create the file test/test/test_crc.c,
which already exists! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored
Repo: dpdk-next-virtio
23242:
patching file MAINTAINERS
Hunk #1 FAILED at 484.
1 out of 1 hunk FAILED -- saving rejects to file MAINTAINERS.rej
patching file test/test/Makefile
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file test/test/Makefile.rej
The next patch would create the file test/test/test_crc.c,
which already exists! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored
Repo: dpdk-next-eventdev
23242:
patching file MAINTAINERS
Hunk #1 FAILED at 484.
1 out of 1 hunk FAILED -- saving rejects to file MAINTAINERS.rej
patching file test/test/Makefile
patching file test/test/test_crc.c
DPDK STV team
reply other threads:[~2017-04-10 2:55 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='e81775$11opeh3@fmsmga001.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=jasvinder.singh@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).