[dpdk-dev] [PATCH v2] ci: catch coredumps
Luca Boccassi
bluca at debian.org
Tue Mar 2 17:16:52 CET 2021
On Mon, 2021-01-25 at 16:05 +0100, David Marchand wrote:
> Parts of the unit tests code rely on forked/secondary processes
> (expectedly) failing.
> A crash in those situations could be missed so add a check on coredumps
> presence after unit tests have run.
> When unit tests fail, it can also help checking for coredumps as it
> could give more insights on what happened.
>
> In some situations (like explicit call to rte_panic), coredump generation
> must be disabled to avoid false positives.
>
> Signed-off-by: David Marchand <david.marchand at redhat.com>
> ---
> Changelog since RFC v1
> - removed RFC,
> - pushed coredumps into gdb for in-situ analysis,
> - gdb presence is used to enable the check. Travis config is left
> untouched for now,
>
> ---
> .ci/linux-build.sh | 37 ++++++++++++++++++++++++++++++++++---
> .github/workflows/build.yml | 4 ++++
> app/test/test_debug.c | 11 +++++++++--
> app/test/test_mbuf.c | 9 ++++++++-
> 4 files changed, 55 insertions(+), 6 deletions(-)
Acked-by: Luca Boccassi <bluca at debian.org>
This fixes an issue for me, with running the debug_autotest under a
reproducible build CI environment.
--
Kind regards,
Luca Boccassi
More information about the dev
mailing list