From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
To: Lincoln Lavoie <lylavoie@iol.unh.edu>
Cc: dev <dev@dpdk.org>, Zhihong Peng <zhihongx.peng@intel.com>,
Neil Horman <nhorman@tuxdriver.com>,
ci@dpdk.org
Subject: Re: [dpdk-dev] [dpdk-ci] [PATCH v2] pmdinfogen: allow padding after NUL terminator
Date: Wed, 9 Jun 2021 19:48:51 +0300 [thread overview]
Message-ID: <20210609194851.5ff889b4@sovereign> (raw)
In-Reply-To: <CAOE1vsP76g1mzFFSSmZimV+E6YLNdU7FDkP-VjG+awhmg97gsA@mail.gmail.com>
2021-06-09 12:01 (UTC-0400), Lincoln Lavoie:
> Hi Dmitry,
>
> If the failing test is the unit test func_reentrancy_autotest, that is
> being looked into , as it seems like the test case does not reliably run.
> It passes / fails between different systems running both on bare metal and
> in virtual environments, on different OSes and architectures.
>
> Do you have a link to your patch in patchworks or the lab dashboard?
Hi Lincoln,
Yes, this is func_reentrancy_autotest failure.
Dashboard link:
https://lab.dpdk.org/results/dashboard/patchsets/17240/
MTU and stats can hardly be affected by this patch.
next prev parent reply other threads:[~2021-06-09 16:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-26 21:43 [dpdk-dev] [PATCH] pmdinfogen: allow padding after NUL terminator Dmitry Kozlyuk
2021-05-27 6:53 ` David Marchand
2021-05-27 7:09 ` Dmitry Kozlyuk
2021-05-27 7:31 ` David Marchand
2021-05-27 21:24 ` [dpdk-dev] [PATCH v2] " Dmitry Kozlyuk
2021-06-09 15:52 ` Dmitry Kozlyuk
2021-06-09 16:01 ` [dpdk-dev] [dpdk-ci] " Lincoln Lavoie
2021-06-09 16:48 ` Dmitry Kozlyuk [this message]
2021-06-09 17:19 ` Owen Hilyard
2021-06-18 14:39 ` [dpdk-dev] " Thomas Monjalon
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=20210609194851.5ff889b4@sovereign \
--to=dmitry.kozliuk@gmail.com \
--cc=ci@dpdk.org \
--cc=dev@dpdk.org \
--cc=lylavoie@iol.unh.edu \
--cc=nhorman@tuxdriver.com \
--cc=zhihongx.peng@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.