bug-texinfo
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: texinfo-6.0.91 pretest


From: Gavin Smith
Subject: Re: texinfo-6.0.91 pretest
Date: Sat, 2 Jan 2016 10:45:39 +0000

On 2 January 2016 at 09:44, Eli Zaretskii <address@hidden> wrote:
> The failures in htmlxref tests are due to a formatting issue.  The
> diffs look like this:
>
>      diff --strip-trailing-cr -a -u -r 
> .//diffs/staging_res/htmlxref_nodes/test_refs.2 
> .//out_parser/htmlxref_nodes/test_refs.2
>      --- .//diffs/staging_res/htmlxref_nodes/test_refs.2     2014-12-19 
> 22:07:28 +0200
>      +++ .//out_parser/htmlxref_nodes/test_refs.2    2016-01-02 11:36:15 +0200
>      @@ -1,2 +1,2 @@
>      -./htmlxref.cnf:15: warning: unrecognized type: foo
>      -./htmlxref.cnf:16: warning: missing type
>      +htmlxref.cnf:15: warning: unrecognized type: foo
>      +htmlxref.cnf:16: warning: missing type
>      FAIL test_scripts/htmlxref_htmlxref_nodes.sh (exit status: 1)
>
> So it's a "./foo" vs "foo" issue.  I don't think this is a real
> problem, is it?  If so, can this be fixed somehow so as not to cause
> bogus failure indications?  (Btw, why two slashes in "//diffs"?)

It's due to the Windows version of File::Spec->catfile canonicalizing
the path to remove a leading "./". It's called in "locate_init_file"
in texi2any.pl.

It would seem to be a loss to avoid this canonicalization for the sake
of the test suite. Maybe this test failure will just have to be
accepted under Windows. There are ways out, of course, e.g. multiple
reference output files, only one of which would have to match, or
conditional tests somehow, but I can't immediately think of anything
easy.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]