From: Bruce Richardson <bruce.richardson@intel.com>
To: David Marchand <david.marchand@redhat.com>
Cc: <dev@dpdk.org>
Subject: Re: [PATCH 2/2] test/eal_flags: add EAL debug logs to recursive calls
Date: Tue, 3 Feb 2026 15:39:58 +0000 [thread overview]
Message-ID: <aYIWzrmzknYkwcNw@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <CAJFAV8yRYXKjQCniarc=u9fYuh-1GYTnKr-fnEJDQwEOrZuSeQ@mail.gmail.com>
On Tue, Feb 03, 2026 at 03:17:43PM +0100, David Marchand wrote:
> On Mon, 26 Jan 2026 at 17:45, Bruce Richardson
> <bruce.richardson@intel.com> wrote:
> >
> > When we make recursive calls to dpdk-test to check flag support, either
> > as a secondary process or as another primary process, add the log-level
> > flag to give extra EAL output to help with debugging any issues. For
> > calls that are spawning another primary process, pass in --no-pci flag
> > too, to skip device probing.
> >
> > Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
>
> On one side, the debug will probably help with future errors.
> But on the second change, the --no-pci stuff is not about debug it
> seems more like an actual fix (or well, a way to hide the issue in
> CI).
>
> I would prefer we split in two.
>
Good point, that is correct. I felt that sometimes we may be at the mercy
of the actual hardware the CI is running on, so disabling pci probing
should make things more reliable. Will see about splitting this patch into
two parts to evaluate separately.
/Bruce
next prev parent reply other threads:[~2026-02-03 15:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-26 16:45 [PATCH 1/2] eal: add location info to interrupt error message Bruce Richardson
2026-01-26 16:45 ` [PATCH 2/2] test/eal_flags: add EAL debug logs to recursive calls Bruce Richardson
2026-02-03 14:17 ` David Marchand
2026-02-03 15:39 ` Bruce Richardson [this message]
2026-01-26 18:16 ` [PATCH 1/2] eal: add location info to interrupt error message Stephen Hemminger
2026-02-13 15:22 ` [PATCH v2 0/3] improve error reporting & resilience in unit tests Bruce Richardson
2026-02-13 15:22 ` [PATCH v2 1/3] eal: add location info to interrupt error message Bruce Richardson
2026-02-13 15:22 ` [PATCH v2 2/3] test/eal_flags: add EAL debug flags to recursive calls Bruce Richardson
2026-02-13 15:22 ` [PATCH v2 3/3] test/eal_flags: remove PCI probing for " Bruce Richardson
2026-02-16 14:48 ` [PATCH v2 0/3] improve error reporting & resilience in unit tests David Marchand
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=aYIWzrmzknYkwcNw@bricha3-mobl1.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=david.marchand@redhat.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