> Date: Wed, 14 Jan 2026 19:04:07 +0200
> From: Eli Zaretskii <[email protected]>
> Cc: [email protected], [email protected]
>
> And after all that, the tree finally builds successfully. Testing
> will begin tomorrow; probably again lots of fun!
Bottom line: not as bad as I feared: most tests pass.
The following 2 tests in info/t/ failed:
FAIL: t/dir-file-sloppily.sh
FAIL: t/dir-no-file.sh
These succeeded in Texinfo 7.2, so it's probably due to some change in
the implementation. But I cannot figure out where to look: other
tests that use INFO_PRINT_COMMAND succeed. Any pointers?
Also, how do I run a test so that the output file(s) are not deleted?
And how do I figure out what is the input file used by a test, so I
could run the test interactively and perhaps debug it? (I expected
for this information toi be in info/t/README, but couldn't find it
there; what did I miss?)
The following two tests fail in tta/tests:
FAIL: test_scripts/formatting_reuse_macro_expand_file.sh
FAIL: test_scripts/coverage_formatting_latex.sh
The first one has its diffs say just this:
-texi2any: warning: overwriting file:
formatting/out_parser/reuse_macro_expand_file/simplest.info
IOW, this warning was expected, but was missing. I see that this
warning comes from texi2any.c:merge_opened_files, but I don't know how
to investigate the reason(s) -- any hints?
The second failure is strange: there's no *.diff files, but 2 of the 3
files in res_parser are very different from out_parser. The file
out_parser/formatting.tex is empty, and out_parser/formatting.2 is
missing 21 lines, and has this extra line:
+Free to wrong pool 13beec0 not 88040400 at ../perl/Texinfo/Convert/LaTeX.pm
line 2674.
This looks like some code used 'free' from a long 'malloc' to free
some memory, like the allocation was done by Perl, but 'free' is from
tta/C code, or vice versa. How to investigate this?
And how do I know whether the tta/ tests were run with or without the
XS extensions and the rest of C code in the tta/ directory? (It might
be a good idea to announce this when the test suite starts.)
All the other tests either succeeded or were skipped.
