Skip to content

improve debug output for EAL flags unit tests

Bruce Richardson dpdk-dev 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest3 patches 5 repliesIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/3app/test: add extra logging for recursive callsapp/test/test.c+12 -20 replies
2/3test/eal_flags: add line numbers to error messagesapp/test/test_eal_flags.c+207 -1612 replies
3/3test/eal_flags: add extra logging for file prefix testsapp/test/test_eal_flags.c+5 -00 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [PATCH 0/3] improve debug output for EAL flags unit tests

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