From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw42259[v3, 04/10] net/mlx5: split PCI from generic probing code
Date: 06 Jul 2018 00:53:28 -0700 [thread overview]
Message-ID: <0590c7$23838g@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1560 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/42259
_apply issues_
Submitter: Adrien Mazarguil <adrien.mazarguil@6wind.com>
Date: 2018-07-04 17:27:40
DPDK git baseline:
Repo:dpdk-master, CommitID: 05e0eee0001cb19671eb7e8d3dd68680a695fea2
Repo:dpdk-next-eventdev, CommitID: 9131a10a60bdbf8cd19e0158c6e01648a1d25e23
Repo:dpdk-next-net, CommitID: e5647516deae231db94b5488a6c3d48310ab619c
Repo:dpdk-next-crypto, CommitID: e4eb7ecc21bc161489d095f96e7769a1406fdaa4
Repo:dpdk-next-virtio, CommitID: 9b954f9c455a76304601deb88e2df1549dc9e09a
*Repo: dpdk-master
Repo:dpdk-master, CommitID: 05e0eee0001cb19671eb7e8d3dd68680a695fea2
fatal: can't open patch '/root/regression_share/patches/42259.patch': No such file or directory
*Repo: dpdk-next-eventdev
Repo:dpdk-next-eventdev, CommitID: 9131a10a60bdbf8cd19e0158c6e01648a1d25e23
fatal: can't open patch '/root/regression_share/patches/42259.patch': No such file or directory
*Repo: dpdk-next-net
Repo:dpdk-next-net, CommitID: e5647516deae231db94b5488a6c3d48310ab619c
fatal: can't open patch '/root/regression_share/patches/42259.patch': No such file or directory
*Repo: dpdk-next-crypto
Repo:dpdk-next-crypto, CommitID: e4eb7ecc21bc161489d095f96e7769a1406fdaa4
fatal: can't open patch '/root/regression_share/patches/42259.patch': No such file or directory
*Repo: dpdk-next-virtio
Repo:dpdk-next-virtio, CommitID: 9b954f9c455a76304601deb88e2df1549dc9e09a
fatal: can't open patch '/root/regression_share/patches/42259.patch': No such file or directory
DPDK STV team
next reply other threads:[~2018-07-06 7:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-06 7:53 sys_stv [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-07-06 6:53 sys_stv
2018-07-05 8:34 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='0590c7$23838g@orsmga001.jf.intel.com' \
--to=sys_stv@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).