https://bugs.kde.org/show_bug.cgi?id=504956
Mark Wielaard <m...@klomp.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #4 from Mark Wielaard <m...@klomp.org> ---
Very nice. The upgrade to LTP 20250530 and LTP_REPRODUCIBLE_OUTPUT=1 and
putting the full output/diffs in the logs make the wrapper script more useful.
Pushed as:
commit b8891a4c5d139b8c327ee20c37066d601fc56b0a
Author: Martin Cermak <mcer...@redhat.com>
Date: Tue Jun 3 13:43:18 2025 +0200
ltp tests: Use new LTP 20250530, allow for filtering valgrind output
Use fresh LTP 20250530.
Allow for filtering valgrind output:
In some cases the LTP tests intentionally work with SIGSEGV. This
happens e.g. with the mmap18 and select03 testcases. Valgrind
detects SIGSEGV and reports that as a failure.
Such report can't be suppressed using the suppressions mechanism.
That's why this update comes with "output filters". Filters are
scripts that read from their stdin, and write filtered output to
their stdout. Filters reside in auxprogs/filters.
This update comes with 2 filters: For mmap18, and for select03.
They are awk scripts.
Except for filters, this update also blacklists testcase fork13
because it is slow. It is possible to add comments prefixed with
the '#' sign (implicitly - because they don't match any testcase
name), so a comment is added too.
This update also introduces new default valgrind --vgdb=no switch. It
improves valgrind behavior with nftw01 nftw6401 setfsgid04 setfsgid03_16
and symlink03 testcases. These were previously complaining like this:
==22969== could not unlink /tmp/vgdb-pipe-from-vgdb-to-22969-by-root-on ...
--
You are receiving this mail because:
You are watching all bug changes.
