Make the stack trace test of t/20-bad.t more predictable

[perl/modules/Test-Valgrind.git] / MANIFEST

diff --git a/MANIFEST b/MANIFEST
index 7e8fd165b3df06960bddc25ff7abfbd047ee7b95..70c1d21fd7267c1e0ad5e1934e261868c8b50fa7 100644 (file)
--- a/MANIFEST
+++ b/MANIFEST
@@ -1,5 +1,7 @@
 Changes
+INSTALL.SKIP
 MANIFEST
+META.json
 META.yml
 Makefile.PL
 README
@@ -14,7 +16,11 @@ lib/Test/Valgrind/Command.pm
 lib/Test/Valgrind/Command/Aggregate.pm
 lib/Test/Valgrind/Command/Perl.pm
 lib/Test/Valgrind/Command/PerlScript.pm
+lib/Test/Valgrind/Component.pm
+lib/Test/Valgrind/Parser.pm
 lib/Test/Valgrind/Parser/Suppressions/Text.pm
+lib/Test/Valgrind/Parser/Text.pm
+lib/Test/Valgrind/Parser/XML.pm
 lib/Test/Valgrind/Parser/XML/Twig.pm
 lib/Test/Valgrind/Report.pm
 lib/Test/Valgrind/Session.pm
@@ -27,7 +33,9 @@ samples/xml-output-protocol4.txt
 t/00-load.t
 t/10-good.t
 t/20-bad.t
+t/70-session.t
 t/80-suppressions.t
+t/81-suppressions-demangle.t
 t/91-pod.t
 t/92-pod-coverage.t
 t/95-portability-files.t