From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: jfreimann@redhat.com
Subject: [dpdk-test-report] |FAILURE| pw26333 [PATCH 2/3] vhost: check return values of pthread_* calls
Date: 05 Jul 2017 13:43:36 -0700 [thread overview]
Message-ID: <e81775$12qauhq@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1551 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/26333
_apply patch file failure_
Submitter: Jens Freimann <jfreimann@redhat.com>
Date: Tue, 4 Jul 2017 10:50:41 +0200
DPDK git baseline: Repo:dpdk-next-eventdev, Branch:master, CommitID:9fc7090f258bb1a5b624f8ebbec551d0017c1399
Repo:dpdk-next-crypto, Branch:master, CommitID:90c21ceb6a1040bbc9ca611d0829987f2978225d
Repo:dpdk-next-net, Branch:master, CommitID:cb6294fdc3fced7c12219bae0ea8e62f02199aa1
Repo:dpdk-next-virtio, Branch:master, CommitID:98b53e38c195c0140d1b9d5b412986f3b92cfcf3
Repo:dpdk, Branch:master, CommitID:a3a2e2c8f7de433e10b1548df65b20bf10086d9c
Apply patch file failed:
Repo: dpdk
26333:
patching file lib/librte_vhost/socket.c
Hunk #2 FAILED at 647.
Hunk #3 FAILED at 658.
2 out of 3 hunks FAILED -- saving rejects to file lib/librte_vhost/socket.c.rej
Repo: dpdk-next-crypto
26333:
patching file lib/librte_vhost/socket.c
Hunk #2 FAILED at 647.
Hunk #3 FAILED at 658.
2 out of 3 hunks FAILED -- saving rejects to file lib/librte_vhost/socket.c.rej
Repo: dpdk-next-net
26333:
patching file lib/librte_vhost/socket.c
Hunk #2 FAILED at 647.
Hunk #3 FAILED at 658.
2 out of 3 hunks FAILED -- saving rejects to file lib/librte_vhost/socket.c.rej
Repo: dpdk-next-eventdev
26333:
patching file lib/librte_vhost/socket.c
Hunk #2 FAILED at 647.
Hunk #3 FAILED at 658.
2 out of 3 hunks FAILED -- saving rejects to file lib/librte_vhost/socket.c.rej
DPDK STV team
reply other threads:[~2017-07-05 20:43 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$12qauhq@fmsmga001.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=jfreimann@redhat.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).