Re: My current test failures

[Scott Kostyshak]

On Wed, Nov 25, 2015 at 01:38:45PM +0100, Kornel Benko wrote:
> Am Mittwoch, 25. November 2015 um 12:24:19, schrieb Guenter Milde 
> 

> > As I don't have all the requirements installed, nor do I want to install
> > them, I want only run selected tests.
> 
> That is only a small part of all tests. To add export tests you have to use
>   'cmake  -DLYX_ENABLE_EXPORT_TESTS=ON'

+1

> If you want also url tests you need to set also -DLYX_ENABLE_URLTESTS=ON

I would say skip the URL tests for now for Günter.

> What do you mean with requirement?
> To run tests you need perl installed, and maybe some perl-modules, that's all.

+1. I think he meant that he soes not want to install non-standard TeX
classes.

Scott


signature.asc
Description: PGP signature

Re: My current test failures

[Kornel Benko]

Am Mittwoch, 25. November 2015 um 11:54:02, schrieb Scott Kostyshak 

> On Wed, Nov 25, 2015 at 01:38:45PM +0100, Kornel Benko wrote:
> > Am Mittwoch, 25. November 2015 um 12:24:19, schrieb Guenter Milde 
> > 
> 
> > > As I don't have all the requirements installed, nor do I want to install
> > > them, I want only run selected tests.
> > 
> > That is only a small part of all tests. To add export tests you have to use
> > 'cmake  -DLYX_ENABLE_EXPORT_TESTS=ON'
> 
> +1
> 
> > If you want also url tests you need to set also -DLYX_ENABLE_URLTESTS=ON
> 
> I would say skip the URL tests for now for Günter.
> 
> > What do you mean with requirement?
> > To run tests you need perl installed, and maybe some perl-modules, that's 
> > all.
> 
> +1. I think he meant that he soes not want to install non-standard TeX
> classes.

OK. To run a test there is no need for such classes. Not all tests need such a 
class.
The test simply fails, so what?

Therefore my conclusion was that he needs something different installed. And I 
would like to know what.

> Scott

Kornel

signature.asc
Description: This is a digitally signed message part.

Re: My current test failures

[Guenter Milde]

On 2015-11-25, Kornel Benko wrote:

>> > > What is the output of the following commands?
>> > 
>> > > cmake . && make && ctest -N
>> > 
>> > After installing cmake, I get:
>> > 
>> > CMake Error: The source directory "/tmp" does not appear to contain 
>> > CMakeLists.txt.
>> > Specify --help for usage, or press the help button on the CMake GUI.

>> What happens when you run that command in LyX's source directory? In
>> LyX's source directory there is a file CMakeLists.txt. That is the file
>> CMake is looking for.

> If you use 'cmake .', that means you have to be at the top of lyx source 
> directory.
> But I strongly discourage such  call.
> I tried to not mess the source directory even in the case one really does use 
> '.', but
> there are always left traces of cmake created files in the source.
> Therefore before using own build directory one would have to clean the source 
> first.

> So select/create a directory you want the build in, chdir to it, and call
>   'cmake '

OK. After this I issued:

ctest -N

and got a lengthy output ending with

...
usr/local/src/lyxbuild/bin/Deployment/check_layout
usr/local/src/lyxbuild/bin/Development/check_layout
usr/local/src/lyxbuild/bin/Development/check_layout
  Test #198: check_layout/varwidth.module
  Test #199: check_ExternalTransforms
  Test #200: check_Length
  Test #201: check_ListingsCaption
  Test #202: lyx2lyx/parser_tools

Total Tests: 202


As I don't have all the requirements installed, nor do I want to install
them, I want only run selected tests.

Günter

Re: My current test failures

[Kornel Benko]

Am Mittwoch, 25. November 2015 um 12:24:19, schrieb Guenter Milde 

> On 2015-11-25, Kornel Benko wrote:
> 
> >> > > What is the output of the following commands?
> >> > 
> >> > > cmake . && make && ctest -N
> >> > 
> >> > After installing cmake, I get:
> >> > 
> >> > CMake Error: The source directory "/tmp" does not appear to contain 
> >> > CMakeLists.txt.
> >> > Specify --help for usage, or press the help button on the CMake GUI.
> 
> >> What happens when you run that command in LyX's source directory? In
> >> LyX's source directory there is a file CMakeLists.txt. That is the file
> >> CMake is looking for.
> 
> > If you use 'cmake .', that means you have to be at the top of lyx source 
> > directory.
> > But I strongly discourage such  call.
> > I tried to not mess the source directory even in the case one really does 
> > use '.', but
> > there are always left traces of cmake created files in the source.
> > Therefore before using own build directory one would have to clean the 
> > source first.
> 
> > So select/create a directory you want the build in, chdir to it, and call
> > 'cmake '
> 
> OK. After this I issued:
> 
> ctest -N
> 
> and got a lengthy output ending with
> 
> ...
> usr/local/src/lyxbuild/bin/Deployment/check_layout
> usr/local/src/lyxbuild/bin/Development/check_layout
> usr/local/src/lyxbuild/bin/Development/check_layout
>   Test #198: check_layout/varwidth.module
>   Test #199: check_ExternalTransforms
>   Test #200: check_Length
>   Test #201: check_ListingsCaption
>   Test #202: lyx2lyx/parser_tools
> 
> Total Tests: 202
> 

This was expected.

> As I don't have all the requirements installed, nor do I want to install
> them, I want only run selected tests.

That is only a small part of all tests. To add export tests you have to use
'cmake  -DLYX_ENABLE_EXPORT_TESTS=ON'
If you want also url tests you need to set also -DLYX_ENABLE_URLTESTS=ON

What do you mean with requirement?
To run tests you need perl installed, and maybe some perl-modules, that's all.

> Günter

Kornel

signature.asc
Description: This is a digitally signed message part.

Re: My current test failures

[Guenter Milde]

On 2015-11-24, Scott Kostyshak wrote:
> On Tue, Nov 24, 2015 at 07:21:41AM +, Guenter Milde wrote:


>> >> > Below are my current (on 77979d91) test failures:
...
>> This exactly was my critique: your list contains both "straight" and
>> "inverted" tests and it is not clear which of them require now our
>> attention.

> I see. Then I will wait to run the tests again until I get the green
> light that the test results are easy to interpret.

Don't wait. I can now interpret the results and having such "suboptimal"
output helps me to think about possible improvement.


...

