automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw43731[v2] hash table: add an iterator over conflicting entries
Date: 16 Aug 2018 00:36:55 -0700	[thread overview]
Message-ID: <0590c7$2ec41n@orsmga001.jf.intel.com> (raw)

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

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

_apply issues_

Submitter: Fu, Qiaobin <qiaobinf@bu.edu>
Date: 2018-08-16 07:30:06
DPDK git baseline:
	Repo:dpdk-master, CommitID: 76b9d9de5c7d747c381027156aac07735cb1bc0c
	Repo:dpdk-next-eventdev, CommitID: f094d5a870e88536eab6210f5eb8586906563809
	Repo:dpdk-next-net, CommitID: 76b9d9de5c7d747c381027156aac07735cb1bc0c
	Repo:dpdk-next-crypto, CommitID: 76b9d9de5c7d747c381027156aac07735cb1bc0c
	Repo:dpdk-next-virtio, CommitID: d68d0d7f99bb515f16307522c3cc0b83dbd7c0a5

*Repo: dpdk-master
Hunk #2 succeeded at 1349 (offset 182 lines).
Checking patch lib/librte_hash/rte_hash.h...
Hunk #1 succeeded at 64 (offset 3 lines).
Hunk #2 succeeded at 468 (offset 44 lines).
Checking patch lib/librte_hash/rte_hash_version.map...
error: while searching for:
	rte_hash_get_key_with_position;

} DPDK_2.2;

error: patch failed: lib/librte_hash/rte_hash_version.map:45
error: lib/librte_hash/rte_hash_version.map: patch does not apply
*Repo: dpdk-next-eventdev
Hunk #2 succeeded at 1349 (offset 182 lines).
Checking patch lib/librte_hash/rte_hash.h...
Hunk #1 succeeded at 64 (offset 3 lines).
Hunk #2 succeeded at 438 (offset 14 lines).
Checking patch lib/librte_hash/rte_hash_version.map...
error: while searching for:
	rte_hash_get_key_with_position;

} DPDK_2.2;

error: patch failed: lib/librte_hash/rte_hash_version.map:45
error: lib/librte_hash/rte_hash_version.map: patch does not apply
*Repo: dpdk-next-net
Hunk #2 succeeded at 1349 (offset 182 lines).
Checking patch lib/librte_hash/rte_hash.h...
Hunk #1 succeeded at 64 (offset 3 lines).
Hunk #2 succeeded at 468 (offset 44 lines).
Checking patch lib/librte_hash/rte_hash_version.map...
error: while searching for:
	rte_hash_get_key_with_position;

} DPDK_2.2;

error: patch failed: lib/librte_hash/rte_hash_version.map:45
error: lib/librte_hash/rte_hash_version.map: patch does not apply
*Repo: dpdk-next-crypto
Hunk #2 succeeded at 1349 (offset 182 lines).
Checking patch lib/librte_hash/rte_hash.h...
Hunk #1 succeeded at 64 (offset 3 lines).
Hunk #2 succeeded at 468 (offset 44 lines).
Checking patch lib/librte_hash/rte_hash_version.map...
error: while searching for:
	rte_hash_get_key_with_position;

} DPDK_2.2;

error: patch failed: lib/librte_hash/rte_hash_version.map:45
error: lib/librte_hash/rte_hash_version.map: patch does not apply
*Repo: dpdk-next-virtio
Hunk #2 succeeded at 1349 (offset 182 lines).
Checking patch lib/librte_hash/rte_hash.h...
Hunk #1 succeeded at 64 (offset 3 lines).
Hunk #2 succeeded at 468 (offset 44 lines).
Checking patch lib/librte_hash/rte_hash_version.map...
error: while searching for:
	rte_hash_get_key_with_position;

} DPDK_2.2;

error: patch failed: lib/librte_hash/rte_hash_version.map:45
error: lib/librte_hash/rte_hash_version.map: patch does not apply

DPDK STV team

                 reply	other threads:[~2018-08-16  7:36 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$2ec41n@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).