improve debug output for EAL flags unit tests
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest3 patches 5 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | app/test: add extra logging for recursive callsapp/ | +12 | 0 replies | |
| 2/3 | test/eal_flags: add line numbers to error messagesapp/ | +207 | 2 replies | |
| 3/3 | test/eal_flags: add extra logging for file prefix testsapp/ | +5 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
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