>> I understand "non standard" in primary sense to mean "requires
>> non-standard ressources (LaTeX packages and document classes, fonts,
>> ... that are not a requirement for running this test suite".

>> In a wider sense, it is currently used for "not to be expected to
>> succeed on every site that runs this test suite".  This wider
>> definition includes tests that have "arbitrary" result depending on
>> local configuration, OS, TeX distribution, package versions, or the
>> phase of the moon.  A more accurate name for this wider definition
>> would be "random_result".

> Makes sense. As Kornel says, it would be great to put this in
> Development.lyx.

I am working on a categorization and naming -- needs some time and discussion.

>> > By the way, Günter, am I correct that you can now run the tests
>> > yourself?

>> No, I can't.

> Do you want to be able to?

> What is the output of the following commands?

> cmake . && make && ctest -N

After installing cmake, I get:

CMake Error: The source directory "/tmp" does not appear to contain 
CMakeLists.txt.
Specify --help for usage, or press the help button on the CMake GUI.


Günter

Re: My current test failures

[Scott Kostyshak]

On Wed, Nov 25, 2015 at 07:11:50AM +, Guenter Milde wrote:
> On 2015-11-24, Scott Kostyshak wrote:

> > I see. Then I will wait to run the tests again until I get the green
> > light that the test results are easy to interpret.
> 
> Don't wait. I can now interpret the results and having such "suboptimal"
> output helps me to think about possible improvement.

OK good to know.

> >> > By the way, Günter, am I correct that you can now run the tests
> >> > yourself?
> 
> >> No, I can't.
> 
> > Do you want to be able to?
> 
> > What is the output of the following commands?
> 
> > cmake . && make && ctest -N
> 
> After installing cmake, I get:
> 
> CMake Error: The source directory "/tmp" does not appear to contain 
> CMakeLists.txt.
> Specify --help for usage, or press the help button on the CMake GUI.

What happens when you run that command in LyX's source directory? In
LyX's source directory there is a file CMakeLists.txt. That is the file
CMake is looking for.

Scott


signature.asc
Description: PGP signature

Re: My current test failures

[Kornel Benko]

Am Mittwoch, 25. November 2015 um 02:28:50, schrieb Scott Kostyshak 

> On Wed, Nov 25, 2015 at 07:11:50AM +, Guenter Milde wrote:
> > On 2015-11-24, Scott Kostyshak wrote:
> 
> > > I see. Then I will wait to run the tests again until I get the green
> > > light that the test results are easy to interpret.
> > 
> > Don't wait. I can now interpret the results and having such "suboptimal"
> > output helps me to think about possible improvement.
> 
> OK good to know.
> 
> > >> > By the way, Günter, am I correct that you can now run the tests
> > >> > yourself?
> > 
> > >> No, I can't.
> > 
> > > Do you want to be able to?
> > 
> > > What is the output of the following commands?
> > 
> > > cmake . && make && ctest -N
> > 
> > After installing cmake, I get:
> > 
> > CMake Error: The source directory "/tmp" does not appear to contain 
> > CMakeLists.txt.
> > Specify --help for usage, or press the help button on the CMake GUI.
> 
> What happens when you run that command in LyX's source directory? In
> LyX's source directory there is a file CMakeLists.txt. That is the file
> CMake is looking for.

If you use 'cmake .', that means you have to be at the top of lyx source 
directory.
But I strongly discourage such  call.
I tried to not mess the source directory even in the case one really does use 
'.', but
there are always left traces of cmake created files in the source.
Therefore before using own build directory one would have to clean the source 
first.

So select/create a directory you want the build in, chdir to it, and call
'cmake '

> Scott

Kornel

signature.asc
Description: This is a digitally signed message part.

Re: My current test failures

[Kornel Benko]

Am Dienstag, 24. November 2015 um 15:48:36, schrieb Guenter Milde 

> On 2015-11-24, Kornel Benko wrote:
> > Am Dienstag, 24. November 2015 um 11:52:19, schrieb Guenter Milde 
> > 
> >> On 2015-11-24, Kornel Benko wrote:
> 
> 
> >> >> I am in the process of devicing a new categorization (or naming for the
> >> >> categories), for what we currently call "nonstandard", I have:
> 
> >> >> + unreliable# export may work or fail (we don't know for sure)
> 
> >> >>   - nonstandard # requires packages or other ressources that are not on 
> >> >> CTAN
> >> >> # (some developers may have them installed)
> 
> >> >>   - erratic # depending on local configuration, OS, TeX 
> >> >> distribution,
> >> >>   # package versions, or the phase of the moon.
> 
> 
> >> > The problem here is that we would need some handling to distinguish the
> >> > cases. ATM it is done by using different files ('*Tests'). The files
> >> > itself contain comments (starting with '#') and regexes. I try to
> >> > implement some sort of sublabels though.
> 
> >> As a start, you could rename "nonstandard" to "unreliable" and
> >> place sublabels just as "header comment", e.g.
> 
> >> file unreliableTests:
> 
> >> # nonstandard
> >> # ===
> 
> > This is not so easy, because at the time of checking I see only lines
> > without comments
> 
> It was just an idea for a stop-gap measure.
> 
> > What about
> > 'Sublabel: nonstandard'
> > ?
> 
> I don't know how you want to implemement it, but if the output contains then
> lines like
> 
>  UNRELIABLE.NON_STANDARD.export/templates/ectaart_dvi3_systemF
>
>  UNRELIABLE.ERRATIC.export/examples/seminar_dvi
> 
> or
> 
>  NON_STANDARD.UNRELIABLE.export/templates/ectaart_dvi3_systemF
> 
>  ERRATIC.UNRELIABLE.export/examples/seminar_dvi
> 
> this is fine.

It is there. Names are
UNRELIABLE.SUBLABEL_export/templates/...
'SUBLABEL' is uppercase of the used sublabel.

Now one can test e.g.
'ctest 'L erratic'
to test only erratic tests defined in unreliableTests.
Unfortunately nothing prevent us ATM using same labels in .*Tests files.

> Günter

Kornel

signature.asc
Description: This is a digitally signed message part.

Re: My current test failures

[Scott Kostyshak]

On Tue, Nov 24, 2015 at 07:21:41AM +, Guenter Milde wrote:
> On 2015-11-24, Scott Kostyshak wrote:
> > On Mon, Nov 23, 2015 at 10:40:11PM +, Guenter Milde wrote:
> >> On 2015-11-21, Scott Kostyshak wrote:
> 
> >> > Below are my current (on 77979d91) test failures:
> 
> >> Thank you for the list. However, I would rather call this a list of
> >> "export failures". 
> 
> >> Only a small subset of them are "test failures":
> >> the others are either
> >> a) passing the test if export fails (inverted), or
> >> b) passing the test in any case or not tested (nonstandard, ignored)
> 
> > I've read this a few times and don't understand. The reason why I don't
> > like the phrase "export failure" is because we don't know if an export
> > failure is expected or not. 
> 
> This exactly was my critique: your list contains both "straight" and
> "inverted" tests and it is not clear which of them require now our attention.

I see. Then I will wait to run the tests again until I get the green
light that the test results are easy to interpret.

> > Once the tests are stable, however, we should expect all tests to
> > pass.
> 
> 
> I understand "non standard" in primary sense to mean "requires
> non-standard ressources (LaTeX packages and document classes, fonts,
> ... that are not a requirement for running this test suite".
> 
> In a wider sense, it is currently used for "not to be expected to
> succeed on every site that runs this test suite".  This wider
> definition includes tests that have "arbitrary" result depending on
> local configuration, OS, TeX distribution, package versions, or the
> phase of the moon.  A more accurate name for this wider definition
> would be "random_result".

Makes sense. As Kornel says, it would be great to put this in
Development.lyx.

> > By the way, Günter, am I correct that you can now run the tests
> > yourself?
> 
> No, I can't.

Do you want to be able to?

What is the output of the following commands?

cmake . && make && ctest -N

Once that works, then you should instead use a separate build directory.

Scott


signature.asc
Description: PGP signature

Re: My current test failures

[Kornel Benko]

Am Dienstag, 24. November 2015 um 07:21:41, schrieb Guenter Milde 

> On 2015-11-24, Scott Kostyshak wrote:
> > On Mon, Nov 23, 2015 at 10:40:11PM +, Guenter Milde wrote:
> >> On 2015-11-21, Scott Kostyshak wrote:

...
 
> >> Here, IEEEtran-Conference.lyx compiles with both, pdflatex and lualatex
> >> while IEEEtran-TransMag.lyx fails with both, due to undefined commands
> >> (version clash?).
> 
> > Good to know. This might have to do with my outdated TL 2015. I'll see
> > if this changes when updating.
> 
> >> > 3900:NON_STANDARD.export/templates/IUCr-article_pdf4_systemF
> 
> >> > 4033:export/templates/ectaart_dvi3_texF
> >> > 4034:export/templates/ectaart_dvi3_systemF
> >> > 4040:export/templates/ectaart_pdf5_texF
> >> > 4041:export/templates/ectaart_pdf5_systemF
> 
> >> Non standard, see http://wiki.lyx.org/Examples/Econometrica

They already are in nonstandard.

> > I still don't understand what NON_STANDARD means (did we define it
> > somewhere in Development.lyx?) but indeed it is not in TeX Live so in
> > that sense I agree.
> 
> I understand "non standard" in primary sense to mean
> "requires non-standard ressources (LaTeX packages and document classes,
> fonts, ... that are not a requirement for running this test suite".
> 
> In a wider sense, it is currently used for "not to be expected to succeed
> on every site that runs this test suite".
>   This wider definition includes tests that have "arbitrary" result depending
> on local configuration, OS, TeX distribution, package versions, or the phase
> of the moon.
>   A more accurate name for this wider definition would be "random_result".

