Re: Texinfo 7.2.90 build with mingw.org's MinGW: testing

Eli Zaretskii <[email protected]>
Newsgroups gmane.comp.tex.texinfo.bugs
Message-ID <[email protected]>
> Date: Thu, 15 Jan 2026 21:54:32 +0100
> From: [email protected]
> Cc: [email protected], [email protected]
> 
> On Thu, Jan 15, 2026 at 03:48:19PM +0200, Eli Zaretskii wrote:
> > 
> >      FAIL: test_scripts/formatting_reuse_macro_expand_file.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?
> 
> First thing to do would be to go to tta/tests and run the test script to
> see if there is something wrong in the texi2any.pl call command line.
> It is possible, because this test is specified by:
> 
>   reuse_macro_expand_file simplest.texi --macro-expand=@[email protected]
> 
> and @OUT_DIR@ should be substituted by
> formatting/out_parser/reuse_macro_expand_file/
> but something may have gone wrong there.
> 
> To run that test, simply call, in tta/tests: 
> ./test_scripts/formatting_reuse_macro_expand_file.sh
> 
> I show below the output of such a call, you can see the command-line
> used to call texi2any.pl, this would be the first thing to check.
> 
> For me, the output is:
> 
> testdir: formatting
> driving_file: ./formatting/list-of-tests
> made result dir: ./formatting/res_parser/
> 
> doing test reuse_macro_expand_file, src_file ./formatting/simplest.texi
> format_option: 
> perl/texi2any.pl reuse_macro_expand_file -> formatting/out_parser/reuse_macro_expand_file
>  /usr/bin/perl -w ./..//perl/texi2any.pl  --force --conf-dir ./../perl/t/init/ --conf-dir ./../perl/init --conf-dir ./../perl/ext -I ./formatting -I formatting/ -I ./ -I . -I built_input -I built_input/non_ascii --error-limit=1000 -c TEST=2  --output formatting/out_parser/reuse_macro_expand_file/ --macro-expand=formatting/out_parser/reuse_macro_expand_file/simplest.info ./formatting/simplest.texi > formatting/out_parser/reuse_macro_expand_file/simplest.1 2>formatting/out_parser/reuse_macro_expand_file/simplest.2
> 
> all done, exiting with status 0

Here's my output:

  $ ./test_scripts/formatting_reuse_macro_expand_file.sh
  D: formatting/diffs/reuse_macro_expand_file.diff (printed below)
  diff --strip-trailing-cr -a -u --strip-trailing-cr -r ./formatting/res_parser/reuse_macro_expand_file/simplest.2 formatting/out_parser/reuse_macro_expand_file/simplest.2
  --- ./formatting/res_parser/reuse_macro_expand_file/simplest.2  2026-01-02 00:38:09 +0200
  +++ formatting/out_parser/reuse_macro_expand_file/simplest.2    2026-01-17 12:27:21 +0200
  @@ -1 +0,0 @@
  -texi2any: warning: overwriting file: formatting/out_parser/reuse_macro_expand_file/simplest.info
  D: formatting/diffs/reuse_macro_expand_file.diff (printed above)
  testdir: formatting
  driving_file: ./formatting/list-of-tests
  made result dir: ./formatting/res_parser/

  doing test reuse_macro_expand_file, src_file ./formatting/simplest.texi
  format_option:
  perl/texi2any.pl reuse_macro_expand_file -> formatting/out_parser/reuse_macro_expand_file
   /d/usr/Perl/bin/perl -w ./..//perl/texi2any.pl  --force --conf-dir ./../perl/t/init/ --conf-dir ./../perl/init --conf-dir ./../perl/ext -I ./formatting -I formatting/ -I ./ -I . -I built_input -I built_input/non_ascii --error-limit=1000 -c TEST=1  --output formatting/out_parser/reuse_macro_expand_file/ --macro-expand=formatting/out_parser/reuse_macro_expand_file/simplest.info ./formatting/simplest.texi > formatting/out_parser/reuse_macro_expand_file/simplest.1 2>formatting/out_parser/reuse_macro_expand_file/simplest.2

  all done, exiting with status 1

AFAICT, the only differences are:

  . I get diffs, whereas you don't
  . in my case the command says TEST=1, not TEST=2
  . the exit status is 1 and not 0

Does this give any clues as to what is going on?
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.