automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw63942[v1] rte_timer: add rte_timer_next_ticks
Date: 21 Jan 2020 14:05:28 -0800	[thread overview]
Message-ID: <ee68f5$9535fa@orsmga001.jf.intel.com> (raw)

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

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

_apply issues_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: 2019-12-17 00:55:03
Reply_mail: 20191217005503.31196-1-stephen@networkplumber.org
DPDK git baseline:
	Repo:dpdk, CommitID: 73c392e24f5e29acbe53044dccb6b07ebbae2467

*Repo: dpdk
/* dump statistics about timers */
static void
__rte_timer_dump_stats(struct rte_timer_data *timer_data __rte_unused, FILE *f)

error: patch failed: lib/librte_timer/rte_timer.c:978
error: lib/librte_timer/rte_timer.c: patch does not apply
Checking patch lib/librte_timer/rte_timer.h...
error: while searching for:
 */
int rte_timer_pending(struct rte_timer *tim);

/**
 * Manage the timer list and execute callback functions.
 *

error: patch failed: lib/librte_timer/rte_timer.h:331
error: lib/librte_timer/rte_timer.h: patch does not apply
Checking patch lib/librte_timer/rte_timer_version.map...
error: while searching for:
	rte_timer_alt_stop;
	rte_timer_data_alloc;
	rte_timer_data_dealloc;
	rte_timer_stop_all;
	rte_timer_subsystem_finalize;
};

error: patch failed: lib/librte_timer/rte_timer_version.map:23
error: lib/librte_timer/rte_timer_version.map: patch does not apply

DPDK STV team

             reply	other threads:[~2020-01-21 22:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-21 22:05 sys_stv [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-12-17  1:24 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='ee68f5$9535fa@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).