Nice wording. I'd like to add it to Development.lyx

> > By the way, Günter, am I correct that you can now run the tests
> > yourself?
> 
> No, I can't.

That is a pity.

> Günter

Kornel

signature.asc
Description: This is a digitally signed message part.

Re: My current test failures

[Guenter Milde]

On 2015-11-24, Kornel Benko wrote:
> Am Dienstag, 24. November 2015 um 07:21:41, schrieb Guenter Milde 
> 

...

>> >> > 3900:NON_STANDARD.export/templates/IUCr-article_pdf4_systemF

>> >> > 4033:export/templates/ectaart_dvi3_texF
>> >> > 4034:export/templates/ectaart_dvi3_systemF
>> >> > 4040:export/templates/ectaart_pdf5_texF
>> >> > 4041:export/templates/ectaart_pdf5_systemF

>> >> Non standard, see http://wiki.lyx.org/Examples/Econometrica

> They already are in nonstandard.

>> > I still don't understand what NON_STANDARD means
...
> Nice wording. I'd like to add it to Development.lyx

I am in the process of devicing a new categorization (or naming for the
categories), for what we currently call "nonstandard", I have:

  + unreliable# export may work or fail (we don't know for sure)

- nonstandard # requires packages or other ressources that are not on 
CTAN
  # (some developers may have them installed)
  
- erratic # depending on local configuration, OS, TeX distribution,
  # package versions, or the phase of the moon.


Günter

Re: My current test failures

[Guenter Milde]

On 2015-11-24, Kornel Benko wrote:


>> I am in the process of devicing a new categorization (or naming for the
>> categories), for what we currently call "nonstandard", I have:

>>   + unreliable# export may work or fail (we don't know for sure)

>> - nonstandard # requires packages or other ressources that are not 
>> on CTAN
>>   # (some developers may have them installed)

>> - erratic # depending on local configuration, OS, TeX 
>> distribution,
>># package versions, or the phase of the moon.


> The problem here is that we would need some handling to distinguish the
> cases. ATM it is done by using different files ('*Tests'). The files
> itself contain comments (starting with '#') and regexes. I try to
> implement some sort of sublabels though.

As a start, you could rename "nonstandard" to "unreliable" and
place sublabels just as "header comment", e.g.

file unreliableTests:

# nonstandard
# ===
#
# Tests using non-standard tex class or package

export/templates/IUCr-article_(dvi|pdf).*
export/templates/es_beamer-conference-ornate-20min_pdf4_texF
export/templates/kluwer_pdf[45]_systemF
export/examples/modernCV_pdf4_(tex|system)F
export/templates/ectaart_(dvi3|pdf5)_(tex|system)F


# erratic
# ===
#
# Tests depending on local configuration, OS, TeX distribution,
# package versions, or the phase of the moon.

export/examples/(|fr/)seminar_(dvi|pdf|pdf[23]|pdf4_texF|pdf5_systemF)





BTW: I am not sure this belongs to "unreliable":
# 1.) missing farsi package with lfeenc.def
# 2.) LuaTeX does not support Farsi yet. See:
# 
https://github.com/reutenauer/polyglossia/commit/ccb0e9e2c6411170ad779b05ff5076f1193cc323
export/examples/fa/splash_(dvi|pdf|pdf[23]|(dvi3|pdf4|pdf5)_(texF|systemF))

Re: My current test failures

[Kornel Benko]

Am Dienstag, 24. November 2015 um 10:52:55, schrieb Guenter Milde 

> On 2015-11-24, Kornel Benko wrote:
> > Am Dienstag, 24. November 2015 um 07:21:41, schrieb Guenter Milde 
> > 
> 
> ...
> 
> >> >> > 3900:NON_STANDARD.export/templates/IUCr-article_pdf4_systemF
> 
> >> >> > 4033:export/templates/ectaart_dvi3_texF
> >> >> > 4034:export/templates/ectaart_dvi3_systemF
> >> >> > 4040:export/templates/ectaart_pdf5_texF
> >> >> > 4041:export/templates/ectaart_pdf5_systemF
> 
> >> >> Non standard, see http://wiki.lyx.org/Examples/Econometrica
> 
> > They already are in nonstandard.
> 
> >> > I still don't understand what NON_STANDARD means
> ...
> > Nice wording. I'd like to add it to Development.lyx
> 
> I am in the process of devicing a new categorization (or naming for the
> categories), for what we currently call "nonstandard", I have:
> 
>   + unreliable# export may work or fail (we don't know for sure)
> 
> - nonstandard # requires packages or other ressources that are not on 
> CTAN
>   # (some developers may have them installed)
> 
> - erratic # depending on local configuration, OS, TeX 
> distribution,
> # package versions, or the phase of the moon.
> 

The problem here is that we would need some handling to distinguish the cases. 
ATM it is done by
using different files ('*Tests').
The files itself contain comments (starting with '#') and regexes.
I try to implement some sort of sublabels though.

> Günter

Kornel


signature.asc
Description: This is a digitally signed message part.

Re: My current test failures

[Guenter Milde]

On 2015-11-24, Kornel Benko wrote:
> Am Dienstag, 24. November 2015 um 11:52:19, schrieb Guenter Milde 
> 
>> On 2015-11-24, Kornel Benko wrote:


>> >> I am in the process of devicing a new categorization (or naming for the
>> >> categories), for what we currently call "nonstandard", I have:

>> >> + unreliable# export may work or fail (we don't know for sure)

>> >>   - nonstandard # requires packages or other ressources that are not on 
>> >> CTAN
>> >> # (some developers may have them installed)

>> >>   - erratic # depending on local configuration, OS, TeX distribution,
>> >> # package versions, or the phase of the moon.


>> > The problem here is that we would need some handling to distinguish the
>> > cases. ATM it is done by using different files ('*Tests'). The files
>> > itself contain comments (starting with '#') and regexes. I try to
>> > implement some sort of sublabels though.

>> As a start, you could rename "nonstandard" to "unreliable" and
>> place sublabels just as "header comment", e.g.

>> file unreliableTests:

>> # nonstandard
>> # ===

> This is not so easy, because at the time of checking I see only lines
> without comments

It was just an idea for a stop-gap measure.

> What about
>   'Sublabel: nonstandard'
> ?

I don't know how you want to implemement it, but if the output contains then
lines like

 UNRELIABLE.NON_STANDARD.export/templates/ectaart_dvi3_systemF

 UNRELIABLE.ERRATIC.export/examples/seminar_dvi

or

 NON_STANDARD.UNRELIABLE.export/templates/ectaart_dvi3_systemF

 ERRATIC.UNRELIABLE.export/examples/seminar_dvi

this is fine.

Günter

Re: My current test failures

[Kornel Benko]

Am Dienstag, 24. November 2015 um 11:52:19, schrieb Guenter Milde 

