automatic DPDK test reports
 help / color / mirror / Atom feed
* [dpdk-test-report]  |FAILURE| pw39860[dpdk-dev, 5/5] doc/qat: document debug options
@ 2018-05-14  2:03 sys_stv
  0 siblings, 0 replies; only message in thread
From: sys_stv @ 2018-05-14  2:03 UTC (permalink / raw)
  To: test-report; +Cc: xinfengx.zhao, zhaoyan.chen, peipeix.lu

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

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

_apply issues_

Submitter: Fiona Trahe <fiona.trahe@intel.com>
Date: 2018-05-11 11:31:48
DPDK git baseline:
	Repo:dpdk-master, CommitID: b8b8b344cb44bea46ac1d2037e8e5f1e742319f6
	Repo:dpdk-next-eventdev, CommitID: 3c955492b601d65402c02ac81dfdc7eeb62f23c9
	Repo:dpdk-next-net, CommitID: dc33238da4be9cf69e44049cd44950fb4fe74e3b
	Repo:dpdk-next-crypto, CommitID: e0d88a394e91f446234aa04d0f9e01c150b0d347
	Repo:dpdk-next-virtio, CommitID: 037c0996bc927342f157426739e0cb63f2db8689

*Repo: dpdk-master
Checking patch doc/guides/cryptodevs/qat.rst...
error: while searching for:
<pci bdf>_<service>, e.g. "0000:41:01.0_qat_sym".
This name can be passed to rte_cryptodev_get_dev_id() to get the device_id.
This is also the format of the slave parameter passed to the crypto scheduler.

error: patch failed: doc/guides/cryptodevs/qat.rst:371
error: doc/guides/cryptodevs/qat.rst: patch does not apply
*Repo: dpdk-next-eventdev
Checking patch doc/guides/cryptodevs/qat.rst...
error: while searching for:
<pci bdf>_<service>, e.g. "0000:41:01.0_qat_sym".
This name can be passed to rte_cryptodev_get_dev_id() to get the device_id.
This is also the format of the slave parameter passed to the crypto scheduler.

error: patch failed: doc/guides/cryptodevs/qat.rst:371
error: doc/guides/cryptodevs/qat.rst: patch does not apply
*Repo: dpdk-next-net
Checking patch doc/guides/cryptodevs/qat.rst...
error: while searching for:
<pci bdf>_<service>, e.g. "0000:41:01.0_qat_sym".
This name can be passed to rte_cryptodev_get_dev_id() to get the device_id.
This is also the format of the slave parameter passed to the crypto scheduler.

error: patch failed: doc/guides/cryptodevs/qat.rst:371
error: doc/guides/cryptodevs/qat.rst: patch does not apply
*Repo: dpdk-next-crypto
Checking patch doc/guides/cryptodevs/qat.rst...
error: while searching for:
<pci bdf>_<service>, e.g. "0000:41:01.0_qat_sym".
This name can be passed to rte_cryptodev_get_dev_id() to get the device_id.
This is also the format of the slave parameter passed to the crypto scheduler.

error: patch failed: doc/guides/cryptodevs/qat.rst:371
error: doc/guides/cryptodevs/qat.rst: patch does not apply
*Repo: dpdk-next-virtio
Checking patch doc/guides/cryptodevs/qat.rst...
error: while searching for:
<pci bdf>_<service>, e.g. "0000:41:01.0_qat_sym".
This name can be passed to rte_cryptodev_get_dev_id() to get the device_id.
This is also the format of the slave parameter passed to the crypto scheduler.

error: patch failed: doc/guides/cryptodevs/qat.rst:371
error: doc/guides/cryptodevs/qat.rst: patch does not apply

DPDK STV team

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2018-05-14  2:03 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-05-14  2:03 [dpdk-test-report] |FAILURE| pw39860[dpdk-dev, 5/5] doc/qat: document debug options sys_stv

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).