DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: dev@dpdk.org
Cc: Bruce Richardson <bruce.richardson@intel.com>
Subject: [PATCH 0/1] make file prefix unit test more resilient
Date: Thu, 14 Sep 2023 11:42:14 +0100	[thread overview]
Message-ID: <20230914104215.71408-1-bruce.richardson@intel.com> (raw)

When examining the IOL testing failures for patch series [1], I observed
that the failures reported were in the eal_flags_file_prefix unit test.
I was able to reproduce this on my system by passing an additional
"--on-pci" flag to the test run, since the log to the test has errors
about device availability. Adding the "no-pci" flag to the individual
test commands used by the unit tests fixed the issue thereafter,
allowing the test to pass in all cases for me. Therefore, I am
submitting this patch in the hopes of making the test more robust, since
the observed failures seem unrelated to the original patchset [1] I
submitted.

[1] http://patches.dpdk.org/project/dpdk/list/?series=29406

Bruce Richardson (1):
  app/test: skip PCI bus scan when testing prefix flags

 app/test/test_eal_flags.c | 20 ++++++++++----------
 1 file changed, 10 insertions(+), 10 deletions(-)

-- 
2.39.2


             reply	other threads:[~2023-09-14 10:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-14 10:42 Bruce Richardson [this message]
2023-09-14 10:42 ` [PATCH 1/1] app/test: skip PCI bus scan when testing prefix flags Bruce Richardson
2023-09-20 10:00 ` [PATCH 0/1] make file prefix unit test more resilient David Marchand
2023-09-20 10:09   ` Bruce Richardson
2023-09-22 12:57     ` Thomas Monjalon
2023-09-22 13:23       ` Bruce Richardson
2023-09-23  8:21         ` Thomas Monjalon
2023-09-25  8:02           ` Bruce Richardson
2023-09-26 15:08             ` Aaron Conole

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=20230914104215.71408-1-bruce.richardson@intel.com \
    --to=bruce.richardson@intel.com \
    --cc=dev@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).