> On 2015-11-24, Kornel Benko wrote:
> 
> 
> >> I am in the process of devicing a new categorization (or naming for the
> >> categories), for what we currently call "nonstandard", I have:
> 
> >>   + unreliable# export may work or fail (we don't know for sure)
> 
> >> - nonstandard # requires packages or other ressources that are not 
> >> on CTAN
> >>   # (some developers may have them installed)
> 
> >> - erratic # depending on local configuration, OS, TeX 
> >> distribution,
> >>  # package versions, or the phase of the moon.
> 
> 
> > The problem here is that we would need some handling to distinguish the
> > cases. ATM it is done by using different files ('*Tests'). The files
> > itself contain comments (starting with '#') and regexes. I try to
> > implement some sort of sublabels though.
> 
> As a start, you could rename "nonstandard" to "unreliable" and
> place sublabels just as "header comment", e.g.
> 
> file unreliableTests:
> 
> # nonstandard
> # ===

This is not so easy, because at the time of checking I see only lines without 
comments
What about
'Sublabel: nonstandard'
?

> # Tests using non-standard tex class or package
> 
> export/templates/IUCr-article_(dvi|pdf).*
> export/templates/es_beamer-conference-ornate-20min_pdf4_texF
> export/templates/kluwer_pdf[45]_systemF
> export/examples/modernCV_pdf4_(tex|system)F
> export/templates/ectaart_(dvi3|pdf5)_(tex|system)F
> 
> 
> # erratic
> # ===
> #
> # Tests depending on local configuration, OS, TeX distribution,
> # package versions, or the phase of the moon.
> 
> export/examples/(|fr/)seminar_(dvi|pdf|pdf[23]|pdf4_texF|pdf5_systemF)
> 
> 
> 
> 
> 
> BTW: I am not sure this belongs to "unreliable":
> # 1.) missing farsi package with lfeenc.def
> # 2.) LuaTeX does not support Farsi yet. See:
> # 
> https://github.com/reutenauer/polyglossia/commit/ccb0e9e2c6411170ad779b05ff5076f1193cc323
> export/examples/fa/splash_(dvi|pdf|pdf[23]|(dvi3|pdf4|pdf5)_(texF|systemF))

This is a TODO then.

Kornel

signature.asc
Description: This is a digitally signed message part.

Re: My current test failures

[Guenter Milde]

On 2015-11-21, Scott Kostyshak wrote:
>
> [-- Type: text/plain, Encoding:  --]
>
> Below are my current (on 77979d91) test failures:

Newsgroups: gmane.editors.lyx.devel
From: Guenter Milde <mi...@users.sf.net>
Subject: Re: My current test failures
References: <20151121160534.GA2808@cotopaxi>
Followup-To: 

On 2015-11-21, Scott Kostyshak wrote:

Dear Scott,

> Below are my current (on 77979d91) test failures:

Thank you for the list. However, I would rather call this a list of
"export failures". 

Only a small subset of them are "test failures":
the others are either
a) passing the test if export fails (inverted), or
b) passing the test in any case or not tested (nonstandard, ignored)

>
> 362:lyx2lyx/doc/Tutorial
> 690:INVERTED_SEE-README.ctest_export/doc/es/Additional_dvi3_texF
> 697:INVERTED_SEE-README.ctest_export/doc/es/Additional_pdf5_texF
> 703:INVERTED_SEE-README.ctest_export/doc/es/Customization_dvi3_texF
> 708:INVERTED_SEE-README.ctest_export/doc/es/Customization_pdf4_texF
> 710:INVERTED_SEE-README.ctest_export/doc/es/Customization_pdf5_texF
> 716:INVERTED_SEE-README.ctest_export/doc/es/DocumentoPostizo1_dvi3_texF
> 721:INVERTED_SEE-README.ctest_export/doc/es/DocumentoPostizo1_pdf4_texF
> 723:INVERTED_SEE-README.ctest_export/doc/es/DocumentoPostizo1_pdf5_texF
> 729:INVERTED_SEE-README.ctest_export/doc/es/DocumentoPostizo2_dvi3_texF
> 734:INVERTED_SEE-README.ctest_export/doc/es/DocumentoPostizo2_pdf4_texF
> 736:INVERTED_SEE-README.ctest_export/doc/es/DocumentoPostizo2_pdf5_texF
> 755:INVERTED_SEE-README.ctest_export/doc/es/Formula-numbering_dvi3_texF
> 760:INVERTED_SEE-README.ctest_export/doc/es/Formula-numbering_pdf4_texF
> 762:INVERTED_SEE-README.ctest_export/doc/es/Formula-numbering_pdf5_texF
> 768:INVERTED_SEE-README.ctest_export/doc/es/Intro_dvi3_texF
> 773:INVERTED_SEE-README.ctest_export/doc/es/Intro_pdf4_texF
> 775:INVERTED_SEE-README.ctest_export/doc/es/Intro_pdf5_texF
> 786:INVERTED_SEE-README.ctest_export/doc/es/Math_pdf4_texF
> 794:INVERTED_SEE-README.ctest_export/doc/es/Shortcuts_dvi3_texF
> 799:INVERTED_SEE-README.ctest_export/doc/es/Shortcuts_pdf4_texF
> 801:INVERTED_SEE-README.ctest_export/doc/es/Shortcuts_pdf5_texF
> 807:INVERTED_SEE-README.ctest_export/doc/es/Tutorial_dvi3_texF
> 812:INVERTED_SEE-README.ctest_export/doc/es/Tutorial_pdf4_texF
> 814:INVERTED_SEE-README.ctest_export/doc/es/Tutorial_pdf5_texF
> 856:lyx2lyx/doc/fr/Additional
> 1949:INVERTED_SEE-README.ctest_export/examples/modernCV_pdf4_texF
> 1950:INVERTED_SEE-README.ctest_export/examples/modernCV_pdf4_systemF
> 1969:INVERTED_SEE-README.ctest_export/examples/powerdot-example_pdf
> 2005:NON_STANDARD.export/examples/seminar_pdf
> 2006:NON_STANDARD.export/examples/seminar_pdf2
> 2007:NON_STANDARD.export/examples/seminar_pdf3
> 2008:NON_STANDARD.export/examples/seminar_pdf4_texF
> 2010:INVERTED_SEE-README.ctest_export/examples/seminar_pdf5_texF
> 2855:INVERTED_SEE-README.ctest_export/examples/es/Braille_dvi3_texF
> 2862:INVERTED_SEE-README.ctest_export/examples/es/Braille_pdf5_texF
> 2868:INVERTED_SEE-README.ctest_export/examples/es/ItemizeBullets_dvi3_texF
> 2875:INVERTED_SEE-README.ctest_export/examples/es/ItemizeBullets_pdf5_texF
> 2881:INVERTED_SEE-README.ctest_export/examples/es/ejemplo_con_lyx_dvi3_texF
> 2888:INVERTED_SEE-README.ctest_export/examples/es/ejemplo_con_lyx_pdf5_texF
> 2894:INVERTED_SEE-README.ctest_export/examples/es/ejemplo_sin_lyx_dvi3_texF
> 2901:INVERTED_SEE-README.ctest_export/examples/es/ejemplo_sin_lyx_pdf5_texF
> 2920:INVERTED_SEE-README.ctest_export/examples/es/linguistics_dvi3_texF
> 2927:INVERTED_SEE-README.ctest_export/examples/es/linguistics_pdf5_texF
> 2946:INVERTED_SEE-README.ctest_export/examples/es/splash_dvi3_texF
> 2953:INVERTED_SEE-README.ctest_export/examples/es/splash_pdf5_texF
> 3005:NON_STANDARD.export/examples/fa/splash_dvi
> 3006:NON_STANDARD.export/examples/fa/splash_dvi3_texF
> 3007:NON_STANDARD.export/examples/fa/splash_dvi3_systemF
> 3008:NON_STANDARD.export/examples/fa/splash_pdf
> 3009:NON_STANDARD.export/examples/fa/splash_pdf2
> 3010:NON_STANDARD.export/examples/fa/splash_pdf3
> 3011:NON_STANDARD.export/examples/fa/splash_pdf4_texF
> 3012:NON_STANDARD.export/examples/fa/splash_pdf4_systemF
> 3013:NON_STANDARD.export/examples/fa/splash_pdf5_texF
> 3014:NON_STANDARD.export/examples/fa/splash_pdf5_systemF
> 3109:INVERTED_SEE-README.ctest_export/examples/fr/exemple-powerdot_pdf
> 3158:NON_STANDARD.export/examples/fr/seminar_dvi
> 3161:NON_STANDARD.export/examples/fr/seminar_pdf
> 3162:NON_STANDARD.export/examples/fr/seminar_pdf2
> 3163:NON_STANDARD.export/examples/fr/seminar_pdf3
> 3164:NON_STANDARD.export/examples/fr/seminar_pdf4_texF
> 3166:INVERTED_SEE-README.ctest_export/examples/fr/seminar_pdf5_texF
> 3284:INVERTED_SEE-REA

