Am Mittwoch, 23. Januar 2019 10:38:52 CET schrieb Guenter Milde <mi...@users.sf.net>: > On 2019-01-23, Kornel Benko wrote: > > Am Dienstag, 22. Januar 2019 21:21:52 CET schrieb Guenter Milde > > <mi...@users.sf.net>: > >> On 2019-01-22, Kornel Benko wrote: > > >> > The following tests FAILED: > >> > 5886 - > >> > UNRELIABLE.VARYING_VERSIONS_export/examples/ja/multilingual_lyx16 > >> > (Failed) > >> > 5887 - > >> > UNRELIABLE.VARYING_VERSIONS_export/examples/ja/multilingual_lyx20 > >> > (Failed) > >> > 5888 - > >> > UNRELIABLE.VARYING_VERSIONS_export/examples/ja/multilingual_lyx21 > >> > (Failed) > >> > 5889 - > >> > UNRELIABLE.VARYING_VERSIONS_export/examples/ja/multilingual_lyx22 > >> > (Failed) > >> > 5890 - > >> > UNRELIABLE.VARYING_VERSIONS_export/examples/ja/multilingual_lyx23 > >> > (Failed) > > >> The lyx2lyx export works in setups where "python" defaults to Python 3. > >> There is an encoding error with Python 2. I am not fully aware of the > >> state of discussion regarding moving to Python 3 and hesitate to inverst > >> time in fixing an issue that becomes a non-issue with this move. > > > This is a pity. I am reluctant to change the system setting, which may > > affect other programs. > > Of course this is not what I expect from users. > > Currently, the "lib/lyx2lyx/lyx2lyx" main script has the "shebang line" > > #! /usr/bin/python3 > > but LyX calls it via "python <path-to>/lyx2lyx". > > This means that users out do the conversion with different Python versions, > depending on the system setup. > > If we are serious about only supporting Python 3, we should change the way > LyX calls the lyx2lyx converter (and other Python scripts). > Under Linux, this would be replacing the command name `python` with `python3`. > Maybe we need to check in the "configure" script for `python3` first and > otherwise check the version for `python`. > > > Nevertheless, I spend some hours and fixed the encoding issue. > Now only 2 lyx2lyx tests are failing: > > The following tests FAILED: > 6008 - > UNRELIABLE.VARYING_VERSIONS_export/examples/ja/multilingual_lyx22 (Failed) > 6009 - > UNRELIABLE.VARYING_VERSIONS_export/examples/ja/multilingual_lyx23 (Failed)
OK
> It took some time and looking in the log to find out that this is due to the
> failing of the recently added compilation step.
Digging through my bad memory, wasn't it your idea to check if the result is
really compilable?
> However, as "export/examples/ja/multilingual_pdf2" is inverted, this failure
> is expected.
>
> IMV, the lyx2lyx tests now are too complex with reasons for failure including:
> * back conversion errors
> * forward conversion errors
> * non-convergence of the round-trip result
> * compilation errors of the round-trip result
>
> How about splitting the test?
> For a start, would it be possible to generate a separate test
Difficult, because the input from one test is the input of another.
And the intermediate files should be saved somewhere ...
> <document path and base name>_lyx23_defaultoutput
>
> or
>
> <document path and base name>.23_<default output format>
>
> e.g.
>
> export/examples/ja/multilingual.23_pdf2
>
> to check for compilability?
>
> Alternatively, a summary of the reason to fail in the test output might
> also help the bug hunter.
Yes, this is easier to handle.
Will check.
>
> Günter
>
Kornel
signature.asc
Description: This is a digitally signed message part.
