public inbox for dev@dpdk.org
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: dev@dpdk.org
Cc: anatoly.burakov@intel.com, Bruce Richardson <bruce.richardson@intel.com>
Subject: [PATCH 0/3] improve debug output for EAL flags unit tests
Date: Tue, 20 Jan 2026 11:25:49 +0000	[thread overview]
Message-ID: <20260120112552.921243-1-bruce.richardson@intel.com> (raw)

If issues arise in the EAL flags unit tests they can be trick to debug
due to the lack of debugging output when running recursive instances of
the test binary with different EAL flags. Try to improve this situation
by adding extra debug output for recursive dpdk-test calls in general,
and to some of the EAL flags tests in particular that are proving
problematic.

NOTE: there are intermittent failures seen in github actions with the
file-prefix EAL unit tests. The problems seem less frequent, or possibly
"gone", with this set applied, but even if it masks the problem, this
set does give us greater visibility to debug if they do re-occur.

Bruce Richardson (3):
  app/test: add extra logging for recursive calls
  test/eal_flags: add line numbers to error messages
  test/eal_flags: add extra logging for file prefix tests

 app/test/test.c           |  14 +-
 app/test/test_eal_flags.c | 373 ++++++++++++++++++++++----------------
 2 files changed, 224 insertions(+), 163 deletions(-)

--
2.51.0


             reply	other threads:[~2026-01-20 11:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-20 11:25 Bruce Richardson [this message]
2026-01-20 11:25 ` [PATCH 1/3] app/test: add extra logging for recursive calls Bruce Richardson
2026-01-20 11:25 ` [PATCH 2/3] test/eal_flags: add line numbers to error messages Bruce Richardson
2026-01-20 15:03   ` Stephen Hemminger
2026-01-20 15:22     ` Bruce Richardson
2026-01-20 11:25 ` [PATCH 3/3] test/eal_flags: add extra logging for file prefix tests Bruce Richardson
2026-01-21  9:14 ` [PATCH 0/3] improve debug output for EAL flags unit tests David Marchand
2026-01-23 11:08   ` David Marchand
2026-01-23 11:28     ` Bruce Richardson

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=20260120112552.921243-1-bruce.richardson@intel.com \
    --to=bruce.richardson@intel.com \
    --cc=anatoly.burakov@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