Re: My current test failures

[Scott Kostyshak]

On Mon, Nov 23, 2015 at 10:40:11PM +, Guenter Milde wrote:
> On 2015-11-21, Scott Kostyshak wrote:
> >
> > [-- Type: text/plain, Encoding:  --]
> >
> > Below are my current (on 77979d91) test failures:
> 
> Newsgroups: gmane.editors.lyx.devel
> From: Guenter Milde <mi...@users.sf.net>
> Subject: Re: My current test failures
> References: <20151121160534.GA2808@cotopaxi>
> Followup-To: 
> 
> On 2015-11-21, Scott Kostyshak wrote:
> 
> Dear Scott,
> 
> > Below are my current (on 77979d91) test failures:
> 
> Thank you for the list. However, I would rather call this a list of
> "export failures". 
> 
> Only a small subset of them are "test failures":
> the others are either
> a) passing the test if export fails (inverted), or
> b) passing the test in any case or not tested (nonstandard, ignored)

I've read this a few times and don't understand. The reason why I don't
like the phrase "export failure" is because we don't know if an export
failure is expected or not. Once the tests are stable, however, we
should expect all tests to pass.

> 
> Strange.
> 
> Here, IEEEtran-Conference.lyx compiles with both, pdflatex and lualatex
> while IEEEtran-TransMag.lyx fails with both, due to undefined commands
> (version clash?).

Good to know. This might have to do with my outdated TL 2015. I'll see
if this changes when updating.

> > 3900:NON_STANDARD.export/templates/IUCr-article_pdf4_systemF
> 
> > 4033:export/templates/ectaart_dvi3_texF
> > 4034:export/templates/ectaart_dvi3_systemF
> > 4040:export/templates/ectaart_pdf5_texF
> > 4041:export/templates/ectaart_pdf5_systemF
> 
> Non standard, see http://wiki.lyx.org/Examples/Econometrica

I still don't understand what NON_STANDARD means (did we define it
somewhere in Development.lyx?) but indeed it is not in TeX Live so in
that sense I agree.

By the way, Günter, am I correct that you can now run the tests
yourself? Or are all of your results from manual testing?

Scott


signature.asc
Description: PGP signature

Re: My current test failures

[Guenter Milde]

On 2015-11-24, Scott Kostyshak wrote:
> On Mon, Nov 23, 2015 at 10:40:11PM +, Guenter Milde wrote:
>> On 2015-11-21, Scott Kostyshak wrote:

>> > Below are my current (on 77979d91) test failures:

>> Thank you for the list. However, I would rather call this a list of
>> "export failures". 

>> Only a small subset of them are "test failures":
>> the others are either
>> a) passing the test if export fails (inverted), or
>> b) passing the test in any case or not tested (nonstandard, ignored)

> I've read this a few times and don't understand. The reason why I don't
> like the phrase "export failure" is because we don't know if an export
> failure is expected or not. 

This exactly was my critique: your list contains both "straight" and
"inverted" tests and it is not clear which of them require now our attention.

> Once the tests are stable, however, we
> should expect all tests to pass.

There were many test lines in the list (everything inverted and
non-standard), where I would call the test suite "stable" regardless of
the outcome of this special test cases.

>> Strange.

>> Here, IEEEtran-Conference.lyx compiles with both, pdflatex and lualatex
>> while IEEEtran-TransMag.lyx fails with both, due to undefined commands
>> (version clash?).

> Good to know. This might have to do with my outdated TL 2015. I'll see
> if this changes when updating.

>> > 3900:NON_STANDARD.export/templates/IUCr-article_pdf4_systemF

>> > 4033:export/templates/ectaart_dvi3_texF
>> > 4034:export/templates/ectaart_dvi3_systemF
>> > 4040:export/templates/ectaart_pdf5_texF
>> > 4041:export/templates/ectaart_pdf5_systemF

>> Non standard, see http://wiki.lyx.org/Examples/Econometrica

> I still don't understand what NON_STANDARD means (did we define it
> somewhere in Development.lyx?) but indeed it is not in TeX Live so in
> that sense I agree.

I understand "non standard" in primary sense to mean
"requires non-standard ressources (LaTeX packages and document classes,
fonts, ... that are not a requirement for running this test suite".

In a wider sense, it is currently used for "not to be expected to succeed
on every site that runs this test suite".
  This wider definition includes tests that have "arbitrary" result depending
on local configuration, OS, TeX distribution, package versions, or the phase
of the moon.
  A more accurate name for this wider definition would be "random_result".
  
> By the way, Günter, am I correct that you can now run the tests
> yourself?

No, I can't.

Günter

Re: My current test failures

[Scott Kostyshak]

On Sun, Nov 22, 2015 at 10:34:51PM +, Guenter Milde wrote:
> On 2015-11-22, Kornel Benko wrote:
> > Am 22. November 2015 um 13:00:20, schrieb Guenter Milde 
> >> On 2015-11-21, Kornel Benko wrote:
> 
> >> > So my fix is obsolete?
> 
> >> I don't know how you fixed it, but I think so (this can be fixed in the
> >> document, it hat nothing to do with math fonts).
> 
> > I fixed it in document. Committed. Pushed. And then I had a 30 minutes
> > pleasure with git. Could not push, because my head was one behind,
> > merging not successful, please resolve conflicts first, and so on.
> 
> Sorry for this. I know it is annoying - had similar problems several times
> (and spent more than 30 minutes cleaning up) until I learned to pull from git
> every time before starting a LyX-coding session...

+1

In particular, 'git pull --rebase' and if there is a problem during
rebasing, it is possible someone is working on similar code.

Scott


signature.asc
Description: PGP signature

Re: My current test failures

[Guenter Milde]

On 2015-11-22, Kornel Benko wrote:
> Am 22. November 2015 um 13:00:20, schrieb Guenter Milde 
>> On 2015-11-21, Kornel Benko wrote:

>> > So my fix is obsolete?

>> I don't know how you fixed it, but I think so (this can be fixed in the
>> document, it hat nothing to do with math fonts).

> I fixed it in document. Committed. Pushed. And then I had a 30 minutes
> pleasure with git. Could not push, because my head was one behind,
> merging not successful, please resolve conflicts first, and so on.

Sorry for this. I know it is annoying - had similar problems several times
(and spent more than 30 minutes cleaning up) until I learned to pull from git
every time before starting a LyX-coding session...

