From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: fiona.trahe@intel.com
Subject: [dpdk-test-report] |FAILURE| pw39857 [PATCH 2/5] crypto/qat: move to dynamic logging for non-dp trace
Date: 14 May 2018 01:52:04 -0700 [thread overview]
Message-ID: <0590c7$1l37qc@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3257 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/39857
_apply patch file failure_
Submitter: Fiona Trahe <fiona.trahe@intel.com>
Date: Fri, 11 May 2018 12:31:45 +0100
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:3c955492b601d65402c02ac81dfdc7eeb62f23c9
Repo:dpdk-next-crypto, Branch:master, CommitID:e0d88a394e91f446234aa04d0f9e01c150b0d347
Repo:dpdk-next-net, Branch:master, CommitID:dc33238da4be9cf69e44049cd44950fb4fe74e3b
Repo:dpdk-next-virtio, Branch:master, CommitID:037c0996bc927342f157426739e0cb63f2db8689
Repo:dpdk, Branch:master, CommitID:3b97888ab2a8405bcbe198abdcc8ac98ee0f0e96
Apply patch file failed:
Repo: dpdk
39857:
patching file config/common_base
Hunk #1 succeeded at 489 with fuzz 2 (offset 5 lines).
patching file drivers/crypto/qat/Makefile
Hunk #1 FAILED at 26.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/qat/Makefile.rej
patching file drivers/crypto/qat/meson.build
Hunk #1 FAILED at 8.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/qat/meson.build.rej
patching file drivers/crypto/qat/qat_logs.c
patching file drivers/crypto/qat/qat_logs.h
Repo: dpdk-next-crypto
39857:
patching file config/common_base
Hunk #1 succeeded at 484 with fuzz 2.
patching file drivers/crypto/qat/Makefile
Hunk #1 FAILED at 26.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/qat/Makefile.rej
patching file drivers/crypto/qat/meson.build
Hunk #1 FAILED at 8.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/qat/meson.build.rej
patching file drivers/crypto/qat/qat_logs.c
patching file drivers/crypto/qat/qat_logs.h
Repo: dpdk-next-net
39857:
patching file config/common_base
Hunk #1 succeeded at 487 with fuzz 2 (offset 3 lines).
patching file drivers/crypto/qat/Makefile
Hunk #1 FAILED at 26.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/qat/Makefile.rej
patching file drivers/crypto/qat/meson.build
Hunk #1 FAILED at 8.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/qat/meson.build.rej
patching file drivers/crypto/qat/qat_logs.c
patching file drivers/crypto/qat/qat_logs.h
Repo: dpdk-next-virtio
39857:
patching file config/common_base
Hunk #1 succeeded at 483 with fuzz 2 (offset -1 lines).
patching file drivers/crypto/qat/Makefile
Hunk #1 FAILED at 26.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/qat/Makefile.rej
patching file drivers/crypto/qat/meson.build
Hunk #1 FAILED at 8.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/qat/meson.build.rej
patching file drivers/crypto/qat/qat_logs.c
patching file drivers/crypto/qat/qat_logs.h
Repo: dpdk-next-eventdev
39857:
patching file config/common_base
Hunk #1 succeeded at 483 with fuzz 2 (offset -1 lines).
patching file drivers/crypto/qat/Makefile
Hunk #1 FAILED at 26.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/qat/Makefile.rej
patching file drivers/crypto/qat/meson.build
Hunk #1 FAILED at 8.
1 out of 1 hunk FAILED -- saving rejects to file drivers/crypto/qat/meson.build.rej
patching file drivers/crypto/qat/qat_logs.c
patching file drivers/crypto/qat/qat_logs.h
DPDK STV team
reply other threads:[~2018-05-14 8:52 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='0590c7$1l37qc@orsmga001.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=fiona.trahe@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).