DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: <kirankumark@marvell.com>
Cc: Jerin Jacob <jerinj@marvell.com>,
	Nithin Dabilpuram <ndabilpuram@marvell.com>,
	Zhirun Yan <yanzhirun_163@163.com>, <dev@dpdk.org>,
	<rjarry@redhat.com>, <chcchc88@163.com>
Subject: Re: [PATCH v4 3/3] test/graph: fix graph autotest second run test failure
Date: Thu, 14 Nov 2024 09:09:00 -0800	[thread overview]
Message-ID: <20241114090849.02c3d953@hermes.local> (raw)
In-Reply-To: <20241114090806.3266673-3-kirankumark@marvell.com>

On Thu, 14 Nov 2024 14:38:06 +0530
<kirankumark@marvell.com> wrote:

> From: Kiran Kumar K <kirankumark@marvell.com>
> 
> The graph autotest second run test is failing due to the
> node name is already present in the node list. Adding changes
> to free nodes at the time of test cleanup.
> 
> Fixes: 6b89650418fe ("test/graph: add functional tests")
> 
> Signed-off-by: Kiran Kumar K <kirankumark@marvell.com>
> ---
>  app/test/test_graph.c | 96 ++++++++++++++++++++++++++++++++++++++++---
>  1 file changed, 90 insertions(+), 6 deletions(-)
> 
> diff --git a/app/test/test_graph.c b/app/test/test_graph.c
> index 2840a25b13..e712dbebf7 100644
> --- a/app/test/test_graph.c
> +++ b/app/test/test_graph.c
> @@ -68,6 +68,8 @@ static void *mbuf_p[MAX_NODES + 1][MBUFF_SIZE];
>  static rte_graph_t graph_id;
>  static uint64_t obj_stats[MAX_NODES + 1];
>  static uint64_t fn_calls[MAX_NODES + 1];
> +static uint32_t dummy_nodes_id[MAX_NODES];
> +static int dummy_nodes_id_count;

Why is dummy_nodes_id_count signed? Can it ever be negative?
If not better to use unsigned or uint32_t

      reply	other threads:[~2024-11-14 17:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-14  7:04 [PATCH v3 1/3] graph: avoid global node ID counter kirankumark
2024-11-14  7:04 ` [PATCH v3 2/3] graph: add support for node free API kirankumark
2024-11-14  7:04 ` [PATCH v3 3/3] test/graph: fix graph autotest second run test failure kirankumark
2024-11-14  9:08 ` [PATCH v4 1/3] graph: avoid global node ID counter kirankumark
2024-11-14  9:08   ` [PATCH v4 2/3] graph: add support for node free API kirankumark
2024-11-14 17:07     ` Stephen Hemminger
2024-11-14  9:08   ` [PATCH v4 3/3] test/graph: fix graph autotest second run test failure kirankumark
2024-11-14 17:09     ` Stephen Hemminger [this message]

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=20241114090849.02c3d953@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=chcchc88@163.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=kirankumark@marvell.com \
    --cc=ndabilpuram@marvell.com \
    --cc=rjarry@redhat.com \
    --cc=yanzhirun_163@163.com \
    /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).