Günter

Re: My current test failures

[Kornel Benko]

Am Sonntag, 22. November 2015 um 13:00:20, schrieb Guenter Milde 

> On 2015-11-21, Kornel Benko wrote:
> 
> > [-- Type: text/plain, Encoding: quoted-printable --]
> 
> > Am Samstag, 21. November 2015 um 22:10:24, schrieb Guenter Milde 
> > 
> >> On 2015-11-21, Scott Kostyshak wrote:
> 
> >> > [-- Type: text/plain, Encoding: quoted-printable --]
> 
> >> > On Sat, Nov 21, 2015 at 03:29:09PM -0500, Scott Kostyshak wrote:
> 
> >> >> > 4.) export/templates/IEEEtran-Conference_dvi3_*F: The last changer 
> >> >> > was Scott, now it does not compile here too.
> 
> >> >> I will take a look.
> 
> >> > I just updated the format. This did not change anything. The document
> >> > fails to compile because of "String contains an invalid utf-8 sequence"
> >> > and "Missing glyphs!".
> 
> >> Missing inputenc package!
> 
> >> After fixing this (8482b2169bf9c/lyxgit), the document compiles also with
> >> LuaTeX to DVI.
> 
> > So my fix is obsolete?
> 
> I don't know how you fixed it, but I think so (this can be fixed in the
> document, it hat nothing to do with math fonts).

I fixed it in document. Committed. Pushed. And then I had a 30 minutes pleasure 
with
git.
Could not push, because my head was one behind, merging not successful, please 
resolve conflicts first, and so on.

> Günter

Kornel

signature.asc
Description: This is a digitally signed message part.

Re: My current test failures

[Guenter Milde]

On 2015-11-21, Kornel Benko wrote:

> [-- Type: text/plain, Encoding: quoted-printable --]

> Am Samstag, 21. November 2015 um 22:10:24, schrieb Guenter Milde 
> 
>> On 2015-11-21, Scott Kostyshak wrote:

>> > [-- Type: text/plain, Encoding: quoted-printable --]

>> > On Sat, Nov 21, 2015 at 03:29:09PM -0500, Scott Kostyshak wrote:

>> >> > 4.) export/templates/IEEEtran-Conference_dvi3_*F: The last changer was 
>> >> > Scott, now it does not compile here too.

>> >> I will take a look.

>> > I just updated the format. This did not change anything. The document
>> > fails to compile because of "String contains an invalid utf-8 sequence"
>> > and "Missing glyphs!".

>> Missing inputenc package!

>> After fixing this (8482b2169bf9c/lyxgit), the document compiles also with
>> LuaTeX to DVI.

> So my fix is obsolete?

I don't know how you fixed it, but I think so (this can be fixed in the
document, it hat nothing to do with math fonts).

Günter

Re: My current test failures

[Scott Kostyshak]

On Sat, Nov 21, 2015 at 06:23:37PM +0100, Kornel Benko wrote:
> Am Samstag, 21. November 2015 um 11:05:34, schrieb Scott Kostyshak 
> 
> > Below are my current (on 77979d91) test failures:
> > 
> > 362:lyx2lyx/doc/Tutorial
> > 690:INVERTED_SEE-README.ctest_export/doc/es/Additional_dvi3_texF
> > 697:INVERTED_SEE-README.ctest_export/doc/es/Additional_pdf5_texF
> > 703:INVERTED_SEE-README.ctest_export/doc/es/Customization_dvi3_texF
> > 708:INVERTED_SEE-README.ctest_export/doc/es/Customization_pdf4_texF
> > 710:INVERTED_SEE-README.ctest_export/doc/es/Customization_pdf5_texF
> > 716:INVERTED_SEE-README.ctest_export/doc/es/DocumentoPostizo1_dvi3_texF
> > 721:INVERTED_SEE-README.ctest_export/doc/es/DocumentoPostizo1_pdf4_texF
> > 723:INVERTED_SEE-README.ctest_export/doc/es/DocumentoPostizo1_pdf5_texF
> > 729:INVERTED_SEE-README.ctest_export/doc/es/DocumentoPostizo2_dvi3_texF
> > 734:INVERTED_SEE-README.ctest_export/doc/es/DocumentoPostizo2_pdf4_texF
> > 736:INVERTED_SEE-README.ctest_export/doc/es/DocumentoPostizo2_pdf5_texF
> > 755:INVERTED_SEE-README.ctest_export/doc/es/Formula-numbering_dvi3_texF
> > 760:INVERTED_SEE-README.ctest_export/doc/es/Formula-numbering_pdf4_texF
> > 762:INVERTED_SEE-README.ctest_export/doc/es/Formula-numbering_pdf5_texF
> > 768:INVERTED_SEE-README.ctest_export/doc/es/Intro_dvi3_texF
> > 773:INVERTED_SEE-README.ctest_export/doc/es/Intro_pdf4_texF
> > 775:INVERTED_SEE-README.ctest_export/doc/es/Intro_pdf5_texF
> > 786:INVERTED_SEE-README.ctest_export/doc/es/Math_pdf4_texF
> > 794:INVERTED_SEE-README.ctest_export/doc/es/Shortcuts_dvi3_texF
> > 799:INVERTED_SEE-README.ctest_export/doc/es/Shortcuts_pdf4_texF
> > 801:INVERTED_SEE-README.ctest_export/doc/es/Shortcuts_pdf5_texF
> > 807:INVERTED_SEE-README.ctest_export/doc/es/Tutorial_dvi3_texF
> > 812:INVERTED_SEE-README.ctest_export/doc/es/Tutorial_pdf4_texF
> > 814:INVERTED_SEE-README.ctest_export/doc/es/Tutorial_pdf5_texF
> > 856:lyx2lyx/doc/fr/Additional
> > 1949:INVERTED_SEE-README.ctest_export/examples/modernCV_pdf4_texF
> > 1950:INVERTED_SEE-README.ctest_export/examples/modernCV_pdf4_systemF
> > 1969:INVERTED_SEE-README.ctest_export/examples/powerdot-example_pdf
> > 2005:NON_STANDARD.export/examples/seminar_pdf
> > 2006:NON_STANDARD.export/examples/seminar_pdf2
> > 2007:NON_STANDARD.export/examples/seminar_pdf3
> > 2008:NON_STANDARD.export/examples/seminar_pdf4_texF
> > 2010:INVERTED_SEE-README.ctest_export/examples/seminar_pdf5_texF
> > 2855:INVERTED_SEE-README.ctest_export/examples/es/Braille_dvi3_texF
> > 2862:INVERTED_SEE-README.ctest_export/examples/es/Braille_pdf5_texF
> > 2868:INVERTED_SEE-README.ctest_export/examples/es/ItemizeBullets_dvi3_texF
> > 2875:INVERTED_SEE-README.ctest_export/examples/es/ItemizeBullets_pdf5_texF
> > 2881:INVERTED_SEE-README.ctest_export/examples/es/ejemplo_con_lyx_dvi3_texF
> > 2888:INVERTED_SEE-README.ctest_export/examples/es/ejemplo_con_lyx_pdf5_texF
> > 2894:INVERTED_SEE-README.ctest_export/examples/es/ejemplo_sin_lyx_dvi3_texF
> > 2901:INVERTED_SEE-README.ctest_export/examples/es/ejemplo_sin_lyx_pdf5_texF
> > 2920:INVERTED_SEE-README.ctest_export/examples/es/linguistics_dvi3_texF
> > 2927:INVERTED_SEE-README.ctest_export/examples/es/linguistics_pdf5_texF
> > 2946:INVERTED_SEE-README.ctest_export/examples/es/splash_dvi3_texF
> > 2953:INVERTED_SEE-README.ctest_export/examples/es/splash_pdf5_texF
> > 3005:NON_STANDARD.export/examples/fa/splash_dvi
> > 3006:NON_STANDARD.export/examples/fa/splash_dvi3_texF
> > 3007:NON_STANDARD.export/examples/fa/splash_dvi3_systemF
> > 3008:NON_STANDARD.export/examples/fa/splash_pdf
> > 3009:NON_STANDARD.export/examples/fa/splash_pdf2
> > 3010:NON_STANDARD.export/examples/fa/splash_pdf3
> > 3011:NON_STANDARD.export/examples/fa/splash_pdf4_texF
> > 3012:NON_STANDARD.export/examples/fa/splash_pdf4_systemF
> > 3013:NON_STANDARD.export/examples/fa/splash_pdf5_texF
> > 3014:NON_STANDARD.export/examples/fa/splash_pdf5_systemF
> > 3109:INVERTED_SEE-README.ctest_export/examples/fr/exemple-powerdot_pdf
> > 3158:NON_STANDARD.export/examples/fr/seminar_dvi
> > 3161:NON_STANDARD.export/examples/fr/seminar_pdf
> > 3162:NON_STANDARD.export/examples/fr/seminar_pdf2
> > 3163:NON_STANDARD.export/examples/fr/seminar_pdf3
> > 3164:NON_STANDARD.export/examples/fr/seminar_pdf4_texF
> > 3166:INVERTED_SEE-README.ctest_export/examples/fr/seminar_pdf5_texF
> > 3284:INVERTED_SEE-README.ctest_export/examples/he/splash_pdf5_systemF
> > 3816:export/templates/IEEEtran-Conference_dvi3_texF
> > 3823:export/templates/IEEEtran-Conference_pdf5_texF
> > 3842:export/templates/IEEEtran-TransMag_dvi3_texF
> > 3849:export/templates/IEEEtran-TransMag_pdf5_texF
> > 3900:NON_STANDARD.export/templates/IUCr-article_pdf4_systemF
> > 4033:export/templates/ectaart_dvi3_texF
> > 4034:export/templates/ectaart_dvi3_systemF
> > 4040:export/templates/ectaart_pdf5_texF
> > 4041:export/templates/ectaart_pdf5_systemF
> > 4064:NON_STANDARD.export/templates/es_beamer-conference-ornate-20min_pdf4_texF
> > 

