automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report]  |FAILURE| pw69946[v3, 1/7] eal: move OS common functions to single file
Date: 07 May 2020 16:32:41 -0700	[thread overview]
Message-ID: <fecc85$a3p8ka@orsmga001.jf.intel.com> (raw)

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

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

_apply issues_

Submitter: Tal Shnaiderman <talshn@mellanox.com>
Date: 2020-05-07 12:16:40
Reply_mail: 20200507121646.624-2-talshn@mellanox.com
DPDK git baseline:
	Repo:dpdk, CommitID: dec44d41109dac609d83805c0b906df446f8680e

*Repo: dpdk
/**
 * Structure storing internal configuration (per-lcore)
 */

error: patch failed: lib/librte_eal/common/eal_private.h:13
error: lib/librte_eal/common/eal_private.h: patch does not apply
Checking patch lib/librte_eal/common/meson.build...
error: while searching for:
		'eal_common_string_fns.c',
		'eal_common_tailqs.c',
		'eal_common_thread.c',
		'malloc_elem.c',
		'malloc_heap.c',
		'rte_malloc.c',

error: patch failed: lib/librte_eal/common/meson.build:21
error: lib/librte_eal/common/meson.build: patch does not apply
Checking patch lib/librte_eal/freebsd/eal.c...
Checking patch lib/librte_eal/linux/eal.c...
Checking patch lib/librte_eal/windows/eal.c...
Hunk #1 succeeded at 28 (offset -3 lines).
--

/* display usage */
static void
eal_usage(const char *prgname)

error: patch failed: lib/librte_eal/windows/eal.c:93
error: lib/librte_eal/windows/eal.c: patch does not apply

DPDK STV team

                 reply	other threads:[~2020-05-07 23:32 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='fecc85$a3p8ka@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).