From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: xinfengx.zhao@intel.com, zhaoyan.chen@intel.com, peipeix.lu@intel.com
Subject: [dpdk-test-report] |FAILURE| pw38064[dpdk-dev, v5, 01/13] compressdev: add basic device management
Date: 24 Apr 2018 19:07:13 -0700 [thread overview]
Message-ID: <0590c7$1g6ubh@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1561 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/38064
_apply issues_
Submitter: Pablo de Lara <pablo.de.lara.guarch@intel.com>
Date: 2018-04-13 18:18:20
DPDK git baseline:
Repo:dpdk-master, CommitID: b65ecf1993247f90165923cd527edc798c2eeb43
Repo:dpdk-next-eventdev, CommitID: fe5abd3150bc1caa8369e743c395c39f53265597
Repo:dpdk-next-net, CommitID: 329502143e095229f8e90d5064849443c4250ef9
Repo:dpdk-next-crypto, CommitID: eb8a86e275ef15a5455948d679d1a2c43dd4c740
Repo:dpdk-next-virtio, CommitID: 81daf0ba4f2eb20c00975b474cb9b6ab71c44e25
*Repo: dpdk-master
Repo:dpdk-master, CommitID: b65ecf1993247f90165923cd527edc798c2eeb43
fatal: can't open patch '/root/regression_share/patches/38064.patch': No such file or directory
*Repo: dpdk-next-eventdev
Repo:dpdk-next-eventdev, CommitID: fe5abd3150bc1caa8369e743c395c39f53265597
fatal: can't open patch '/root/regression_share/patches/38064.patch': No such file or directory
*Repo: dpdk-next-net
Repo:dpdk-next-net, CommitID: 329502143e095229f8e90d5064849443c4250ef9
fatal: can't open patch '/root/regression_share/patches/38064.patch': No such file or directory
*Repo: dpdk-next-crypto
Repo:dpdk-next-crypto, CommitID: eb8a86e275ef15a5455948d679d1a2c43dd4c740
fatal: can't open patch '/root/regression_share/patches/38064.patch': No such file or directory
*Repo: dpdk-next-virtio
Repo:dpdk-next-virtio, CommitID: 81daf0ba4f2eb20c00975b474cb9b6ab71c44e25
fatal: can't open patch '/root/regression_share/patches/38064.patch': No such file or directory
DPDK STV team
reply other threads:[~2018-04-25 2:07 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$1g6ubh@orsmga001.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=peipeix.lu@intel.com \
--cc=test-report@dpdk.org \
--cc=xinfengx.zhao@intel.com \
--cc=zhaoyan.chen@intel.com \
/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).