Re: My current test failures

[Kornel Benko]

Am Samstag, 21. November 2015 um 11:05:34, schrieb Scott Kostyshak 

> Below are my current (on 77979d91) test failures:
> 
> 362:lyx2lyx/doc/Tutorial
> 690:INVERTED_SEE-README.ctest_export/doc/es/Additional_dvi3_texF
> 697:INVERTED_SEE-README.ctest_export/doc/es/Additional_pdf5_texF
> 703:INVERTED_SEE-README.ctest_export/doc/es/Customization_dvi3_texF
> 708:INVERTED_SEE-README.ctest_export/doc/es/Customization_pdf4_texF
> 710:INVERTED_SEE-README.ctest_export/doc/es/Customization_pdf5_texF
> 716:INVERTED_SEE-README.ctest_export/doc/es/DocumentoPostizo1_dvi3_texF
> 721:INVERTED_SEE-README.ctest_export/doc/es/DocumentoPostizo1_pdf4_texF
> 723:INVERTED_SEE-README.ctest_export/doc/es/DocumentoPostizo1_pdf5_texF
> 729:INVERTED_SEE-README.ctest_export/doc/es/DocumentoPostizo2_dvi3_texF
> 734:INVERTED_SEE-README.ctest_export/doc/es/DocumentoPostizo2_pdf4_texF
> 736:INVERTED_SEE-README.ctest_export/doc/es/DocumentoPostizo2_pdf5_texF
> 755:INVERTED_SEE-README.ctest_export/doc/es/Formula-numbering_dvi3_texF
> 760:INVERTED_SEE-README.ctest_export/doc/es/Formula-numbering_pdf4_texF
> 762:INVERTED_SEE-README.ctest_export/doc/es/Formula-numbering_pdf5_texF
> 768:INVERTED_SEE-README.ctest_export/doc/es/Intro_dvi3_texF
> 773:INVERTED_SEE-README.ctest_export/doc/es/Intro_pdf4_texF
> 775:INVERTED_SEE-README.ctest_export/doc/es/Intro_pdf5_texF
> 786:INVERTED_SEE-README.ctest_export/doc/es/Math_pdf4_texF
> 794:INVERTED_SEE-README.ctest_export/doc/es/Shortcuts_dvi3_texF
> 799:INVERTED_SEE-README.ctest_export/doc/es/Shortcuts_pdf4_texF
> 801:INVERTED_SEE-README.ctest_export/doc/es/Shortcuts_pdf5_texF
> 807:INVERTED_SEE-README.ctest_export/doc/es/Tutorial_dvi3_texF
> 812:INVERTED_SEE-README.ctest_export/doc/es/Tutorial_pdf4_texF
> 814:INVERTED_SEE-README.ctest_export/doc/es/Tutorial_pdf5_texF
> 856:lyx2lyx/doc/fr/Additional
> 1949:INVERTED_SEE-README.ctest_export/examples/modernCV_pdf4_texF
> 1950:INVERTED_SEE-README.ctest_export/examples/modernCV_pdf4_systemF
> 1969:INVERTED_SEE-README.ctest_export/examples/powerdot-example_pdf
> 2005:NON_STANDARD.export/examples/seminar_pdf
> 2006:NON_STANDARD.export/examples/seminar_pdf2
> 2007:NON_STANDARD.export/examples/seminar_pdf3
> 2008:NON_STANDARD.export/examples/seminar_pdf4_texF
> 2010:INVERTED_SEE-README.ctest_export/examples/seminar_pdf5_texF
> 2855:INVERTED_SEE-README.ctest_export/examples/es/Braille_dvi3_texF
> 2862:INVERTED_SEE-README.ctest_export/examples/es/Braille_pdf5_texF
> 2868:INVERTED_SEE-README.ctest_export/examples/es/ItemizeBullets_dvi3_texF
> 2875:INVERTED_SEE-README.ctest_export/examples/es/ItemizeBullets_pdf5_texF
> 2881:INVERTED_SEE-README.ctest_export/examples/es/ejemplo_con_lyx_dvi3_texF
> 2888:INVERTED_SEE-README.ctest_export/examples/es/ejemplo_con_lyx_pdf5_texF
> 2894:INVERTED_SEE-README.ctest_export/examples/es/ejemplo_sin_lyx_dvi3_texF
> 2901:INVERTED_SEE-README.ctest_export/examples/es/ejemplo_sin_lyx_pdf5_texF
> 2920:INVERTED_SEE-README.ctest_export/examples/es/linguistics_dvi3_texF
> 2927:INVERTED_SEE-README.ctest_export/examples/es/linguistics_pdf5_texF
> 2946:INVERTED_SEE-README.ctest_export/examples/es/splash_dvi3_texF
> 2953:INVERTED_SEE-README.ctest_export/examples/es/splash_pdf5_texF
> 3005:NON_STANDARD.export/examples/fa/splash_dvi
> 3006:NON_STANDARD.export/examples/fa/splash_dvi3_texF
> 3007:NON_STANDARD.export/examples/fa/splash_dvi3_systemF
> 3008:NON_STANDARD.export/examples/fa/splash_pdf
> 3009:NON_STANDARD.export/examples/fa/splash_pdf2
> 3010:NON_STANDARD.export/examples/fa/splash_pdf3
> 3011:NON_STANDARD.export/examples/fa/splash_pdf4_texF
> 3012:NON_STANDARD.export/examples/fa/splash_pdf4_systemF
> 3013:NON_STANDARD.export/examples/fa/splash_pdf5_texF
> 3014:NON_STANDARD.export/examples/fa/splash_pdf5_systemF
> 3109:INVERTED_SEE-README.ctest_export/examples/fr/exemple-powerdot_pdf
> 3158:NON_STANDARD.export/examples/fr/seminar_dvi
> 3161:NON_STANDARD.export/examples/fr/seminar_pdf
> 3162:NON_STANDARD.export/examples/fr/seminar_pdf2
> 3163:NON_STANDARD.export/examples/fr/seminar_pdf3
> 3164:NON_STANDARD.export/examples/fr/seminar_pdf4_texF
> 3166:INVERTED_SEE-README.ctest_export/examples/fr/seminar_pdf5_texF
> 3284:INVERTED_SEE-README.ctest_export/examples/he/splash_pdf5_systemF
> 3816:export/templates/IEEEtran-Conference_dvi3_texF
> 3823:export/templates/IEEEtran-Conference_pdf5_texF
> 3842:export/templates/IEEEtran-TransMag_dvi3_texF
> 3849:export/templates/IEEEtran-TransMag_pdf5_texF
> 3900:NON_STANDARD.export/templates/IUCr-article_pdf4_systemF
> 4033:export/templates/ectaart_dvi3_texF
> 4034:export/templates/ectaart_dvi3_systemF
> 4040:export/templates/ectaart_pdf5_texF
> 4041:export/templates/ectaart_pdf5_systemF
> 4064:NON_STANDARD.export/templates/es_beamer-conference-ornate-20min_pdf4_texF
> 4166:NON_STANDARD.export/templates/kluwer_pdf4_systemF
> 4168:NON_STANDARD.export/templates/kluwer_pdf5_systemF
> 4312:check_accessible_urls
> 4315:check_translators
> 

1.) Many suspended test are now compilable.
2.) urls 

Re: My current test failures

[Kornel Benko]

Am Samstag, 21. November 2015 um 12:27:18, schrieb Scott Kostyshak 

> On Sat, Nov 21, 2015 at 06:23:37PM +0100, Kornel Benko wrote:
> > Am Samstag, 21. November 2015 um 11:05:34, schrieb Scott Kostyshak 
> > 
> > > Below are my current (on 77979d91) test failures:
> > > 

...

> > 
> > 1.) Many suspended test are now compilable.
> > 2.) urls test belong to nonstandard I think. Here they would pass.
> > 
> > I am in the process of cleaning the now working suspended tests.
> 
> OK let me know when it would be a good time to run all the tests so we
> can compare our results.

1.) Ignore everything marked NON_STANDARD
2.) /es/ should be OK now.
3.) Inverted ctest_export/examples/modernCV_pdf4 passes here, moving to 
nonstandard
4.) export/templates/IEEEtran-Conference_dvi3_*F: The last changer was Scott, 
now it does not compile here too.
5.) export/templates/ectaart.* compiles here, moving to nonstandard

Not sure, what to do with check_.*_urls

Committed at 98746f3

> Scott

Kornel

signature.asc
Description: This is a digitally signed message part.

Re: My current test failures

[Scott Kostyshak]

On Sat, Nov 21, 2015 at 07:41:13PM +0100, Kornel Benko wrote:
> Am Samstag, 21. November 2015 um 12:27:18, schrieb Scott Kostyshak 
> 
> > On Sat, Nov 21, 2015 at 06:23:37PM +0100, Kornel Benko wrote:
> > > Am Samstag, 21. November 2015 um 11:05:34, schrieb Scott Kostyshak 
> > > 
> > > > Below are my current (on 77979d91) test failures:
> > > > 
> 
> ...
> 
> > > 
> > > 1.) Many suspended test are now compilable.
> > > 2.) urls test belong to nonstandard I think. Here they would pass.
> > > 
> > > I am in the process of cleaning the now working suspended tests.
> > 
> > OK let me know when it would be a good time to run all the tests so we
> > can compare our results.
> 
> 1.) Ignore everything marked NON_STANDARD

OK

> 2.) /es/ should be OK now.
> 3.) Inverted ctest_export/examples/modernCV_pdf4 passes here, moving to 
> nonstandard

OK, could also be due to different versions.

> 4.) export/templates/IEEEtran-Conference_dvi3_*F: The last changer was Scott, 
> now it does not compile here too.

I will take a look.

> 5.) export/templates/ectaart.* compiles here, moving to nonstandard
> 
> Not sure, what to do with check_.*_urls

Me neither. Since they are not enabled by default, I guess it does not
matter too much.

Scott


signature.asc
Description: PGP signature

Re: My current test failures

[Scott Kostyshak]

On Sat, Nov 21, 2015 at 03:29:09PM -0500, Scott Kostyshak wrote:

> > 4.) export/templates/IEEEtran-Conference_dvi3_*F: The last changer was 
> > Scott, now it does not compile here too.
> 
> I will take a look.

I just updated the format. This did not change anything. The document
fails to compile because of "String contains an invalid utf-8 sequence"
and "Missing glyphs!".

Scott


signature.asc
Description: PGP signature

Re: My current test failures

[Guenter Milde]

On 2015-11-21, Scott Kostyshak wrote:

> [-- Type: text/plain, Encoding: quoted-printable --]

> On Sat, Nov 21, 2015 at 03:29:09PM -0500, Scott Kostyshak wrote:

>> > 4.) export/templates/IEEEtran-Conference_dvi3_*F: The last changer was 
>> > Scott, now it does not compile here too.

>> I will take a look.

> I just updated the format. This did not change anything. The document
> fails to compile because of "String contains an invalid utf-8 sequence"
> and "Missing glyphs!".

Missing inputenc package!

After fixing this (8482b2169bf9c/lyxgit), the document compiles also with
LuaTeX to DVI.

Günter

Re: My current test failures

[Kornel Benko]

Am Samstag, 21. November 2015 um 16:04:11, schrieb Scott Kostyshak 

> On Sat, Nov 21, 2015 at 03:29:09PM -0500, Scott Kostyshak wrote:
> 
> > > 4.) export/templates/IEEEtran-Conference_dvi3_*F: The last changer was 
> > > Scott, now it does not compile here too.
> > 
> > I will take a look.
> 
> I just updated the format. This did not change anything. The document
> fails to compile because of "String contains an invalid utf-8 sequence"
> and "Missing glyphs!".
> 
> Scott

That helps.

Setting \font_math and \inputencoding.

Kornel

signature.asc
Description: This is a digitally signed message part.

Re: My current test failures

[Kornel Benko]

Am Samstag, 21. November 2015 um 22:10:24, schrieb Guenter Milde 

> On 2015-11-21, Scott Kostyshak wrote:
> 
> > [-- Type: text/plain, Encoding: quoted-printable --]
> 
> > On Sat, Nov 21, 2015 at 03:29:09PM -0500, Scott Kostyshak wrote:
> 
> >> > 4.) export/templates/IEEEtran-Conference_dvi3_*F: The last changer was 
> >> > Scott, now it does not compile here too.
> 
> >> I will take a look.
> 
> > I just updated the format. This did not change anything. The document
> > fails to compile because of "String contains an invalid utf-8 sequence"
> > and "Missing glyphs!".
> 
> Missing inputenc package!
> 
> After fixing this (8482b2169bf9c/lyxgit), the document compiles also with
> LuaTeX to DVI.

So my fix is obsolete?

> Günter

Kornel

signature.asc
Description: This is a digitally signed message part.