Re: ctests (was: Intro with PDF(luatex))

2016-09-16 Thread Scott Kostyshak 
On Fri, Sep 16, 2016 at 07:26:12AM +, Guenter Milde wrote:
> On 2016-09-15, Scott Kostyshak wrote:

> > But not the mystery. How did it work for you before and not for me? Do
> > you have \Esc defined locally somehow?
> 
> I must have run the tests while either the \Esc was commented or
> \usepackage{keystroke} in the preamble while updating git with uncommented
> \Esc and without keystroke :-(

Ah OK. So there is no difference between LaTeX installations (regarding
this issue).

Thanks,

Scott


signature.asc
Description: PGP signature

Re: ctests (was: Intro with PDF(luatex))

2016-09-16 Thread Guenter Milde 
On 2016-09-15, Scott Kostyshak wrote:
> On Thu, Sep 15, 2016 at 07:19:50PM +, Guenter Milde wrote:

Dear Scott,

>> >> > >> > 280:export/export/Unicode-characters/077-79-mathops-technical-control-utf8_pdf2

>> >> > > I get the following error:
>> >> > 
>> >> > > ! Undefined control sequence.
>> >> > > l.114 ...380}]  Escape  TODO: user keystroke? \Esc
>> ...
>> >> In the .lyx file there is an ERT with \Esc

>> >> Somehow, \Esc is defined for you but not for me. Do you know where?

>> > Missing '\usepackage{keystroke}' in the preamble?

>> That solved the failure.

> But not the mystery. How did it work for you before and not for me? Do
> you have \Esc defined locally somehow?

I must have run the tests while either the \Esc was commented or
\usepackage{keystroke} in the preamble while updating git with uncommented
\Esc and without keystroke :-(

Günter

Re: ctests (was: Intro with PDF(luatex))

2016-09-15 Thread Scott Kostyshak 
On Thu, Sep 15, 2016 at 07:05:51PM +, Guenter Milde wrote:
> On 2016-09-14, Kornel Benko wrote:
> 
> > [-- Type: text/plain, Encoding: 7bit --]
> 
> > Am Mittwoch, 14. September 2016 um 16:36:38, schrieb Scott Kostyshak 
> > 
> >> On Wed, Sep 14, 2016 at 10:26:47PM +0200, Kornel Benko wrote:
> >> > Am Mittwoch, 14. September 2016 um 15:44:31, schrieb Scott Kostyshak 
> >> > 
> >> > > On Wed, Sep 14, 2016 at 07:25:43PM +, Guenter Milde wrote:
> 
> >> > > > > Full list of failing tests is attached. The tests were run on a 
> >> > > > > clean
> >> > > > > checkout of f2a263e3.
> >> > > >
> >> > > > SUSPENDED.LYXBUGS are both, "suspended" and inverted because they 
> >> > > > match in
> >> > > > both suspended- and suspiciousTests.
> >> > > > This means they fail because export works and you may remove the 
> >> > > > pattern(s)
> >> > > > from "suspiciousTests"
> >> > > > (checking the output first if you have some spare time).
> >> >
> >> > No please. They have to be removed from suspiciousTests only.
> 
> >> OK. Should I do that for the ones with SUSPENDED.LYXBUGS on the list I
> >> sent?
> 
> >> Scott
> 
> > These are failing here
> 
> > 1508 - SUSPENDED.LYXBUGS_export/doc/hu/Intro_dvi3_texF (Failed)
> > 1515 - SUSPENDED.LYXBUGS_export/doc/hu/Intro_pdf5_texF (Failed)
> > 1524 - SUSPENDED.LYXBUGS_export/doc/hu/Tutorial_dvi3_texF (Failed)
> > 1531 - SUSPENDED.LYXBUGS_export/doc/hu/Tutorial_pdf5_texF (Failed)
> > 1540 - SUSPENDED.LYXBUGS_export/doc/id/Intro_dvi3_texF (Failed)
> > 1547 - SUSPENDED.LYXBUGS_export/doc/id/Intro_pdf5_texF (Failed)
> > 1556 - SUSPENDED.LYXBUGS_export/doc/id/Shortcuts_dvi3_texF (Failed)
> > 1563 - SUSPENDED.LYXBUGS_export/doc/id/Shortcuts_pdf5_texF (Failed)
> > 1572 - SUSPENDED.LYXBUGS_export/doc/id/Tutorial_dvi3_texF (Failed)
> > 1579 - SUSPENDED.LYXBUGS_export/doc/id/Tutorial_pdf5_texF (Failed)
> > 4130 - SUSPENDED.LYXBUGS_export/examples/hu/example_lyxified_dvi3_texF 
> > (Failed)
> > 4137 - SUSPENDED.LYXBUGS_export/examples/hu/example_lyxified_pdf5_texF 
> > (Failed)
> > 4146 - SUSPENDED.LYXBUGS_export/examples/hu/example_raw_dvi3_texF 
> > (Failed)
> > 4153 - SUSPENDED.LYXBUGS_export/examples/hu/example_raw_pdf5_texF 
> > (Failed)
> > 4162 - SUSPENDED.LYXBUGS_export/examples/hu/splash_dvi3_texF (Failed)
> > 4169 - SUSPENDED.LYXBUGS_export/examples/hu/splash_pdf5_texF (Failed)
> 
> > If they fail on your side too, then yes.
> > Actually, I checked, you have the same set :)
> 
> This is the section
> 
> -#9910 use LuaTeX-compatible language names
> -# Wrong language name for LuaTeX (with Babel, no error with Polyglossia)
> -# Seems fixed in recent Babel now (2016-09-07)
> -# After LyX 2.1 is released, apply the patch and remove these
> -# See http://www.mail-archive.com/lyx-devel@lists.lyx.org/msg181595.html
> -# ! LuaTeX error 
> ...e/2015/texmf-dist/tex/luatex/hyph-utf8/luatex-hyphen.lua:53: 
> luatex-hyphen: no entry in language.dat.lua for this language: bahasa
> -export/doc/attic/id_UserGuide_(dvi3|pdf5).*
> -export/(doc|examples)/id/.*_(dvi3|pdf5)_texF
> -export/(doc|examples)/hu/.*(dvi3|pdf5)_texF
> 
> 
> Feel free to either still change the language name or just close the bug
> report #9910 as outdated (fixed upstream).

From what I understand, you took care of everything. If there's anything
I'm supposed to do on this, let me know. Otherwise I'll consider it
solved and will run the tests again and confirm the SUSPENDED.LYXBUGS
failures are gone.

Thanks,

Scott


signature.asc
Description: PGP signature

Re: ctests (was: Intro with PDF(luatex))

2016-09-15 Thread Scott Kostyshak 
On Thu, Sep 15, 2016 at 07:19:50PM +, Guenter Milde wrote:
> Dear Scott and Kornel,
> 
> On 2016-09-15, Kornel Benko wrote:
> > Am Donnerstag, 15. September 2016 um 10:50:46, schrieb Scott Kostyshak 
> > 
> >> On Thu, Sep 15, 2016 at 08:56:09AM +, Guenter Milde wrote:
> 
> >> > >> > 280:export/export/Unicode-characters/077-79-mathops-technical-control-utf8_pdf2
> 
> >> > > I get the following error:
> >> > 
> >> > > ! Undefined control sequence.
> >> > > l.114 ...380}]  Escape  TODO: user keystroke? \Esc
> 
> ...
> 
> >> In the .lyx file there is an ERT with \Esc
> 
> >> Somehow, \Esc is defined for you but not for me. Do you know where?
> 
> I see. So the comment/experiment was in the lyx file, not in unicodesymbols.
> 
> > Missing '\usepackage{keystroke}' in the preamble?
> 
> That solved the failure.

But not the mystery. How did it work for you before and not for me? Do
you have \Esc defined locally somehow?

> It should work now. Unfortunately, I had to invert all Unicode_character
> tests, because "export failed while converting"
> (see the comment in suspiciousTests).
> 
> 
> 
> >> By the way is there a way to see in LaTeX exactly where a command is
> >> defined? For example, whether it comes from the .tex file itself or the
> >> .sty or a package (e.g. and what line *in* the package file)? That would
> >> be useful for my learning how to debug issues like this.
> 
> Not easily (of course, you can `grep` in the sources, try googling for
> documentation or tips and tricks, or ask at comp.text.tex).
> 
> In case of an error, the log gives some hints: whenever a new file is
> loaded, you see a "(" followed by the path. After processing the file,
> closing is indicated by ")". If a file loads another one, the () are nested.
> This way you can find out which file the code triggering the error is from.

Good to know. I have not paid attention to this.

> For location of the problem in a LyX file, line-numbers or a search
> feature in the source pane would be nice. Until we have such a thing, you
> can open the tmp-dir and then open the log with a decent text editor...

OK.

Thanks,

Scott


signature.asc
Description: PGP signature

Re: ctests (was: Intro with PDF(luatex))

2016-09-15 Thread Kornel Benko 
Am Donnerstag, 15. September 2016 um 19:22:38, schrieb Guenter Milde 

> On 2016-09-15, Kornel Benko wrote:
> > Am Donnerstag, 15. September 2016 um 09:21:21, schrieb Guenter Milde 
> > 
> 
> >> I did not think about the lyx2lyx export and hence used a too generic
> >> "inversion pattern".
> 
> > I suspected something in that direction.
> 
> >> As testing these samples for other export routes or conversion or loading
> >> does not gain any new insights, I moved them to a new subdirectory
> >> autotests/export/latex/ and added "ignore" clauses for samples from this
> >> subdirectory.
> 
> > OK.
> 
> Done.
> 
> Unfortunately, all tests in autotests/export/latex/Unicode-characters now
> fail with
>
>  could not make dir 
> "/usr/local/src/lyxtest/autotests/out-home/AbC_1zG2wo/latex/Unicode-characters"
>  at /usr/local/src/lyx/development/autotests/lyxStatus.pm line 97.
>  Called stack
>  (0) lyxStatus::diestack() called from 
> "/usr/local/src/lyx/development/autotests/useSystemFonts.pl":154
>  CMake Error at /usr/local/src/lyx/development/autotests/export.cmake:49 
> (message):
>   Export failed while converting
> 

This is due to call 'mkdir 
/usr/local/src/lyxtest/autotests/out-home/AbC_1zG2wo/latex/Unicode-characters'. 
While the directory 'AbC_1zG2wo' exist,
the dir 'AbC_1zG2womk/latex' does not. Changing to call 'mkpath ...', now it 
works again.

> Günter

Kornel

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

Re: ctests (was: Intro with PDF(luatex))

2016-09-15 Thread Guenter Milde 
On 2016-09-15, Kornel Benko wrote:
> Am Donnerstag, 15. September 2016 um 09:21:21, schrieb Guenter Milde 
> 

>> I did not think about the lyx2lyx export and hence used a too generic
>> "inversion pattern".

> I suspected something in that direction.

>> As testing these samples for other export routes or conversion or loading
>> does not gain any new insights, I moved them to a new subdirectory
>> autotests/export/latex/ and added "ignore" clauses for samples from this
>> subdirectory.

> OK.

Done.

Unfortunately, all tests in autotests/export/latex/Unicode-characters now
fail with

 could not make dir 
"/usr/local/src/lyxtest/autotests/out-home/AbC_1zG2wo/latex/Unicode-characters" 
at /usr/local/src/lyx/development/autotests/lyxStatus.pm line 97.
 Called stack
 (0) lyxStatus::diestack() called from 
"/usr/local/src/lyx/development/autotests/useSystemFonts.pl":154
 CMake Error at /usr/local/src/lyx/development/autotests/export.cmake:49 
(message):
  Export failed while converting


Günter

Re: ctests (was: Intro with PDF(luatex))

2016-09-15 Thread Guenter Milde 
Dear Scott and Kornel,

On 2016-09-15, Kornel Benko wrote:
> Am Donnerstag, 15. September 2016 um 10:50:46, schrieb Scott Kostyshak 
> 
>> On Thu, Sep 15, 2016 at 08:56:09AM +, Guenter Milde wrote:

>> > >> > 280:export/export/Unicode-characters/077-79-mathops-technical-control-utf8_pdf2

>> > > I get the following error:
>> > 
>> > > ! Undefined control sequence.
>> > > l.114 ...380}]  Escape  TODO: user keystroke? \Esc

...

>> In the .lyx file there is an ERT with \Esc

>> Somehow, \Esc is defined for you but not for me. Do you know where?

I see. So the comment/experiment was in the lyx file, not in unicodesymbols.

> Missing '\usepackage{keystroke}' in the preamble?

That solved the failure.

It should work now. Unfortunately, I had to invert all Unicode_character
tests, because "export failed while converting"
(see the comment in suspiciousTests).



>> By the way is there a way to see in LaTeX exactly where a command is
>> defined? For example, whether it comes from the .tex file itself or the
>> .sty or a package (e.g. and what line *in* the package file)? That would
>> be useful for my learning how to debug issues like this.

Not easily (of course, you can `grep` in the sources, try googling for
documentation or tips and tricks, or ask at comp.text.tex).

In case of an error, the log gives some hints: whenever a new file is
loaded, you see a "(" followed by the path. After processing the file,
closing is indicated by ")". If a file loads another one, the () are nested.
This way you can find out which file the code triggering the error is from.

For location of the problem in a LyX file, line-numbers or a search
feature in the source pane would be nice. Until we have such a thing, you
can open the tmp-dir and then open the log with a decent text editor...


Günter

Re: ctests (was: Intro with PDF(luatex))

2016-09-15 Thread Guenter Milde 
On 2016-09-14, Kornel Benko wrote:

> [-- Type: text/plain, Encoding: 7bit --]

> Am Mittwoch, 14. September 2016 um 16:36:38, schrieb Scott Kostyshak 
> 
>> On Wed, Sep 14, 2016 at 10:26:47PM +0200, Kornel Benko wrote:
>> > Am Mittwoch, 14. September 2016 um 15:44:31, schrieb Scott Kostyshak 
>> > 
>> > > On Wed, Sep 14, 2016 at 07:25:43PM +, Guenter Milde wrote:

>> > > > > Full list of failing tests is attached. The tests were run on a clean
>> > > > > checkout of f2a263e3.
>> > > >
>> > > > SUSPENDED.LYXBUGS are both, "suspended" and inverted because they 
>> > > > match in
>> > > > both suspended- and suspiciousTests.
>> > > > This means they fail because export works and you may remove the 
>> > > > pattern(s)
>> > > > from "suspiciousTests"
>> > > > (checking the output first if you have some spare time).
>> >
>> > No please. They have to be removed from suspiciousTests only.

>> OK. Should I do that for the ones with SUSPENDED.LYXBUGS on the list I
>> sent?

>> Scott

> These are failing here

>   1508 - SUSPENDED.LYXBUGS_export/doc/hu/Intro_dvi3_texF (Failed)
>   1515 - SUSPENDED.LYXBUGS_export/doc/hu/Intro_pdf5_texF (Failed)
>   1524 - SUSPENDED.LYXBUGS_export/doc/hu/Tutorial_dvi3_texF (Failed)
>   1531 - SUSPENDED.LYXBUGS_export/doc/hu/Tutorial_pdf5_texF (Failed)
>   1540 - SUSPENDED.LYXBUGS_export/doc/id/Intro_dvi3_texF (Failed)
>   1547 - SUSPENDED.LYXBUGS_export/doc/id/Intro_pdf5_texF (Failed)
>   1556 - SUSPENDED.LYXBUGS_export/doc/id/Shortcuts_dvi3_texF (Failed)
>   1563 - SUSPENDED.LYXBUGS_export/doc/id/Shortcuts_pdf5_texF (Failed)
>   1572 - SUSPENDED.LYXBUGS_export/doc/id/Tutorial_dvi3_texF (Failed)
>   1579 - SUSPENDED.LYXBUGS_export/doc/id/Tutorial_pdf5_texF (Failed)
>   4130 - SUSPENDED.LYXBUGS_export/examples/hu/example_lyxified_dvi3_texF 
> (Failed)
>   4137 - SUSPENDED.LYXBUGS_export/examples/hu/example_lyxified_pdf5_texF 
> (Failed)
>   4146 - SUSPENDED.LYXBUGS_export/examples/hu/example_raw_dvi3_texF 
> (Failed)
>   4153 - SUSPENDED.LYXBUGS_export/examples/hu/example_raw_pdf5_texF 
> (Failed)
>   4162 - SUSPENDED.LYXBUGS_export/examples/hu/splash_dvi3_texF (Failed)
>   4169 - SUSPENDED.LYXBUGS_export/examples/hu/splash_pdf5_texF (Failed)

> If they fail on your side too, then yes.
> Actually, I checked, you have the same set :)

This is the section

-#9910 use LuaTeX-compatible language names
-# Wrong language name for LuaTeX (with Babel, no error with Polyglossia)
-# Seems fixed in recent Babel now (2016-09-07)
-# After LyX 2.1 is released, apply the patch and remove these
-# See http://www.mail-archive.com/lyx-devel@lists.lyx.org/msg181595.html
-# ! LuaTeX error 
...e/2015/texmf-dist/tex/luatex/hyph-utf8/luatex-hyphen.lua:53: luatex-hyphen: 
no entry in language.dat.lua for this language: bahasa
-export/doc/attic/id_UserGuide_(dvi3|pdf5).*
-export/(doc|examples)/id/.*_(dvi3|pdf5)_texF
-export/(doc|examples)/hu/.*(dvi3|pdf5)_texF


Feel free to either still change the language name or just close the bug
report #9910 as outdated (fixed upstream).


Günter

Re: ctests (was: Intro with PDF(luatex))

2016-09-15 Thread Kornel Benko 
Am Donnerstag, 15. September 2016 um 10:50:46, schrieb Scott Kostyshak 

> On Thu, Sep 15, 2016 at 08:56:09AM +, Guenter Milde wrote:
> > On 2016-09-14, Scott Kostyshak wrote:
> > > On Wed, Sep 14, 2016 at 07:25:43PM +, Guenter Milde wrote:
> > 
> > >> > 280:export/export/Unicode-characters/077-79-mathops-technical-control-utf8_pdf2
> > 
> > >> All 19 "Unicode-characters" tests pass here.
> > 
> > > I get the following error:
> > 
> > > ! Undefined control sequence.
> > > l.114 ...380}]  Escape  TODO: user keystroke? \Esc
> > 
> > 
> > This is strange:
> > 
> > * I had once such a comment in lib/unicodesymbols
> >   (currently, we print the word "Escape" for the sign 
> >BROKEN CIRCLE WITH NORTHWEST ARROW 0x238b ⎋)
> > 
> > * at some time this may have been uncommented by accident
> > 
> > * the relevant line in lib/unicodesymbols is now:
> > 
> >   0x238b "Escape"   "" "force=utf8,notermination=text" "" 
> > "" # Qt::Key_Escape, BROKEN CIRCLE WITH NORTHWEST ARROW = escape
> > 
> > * I don't see differences between my local lib/unicodesymbols and
> >   origin/master at e4d2c1c04fb21
> > 
> > Either there is some git-inconsistency due to my experimenting without
> > experience or you have some local changes...
> > 
> > What does line 2431 in your lib/unicodesymbols look like?
> 
> It is the following:
> 
> 0x238b "Escape"   "" "force=utf8,notermination=text" "" "" # 
> Qt::Key_Escape, BROKEN CIRCLE WITH NORTHWEST ARROW = escape
> 
> In the .lyx file there is an ERT with \Esc
> 
> Somehow, \Esc is defined for you but not for me. Do you know where?

Missing '\usepackage{keystroke}' in the preamble?

> To be clear, here is what I did:
> 
> 1. git pull (this gives me commit e36a8903 now)
> 2. git clean -xdf
> 3. [build]
> 4. [lyx-binary] 
> autotests/export/Unicode-characters/077-79-mathops-technical-control-utf8.lyx
> 5. View PDF (pdflatex)
> 
> By the way is there a way to see in LaTeX exactly where a command is
> defined? For example, whether it comes from the .tex file itself or the
> .sty or a package (e.g. and what line *in* the package file)? That would
> be useful for my learning how to debug issues like this.
> 
> Scott

Kornel

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

Re: ctests (was: Intro with PDF(luatex))

2016-09-15 Thread Scott Kostyshak 
On Thu, Sep 15, 2016 at 08:56:09AM +, Guenter Milde wrote:
> On 2016-09-14, Scott Kostyshak wrote:
> > On Wed, Sep 14, 2016 at 07:25:43PM +, Guenter Milde wrote:
> 
> >> > 280:export/export/Unicode-characters/077-79-mathops-technical-control-utf8_pdf2
> 
> >> All 19 "Unicode-characters" tests pass here.
> 
> > I get the following error:
> 
> > ! Undefined control sequence.
> > l.114 ...380}]  Escape  TODO: user keystroke? \Esc
> 
> 
> This is strange:
> 
> * I had once such a comment in lib/unicodesymbols
>   (currently, we print the word "Escape" for the sign 
>BROKEN CIRCLE WITH NORTHWEST ARROW 0x238b ⎋)
> 
> * at some time this may have been uncommented by accident
> 
> * the relevant line in lib/unicodesymbols is now:
> 
>   0x238b "Escape"   "" "force=utf8,notermination=text" "" "" 
> # Qt::Key_Escape, BROKEN CIRCLE WITH NORTHWEST ARROW = escape
> 
> * I don't see differences between my local lib/unicodesymbols and
>   origin/master at e4d2c1c04fb21
> 
> Either there is some git-inconsistency due to my experimenting without
> experience or you have some local changes...
> 
> What does line 2431 in your lib/unicodesymbols look like?

It is the following:

0x238b "Escape"   "" "force=utf8,notermination=text" "" "" # 
Qt::Key_Escape, BROKEN CIRCLE WITH NORTHWEST ARROW = escape

In the .lyx file there is an ERT with \Esc

Somehow, \Esc is defined for you but not for me. Do you know where?

To be clear, here is what I did:

1. git pull (this gives me commit e36a8903 now)
2. git clean -xdf
3. [build]
4. [lyx-binary] 
autotests/export/Unicode-characters/077-79-mathops-technical-control-utf8.lyx
5. View PDF (pdflatex)

By the way is there a way to see in LaTeX exactly where a command is
defined? For example, whether it comes from the .tex file itself or the
.sty or a package (e.g. and what line *in* the package file)? That would
be useful for my learning how to debug issues like this.

Scott


signature.asc
Description: PGP signature

Re: ctests (was: Intro with PDF(luatex))

2016-09-15 Thread Kornel Benko 
Am Donnerstag, 15. September 2016 um 09:21:21, schrieb Guenter Milde 

> On 2016-09-14, Kornel Benko wrote:
> > Am Mittwoch, 14. September 2016 um 19:25:43, schrieb Guenter Milde 
> > 
> >> On 2016-09-14, Scott Kostyshak wrote:
> 
> >> > I attach my complete list of failing tests (for git hash f2a263e3). The
> >> > ones that are interesting I think are listed below with some comments:
> 
> >> > 206:INVERTED.LYXBUGS_export/export/LongestLabelWithUnderscore_lyx16
> ...
> 
> >> It looks like ctest is testing the backup files from lyx2lyx conversion.
> >> Do you have some *lyx21.lyx (etc.) files in the tested directories?
> 
> > No backups, the test is exporting to lyx16 (e.g. lyx2lyx) format.
> 
> I see, besides the lyx2lyx tests, there are also export tests for lyx2lyx.
> 
> >> I hope these backups are marked as such with ~ soon.
> >> But we could also (at least for the meantime) add a clause to ignore them
> >> in "ignoredtests". 
> 
> > No need. The tests have a reason.
> 
> I see.
> 
> However, the inverted tests in autotests/export/ are dedicated LaTeX tests
> where we know that they currently fail with LaTeX and why.

It is not _only_ latex export. Also html and older lyx versions are included.
(Anything you can use by 'lyx -export ...' should be there,
but ATM we consider only xhtml, pdf, pdf2, pdf3, pdf4, pdf5, dvi, dvi3, lyx16, 
lyx21, lyx22)

> I did not think about the lyx2lyx export and hence used a too generic
> "inversion pattern".

I suspected something in that direction.

> As testing these samples for other export routes or conversion or loading
> does not gain any new insights, I moved them to a new subdirectory
> autotests/export/latex/ and added "ignore" clauses for samples from this
> subdirectory.

OK.

> I hope this helps to keep the test system relatively clean and simple.
> 
> 
> Günter

Kornel

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

Re: ctests (was: Intro with PDF(luatex))

2016-09-15 Thread Guenter Milde 
On 2016-09-14, Kornel Benko wrote:
> Am Mittwoch, 14. September 2016 um 19:25:43, schrieb Guenter Milde 
> 
>> On 2016-09-14, Scott Kostyshak wrote:

>> > I attach my complete list of failing tests (for git hash f2a263e3). The
>> > ones that are interesting I think are listed below with some comments:

>> > 206:INVERTED.LYXBUGS_export/export/LongestLabelWithUnderscore_lyx16
...

>> It looks like ctest is testing the backup files from lyx2lyx conversion.
>> Do you have some *lyx21.lyx (etc.) files in the tested directories?

> No backups, the test is exporting to lyx16 (e.g. lyx2lyx) format.

I see, besides the lyx2lyx tests, there are also export tests for lyx2lyx.

>> I hope these backups are marked as such with ~ soon.
>> But we could also (at least for the meantime) add a clause to ignore them
>> in "ignoredtests". 

> No need. The tests have a reason.

I see.

However, the inverted tests in autotests/export/ are dedicated LaTeX tests
where we know that they currently fail with LaTeX and why.

I did not think about the lyx2lyx export and hence used a too generic
"inversion pattern".

As testing these samples for other export routes or conversion or loading
does not gain any new insights, I moved them to a new subdirectory
autotests/export/latex/ and added "ignore" clauses for samples from this
subdirectory.

I hope this helps to keep the test system relatively clean and simple.


Günter

Re: ctests (was: Intro with PDF(luatex))

2016-09-15 Thread Guenter Milde 
On 2016-09-14, Scott Kostyshak wrote:
> On Wed, Sep 14, 2016 at 07:25:43PM +, Guenter Milde wrote:

>> > 280:export/export/Unicode-characters/077-79-mathops-technical-control-utf8_pdf2

>> All 19 "Unicode-characters" tests pass here.

> I get the following error:

> ! Undefined control sequence.
> l.114 ...380}]  Escape  TODO: user keystroke? \Esc


This is strange:

* I had once such a comment in lib/unicodesymbols
  (currently, we print the word "Escape" for the sign 
   BROKEN CIRCLE WITH NORTHWEST ARROW 0x238b ⎋)

* at some time this may have been uncommented by accident

* the relevant line in lib/unicodesymbols is now:

  0x238b "Escape"   "" "force=utf8,notermination=text" "" "" # 
Qt::Key_Escape, BROKEN CIRCLE WITH NORTHWEST ARROW = escape

* I don't see differences between my local lib/unicodesymbols and
  origin/master at e4d2c1c04fb21

Either there is some git-inconsistency due to my experimenting without
experience or you have some local changes...

What does line 2431 in your lib/unicodesymbols look like?

Günter

Re: ctests (was: Intro with PDF(luatex))

2016-09-14 Thread Kornel Benko 
Am Mittwoch, 14. September 2016 um 16:36:38, schrieb Scott Kostyshak 

> On Wed, Sep 14, 2016 at 10:26:47PM +0200, Kornel Benko wrote:
> > Am Mittwoch, 14. September 2016 um 15:44:31, schrieb Scott Kostyshak 
> > 
> > > On Wed, Sep 14, 2016 at 07:25:43PM +, Guenter Milde wrote:
> 
> > > > > Full list of failing tests is attached. The tests were run on a clean
> > > > > checkout of f2a263e3.
> > > > 
> > > > SUSPENDED.LYXBUGS are both, "suspended" and inverted because they match 
> > > > in
> > > > both suspended- and suspiciousTests.
> > > > This means they fail because export works and you may remove the 
> > > > pattern(s)
> > > > from "suspiciousTests"
> > > > (checking the output first if you have some spare time).
> > 
> > No please. They have to be removed from suspiciousTests only.
> 
> OK. Should I do that for the ones with SUSPENDED.LYXBUGS on the list I
> sent?
> 
> Scott

These are failing here

740 - SUSPENDED.LYXBUGS_export/doc/attic/id_UserGuide_dvi3_texF (Failed)
747 - SUSPENDED.LYXBUGS_export/doc/attic/id_UserGuide_pdf5_texF (Failed)
1508 - SUSPENDED.LYXBUGS_export/doc/hu/Intro_dvi3_texF (Failed)
1515 - SUSPENDED.LYXBUGS_export/doc/hu/Intro_pdf5_texF (Failed)
1524 - SUSPENDED.LYXBUGS_export/doc/hu/Tutorial_dvi3_texF (Failed)
1531 - SUSPENDED.LYXBUGS_export/doc/hu/Tutorial_pdf5_texF (Failed)
1540 - SUSPENDED.LYXBUGS_export/doc/id/Intro_dvi3_texF (Failed)
1547 - SUSPENDED.LYXBUGS_export/doc/id/Intro_pdf5_texF (Failed)
1556 - SUSPENDED.LYXBUGS_export/doc/id/Shortcuts_dvi3_texF (Failed)
1563 - SUSPENDED.LYXBUGS_export/doc/id/Shortcuts_pdf5_texF (Failed)
1572 - SUSPENDED.LYXBUGS_export/doc/id/Tutorial_dvi3_texF (Failed)
1579 - SUSPENDED.LYXBUGS_export/doc/id/Tutorial_pdf5_texF (Failed)
4130 - SUSPENDED.LYXBUGS_export/examples/hu/example_lyxified_dvi3_texF 
(Failed)
4137 - SUSPENDED.LYXBUGS_export/examples/hu/example_lyxified_pdf5_texF 
(Failed)
4146 - SUSPENDED.LYXBUGS_export/examples/hu/example_raw_dvi3_texF 
(Failed)
4153 - SUSPENDED.LYXBUGS_export/examples/hu/example_raw_pdf5_texF 
(Failed)
4162 - SUSPENDED.LYXBUGS_export/examples/hu/splash_dvi3_texF (Failed)
4169 - SUSPENDED.LYXBUGS_export/examples/hu/splash_pdf5_texF (Failed)
4178 - SUSPENDED.LYXBUGS_export/examples/id/splash_dvi3_texF (Failed)
4185 - SUSPENDED.LYXBUGS_export/examples/id/splash_pdf5_texF (Failed)

If they fail on your side too, then yes.
Actually, I checked, you have the same set :)

Kornel

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

Re: ctests (was: Intro with PDF(luatex))

2016-09-14 Thread Scott Kostyshak 
On Wed, Sep 14, 2016 at 10:26:47PM +0200, Kornel Benko wrote:
> Am Mittwoch, 14. September 2016 um 15:44:31, schrieb Scott Kostyshak 
> 
> > On Wed, Sep 14, 2016 at 07:25:43PM +, Guenter Milde wrote:

> > > > Full list of failing tests is attached. The tests were run on a clean
> > > > checkout of f2a263e3.
> > > 
> > > SUSPENDED.LYXBUGS are both, "suspended" and inverted because they match in
> > > both suspended- and suspiciousTests.
> > > This means they fail because export works and you may remove the 
> > > pattern(s)
> > > from "suspiciousTests"
> > > (checking the output first if you have some spare time).
> 
> No please. They have to be removed from suspiciousTests only.

OK. Should I do that for the ones with SUSPENDED.LYXBUGS on the list I
sent?

Scott


signature.asc
Description: PGP signature

Re: ctests (was: Intro with PDF(luatex))

2016-09-14 Thread Kornel Benko 
Am Mittwoch, 14. September 2016 um 19:25:43, schrieb Guenter Milde 

> Dear Scott,
> 
> On 2016-09-14, Scott Kostyshak wrote:
> 
> > I attach my complete list of failing tests (for git hash f2a263e3). The
> > ones that are interesting I think are listed below with some comments:
> 
> ...
> 
> > 280:export/export/Unicode-characters/077-79-mathops-technical-control-utf8_pdf2
> 
> > Is this something new that you committed recently? Does the test pass
> > for you?
> 
> There are new test samples for lib/unicodesymbols.
> All 19 "Unicode-characters" tests pass here.
> 
> Could you run the test "manually" and tell what is failing?
> 
> > 206:INVERTED.LYXBUGS_export/export/LongestLabelWithUnderscore_lyx16
> > 207:INVERTED.LYXBUGS_export/export/LongestLabelWithUnderscore_lyx21
> > 208:INVERTED.LYXBUGS_export/export/LongestLabelWithUnderscore_lyx22
> 
> > 5435:export/mathmacros/testcases_speed_lyx22
> 
> > I'm not sure what the above mean.
> 
> It looks like ctest is testing the backup files from lyx2lyx conversion.
> Do you have some *lyx21.lyx (etc.) files in the tested directories?

No backups, the test is exporting to lyx16 (e.g. lyx2lyx) format.

> I hope these backups are marked as such with ~ soon.
> But we could also (at least for the meantime) add a clause to ignore them
> in "ignoredtests". 

No need. The tests have a reason.

> > Full list of failing tests is attached. The tests were run on a clean
> > checkout of f2a263e3.
> 

Kornel

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

Re: ctests (was: Intro with PDF(luatex))

2016-09-14 Thread Kornel Benko 
Am Mittwoch, 14. September 2016 um 15:44:31, schrieb Scott Kostyshak 

> On Wed, Sep 14, 2016 at 07:25:43PM +, Guenter Milde wrote:
> 
> > > 280:export/export/Unicode-characters/077-79-mathops-technical-control-utf8_pdf2
> > 
> > > Is this something new that you committed recently? Does the test pass
> > > for you?
> > 
> > There are new test samples for lib/unicodesymbols.
> > All 19 "Unicode-characters" tests pass here.
> > 
> > Could you run the test "manually" and tell what is failing?
> 
> I get the following error:
> 
> ! Undefined control sequence.
> l.114 ...380}]  Escape  TODO: user keystroke? \Esc
> 
> I attach the complete log.
> 
> > > Full list of failing tests is attached. The tests were run on a clean
> > > checkout of f2a263e3.
> > 
> > SUSPENDED.LYXBUGS are both, "suspended" and inverted because they match in
> > both suspended- and suspiciousTests.
> > This means they fail because export works and you may remove the pattern(s)
> > from "suspiciousTests"
> > (checking the output first if you have some spare time).

No please. They have to be removed from suspiciousTests only.

> Let's see if Kornel has an opinion on what he thinks is best, and if he
> can compare his failing test to the list I sent.

> Scott

Kornel

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

Re: ctests (was: Intro with PDF(luatex))

2016-09-14 Thread Scott Kostyshak 
On Wed, Sep 14, 2016 at 07:25:43PM +, Guenter Milde wrote:

> > 280:export/export/Unicode-characters/077-79-mathops-technical-control-utf8_pdf2
> 
> > Is this something new that you committed recently? Does the test pass
> > for you?
> 
> There are new test samples for lib/unicodesymbols.
> All 19 "Unicode-characters" tests pass here.
> 
> Could you run the test "manually" and tell what is failing?

I get the following error:

! Undefined control sequence.
l.114 ...380}]  Escape  TODO: user keystroke? \Esc

I attach the complete log.

> > Full list of failing tests is attached. The tests were run on a clean
> > checkout of f2a263e3.
> 
> SUSPENDED.LYXBUGS are both, "suspended" and inverted because they match in
> both suspended- and suspiciousTests.
> This means they fail because export works and you may remove the pattern(s)
> from "suspiciousTests"
> (checking the output first if you have some spare time).

Let's see if Kornel has an opinion on what he thinks is best, and if he
can compare his failing test to the list I sent.

Scott
This is pdfTeX, Version 3.14159265-2.6-1.40.17 (TeX Live 2016) (preloaded 
format=pdflatex 2016.9.3)  14 SEP 2016 15:40
entering extended mode
 restricted \write18 enabled.
 %&-line parsing enabled.
**077-79-mathops-technical-control-utf8.tex
(./077-79-mathops-technical-control-utf8.tex
LaTeX2e <2016/03/31> patch level 3
Babel <3.9r> and hyphenation patterns for 83 language(s) loaded.

(/usr/local/texlive/2016/texmf-dist/tex/latex/base/article.cls
Document Class: article 2014/09/29 v1.4h Standard LaTeX document class
(/usr/local/texlive/2016/texmf-dist/tex/latex/base/size10.clo
File: size10.clo 2014/09/29 v1.4h Standard LaTeX file (size option)
)
\c@part=\count79
\c@section=\count80
\c@subsection=\count81
\c@subsubsection=\count82
\c@paragraph=\count83
\c@subparagraph=\count84
\c@figure=\count85
\c@table=\count86
\abovecaptionskip=\skip41
\belowcaptionskip=\skip42
\bibindent=\dimen102
) (/usr/local/texlive/2016/texmf-dist/tex/latex/lm/lmodern.sty
Package: lmodern 2009/10/30 v1.6 Latin Modern Fonts
LaTeX Font Info:Overwriting symbol font `operators' in version `normal'
(Font)  OT1/cmr/m/n --> OT1/lmr/m/n on input line 22.
LaTeX Font Info:Overwriting symbol font `letters' in version `normal'
(Font)  OML/cmm/m/it --> OML/lmm/m/it on input line 23.
LaTeX Font Info:Overwriting symbol font `symbols' in version `normal'
(Font)  OMS/cmsy/m/n --> OMS/lmsy/m/n on input line 24.
LaTeX Font Info:Overwriting symbol font `largesymbols' in version `normal'
(Font)  OMX/cmex/m/n --> OMX/lmex/m/n on input line 25.
LaTeX Font Info:Overwriting symbol font `operators' in version `bold'
(Font)  OT1/cmr/bx/n --> OT1/lmr/bx/n on input line 26.
LaTeX Font Info:Overwriting symbol font `letters' in version `bold'
(Font)  OML/cmm/b/it --> OML/lmm/b/it on input line 27.
LaTeX Font Info:Overwriting symbol font `symbols' in version `bold'
(Font)  OMS/cmsy/b/n --> OMS/lmsy/b/n on input line 28.
LaTeX Font Info:Overwriting symbol font `largesymbols' in version `bold'
(Font)  OMX/cmex/m/n --> OMX/lmex/m/n on input line 29.
LaTeX Font Info:Overwriting math alphabet `\mathbf' in version `normal'
(Font)  OT1/cmr/bx/n --> OT1/lmr/bx/n on input line 31.
LaTeX Font Info:Overwriting math alphabet `\mathsf' in version `normal'
(Font)  OT1/cmss/m/n --> OT1/lmss/m/n on input line 32.
LaTeX Font Info:Overwriting math alphabet `\mathit' in version `normal'
(Font)  OT1/cmr/m/it --> OT1/lmr/m/it on input line 33.
LaTeX Font Info:Overwriting math alphabet `\mathtt' in version `normal'
(Font)  OT1/cmtt/m/n --> OT1/lmtt/m/n on input line 34.
LaTeX Font Info:Overwriting math alphabet `\mathbf' in version `bold'
(Font)  OT1/cmr/bx/n --> OT1/lmr/bx/n on input line 35.
LaTeX Font Info:Overwriting math alphabet `\mathsf' in version `bold'
(Font)  OT1/cmss/bx/n --> OT1/lmss/bx/n on input line 36.
LaTeX Font Info:Overwriting math alphabet `\mathit' in version `bold'
(Font)  OT1/cmr/bx/it --> OT1/lmr/bx/it on input line 37.
LaTeX Font Info:Overwriting math alphabet `\mathtt' in version `bold'
(Font)  OT1/cmtt/m/n --> OT1/lmtt/m/n on input line 38.
) (/usr/local/texlive/2016/texmf-dist/tex/latex/base/fontenc.sty
Package: fontenc 2016/06/19 v1.99m Standard LaTeX package
(/usr/local/texlive/2016/texmf-dist/tex/latex/base/t1enc.def
File: t1enc.def 2016/06/19 v1.99m Standard LaTeX file
LaTeX Font Info:Redeclaring font encoding T1 on input line 48.
)) (/usr/local/texlive/2016/texmf-dist/tex/latex/base/inputenc.sty
Package: inputenc 2015/03/17 v1.2c Input encoding file
\inpenc@prehook=\toks14
\inpenc@posthook=\toks15
(/usr/local/texlive/2016/texmf-dist/tex/latex/base/utf8.def
File: utf8.def 2016/02/28 v1.1s UTF-8

Re: ctests (was: Intro with PDF(luatex))

2016-09-14 Thread Guenter Milde 
Dear Scott,

On 2016-09-14, Scott Kostyshak wrote:

> I attach my complete list of failing tests (for git hash f2a263e3). The
> ones that are interesting I think are listed below with some comments:

...

> 280:export/export/Unicode-characters/077-79-mathops-technical-control-utf8_pdf2

> Is this something new that you committed recently? Does the test pass
> for you?

There are new test samples for lib/unicodesymbols.
All 19 "Unicode-characters" tests pass here.

Could you run the test "manually" and tell what is failing?

> 206:INVERTED.LYXBUGS_export/export/LongestLabelWithUnderscore_lyx16
> 207:INVERTED.LYXBUGS_export/export/LongestLabelWithUnderscore_lyx21
> 208:INVERTED.LYXBUGS_export/export/LongestLabelWithUnderscore_lyx22

> 5435:export/mathmacros/testcases_speed_lyx22

> I'm not sure what the above mean.

It looks like ctest is testing the backup files from lyx2lyx conversion.
Do you have some *lyx21.lyx (etc.) files in the tested directories?

I hope these backups are marked as such with ~ soon.
But we could also (at least for the meantime) add a clause to ignore them
in "ignoredtests". 

> Full list of failing tests is attached. The tests were run on a clean
> checkout of f2a263e3.

SUSPENDED.LYXBUGS are both, "suspended" and inverted because they match in
both suspended- and suspiciousTests.
This means they fail because export works and you may remove the pattern(s)
from "suspiciousTests"
(checking the output first if you have some spare time).

Günter

Re: ctests (was: Intro with PDF(luatex))

2016-09-14 Thread Scott Kostyshak 
On Tue, Sep 13, 2016 at 10:54:06PM -0400, Scott Kostyshak wrote:
> On Tue, Sep 13, 2016 at 08:36:57PM +, Guenter Milde wrote:

> > Which tests still fail?
> 
> I run the tests on current master and post back tomorrow.

I attach my complete list of failing tests (for git hash f2a263e3). The
ones that are interesting I think are listed below with some comments:

3847:export/examples/fr/beamer-article_dvi3_systemF
3851:export/examples/fr/beamer-article_pdf4_texF
3852:export/examples/fr/beamer-article_pdf4_systemF
3854:export/examples/fr/beamer-article_pdf5_systemF

I'm hoping someone will be able to look into the assertion, which I
posted here:
https://www.mail-archive.com/search?l=mid=20160903145049.3jho4smwrfuybzn3%40steph
Richard might be too busy with the 2.2.2 release to take a look.

5233:export/templates/lettre_pdf5_texF 
5234:export/templates/lettre_pdf5_systemF 

Jean-Paul is going to look into these when he has time. See here:
https://www.mail-archive.com/search?l=mid=20160903173655.3iumrihh7tjuiwft%40steph

5339:export/templates/slides_dvi3_systemF
5344:export/templates/slides_pdf4_systemF
5346:export/templates/slides_pdf5_systemF

I'm not sure I've looked into these. I couldn't find any email I sent
regarding them.

280:export/export/Unicode-characters/077-79-mathops-technical-control-utf8_pdf2

Is this something new that you committed recently? Does the test pass
for you?

206:INVERTED.LYXBUGS_export/export/LongestLabelWithUnderscore_lyx16
207:INVERTED.LYXBUGS_export/export/LongestLabelWithUnderscore_lyx21
208:INVERTED.LYXBUGS_export/export/LongestLabelWithUnderscore_lyx22

I'm not sure what the above mean.

5435:export/mathmacros/testcases_speed_lyx22

I'm not sure what this means either.

Full list of failing tests is attached. The tests were run on a clean
checkout of f2a263e3.

Scott
206:INVERTED.LYXBUGS_export/export/LongestLabelWithUnderscore_lyx16
207:INVERTED.LYXBUGS_export/export/LongestLabelWithUnderscore_lyx21
208:INVERTED.LYXBUGS_export/export/LongestLabelWithUnderscore_lyx22
280:export/export/Unicode-characters/077-79-mathops-technical-control-utf8_pdf2
700:SUSPENDED.LYXBUGS_export/doc/attic/id_UserGuide_dvi3_texF
707:SUSPENDED.LYXBUGS_export/doc/attic/id_UserGuide_pdf5_texF
897:UNRELIABLE.WRONG_OUTPUT_export/doc/de/EmbeddedObjects_pdf4_texF
1025:UNRELIABLE.WRONG_OUTPUT_export/doc/es/Additional_pdf4_texF
1041:UNRELIABLE.ERRATIC_export/doc/es/Customization_pdf4_texF
1084:UNRELIABLE.WRONG_OUTPUT_export/doc/es/EmbeddedObjects_dvi3_texF
1089:UNRELIABLE.WRONG_OUTPUT_export/doc/es/EmbeddedObjects_pdf4_texF
1091:UNRELIABLE.WRONG_OUTPUT_export/doc/es/EmbeddedObjects_pdf5_texF
1180:UNRELIABLE.WRONG_OUTPUT_export/doc/es/UserGuide_dvi3_texF
1185:UNRELIABLE.WRONG_OUTPUT_export/doc/es/UserGuide_pdf4_texF
1187:UNRELIABLE.WRONG_OUTPUT_export/doc/es/UserGuide_pdf5_texF
1468:SUSPENDED.LYXBUGS_export/doc/hu/Intro_dvi3_texF
1475:SUSPENDED.LYXBUGS_export/doc/hu/Intro_pdf5_texF
1484:SUSPENDED.LYXBUGS_export/doc/hu/Tutorial_dvi3_texF
1491:SUSPENDED.LYXBUGS_export/doc/hu/Tutorial_pdf5_texF
1500:SUSPENDED.LYXBUGS_export/doc/id/Intro_dvi3_texF
1507:SUSPENDED.LYXBUGS_export/doc/id/Intro_pdf5_texF
1516:SUSPENDED.LYXBUGS_export/doc/id/Shortcuts_dvi3_texF
1523:SUSPENDED.LYXBUGS_export/doc/id/Shortcuts_pdf5_texF
1532:SUSPENDED.LYXBUGS_export/doc/id/Tutorial_dvi3_texF
1539:SUSPENDED.LYXBUGS_export/doc/id/Tutorial_pdf5_texF
2142:UNRELIABLE.NONSTANDARD_export/examples/aa_sample_dvi3_texF
2143:UNRELIABLE.NONSTANDARD_export/examples/aa_sample_dvi3_systemF
2147:UNRELIABLE.NONSTANDARD_export/examples/aa_sample_pdf4_texF
2148:UNRELIABLE.NONSTANDARD_export/examples/aa_sample_pdf4_systemF
2149:UNRELIABLE.NONSTANDARD_export/examples/aa_sample_pdf5_texF
2150:UNRELIABLE.NONSTANDARD_export/examples/aa_sample_pdf5_systemF
2567:UNRELIABLE.ERRATIC_export/examples/seminar_pdf
2568:UNRELIABLE.ERRATIC_export/examples/seminar_pdf2
2569:UNRELIABLE.ERRATIC_export/examples/seminar_pdf3
2570:UNRELIABLE.ERRATIC_export/examples/seminar_pdf4_texF
2571:UNRELIABLE.ERRATIC_export/examples/seminar_pdf4_systemF
3622:UNRELIABLE.WRONG_OUTPUT_export/examples/es/linguistics_pdf4_texF
3726:UNRELIABLE.NONSTANDARD_export/examples/fa/splash_dvi
3727:UNRELIABLE.NONSTANDARD_export/examples/fa/splash_dvi3_texF
3728:UNRELIABLE.NONSTANDARD_export/examples/fa/splash_dvi3_systemF
3729:UNRELIABLE.NONSTANDARD_export/examples/fa/splash_pdf
3730:UNRELIABLE.NONSTANDARD_export/examples/fa/splash_pdf2
3731:UNRELIABLE.NONSTANDARD_export/examples/fa/splash_pdf3
3732:UNRELIABLE.NONSTANDARD_export/examples/fa/splash_pdf4_texF
3733:UNRELIABLE.NONSTANDARD_export/examples/fa/splash_pdf4_systemF
3734:UNRELIABLE.NONSTANDARD_export/examples/fa/splash_pdf5_texF
3735:UNRELIABLE.NONSTANDARD_export/examples/fa/splash_pdf5_systemF
3847:export/examples/fr/beamer-article_dvi3_systemF
3851:export/examples/fr/beamer-article_pdf4_texF
3852:export/examples/fr/beamer-article_pdf4_systemF
3854:export/examples/fr/beamer-article_pdf5_systemF

Re: ctests (was: Intro with PDF(luatex))

2016-09-14 Thread Scott Kostyshak 
On Wed, Sep 14, 2016 at 08:25:31AM +, Guenter Milde wrote:
> On 2016-09-14, Scott Kostyshak wrote:
> 
> >> A big step towards "easy to maintain" will be storing of LaTeX-log
> >> output in the test log. Currently, we always have to "hand-compile"
> >> (and in many cases edit the sources before) to find out what went
> >> wrong.
> 
> > Yes that would be nice. I think we have a ticket for this somewhere. I
> > think this should be implemented more generally, for LyX export on the
> > command line.
> 
> There are two tickets, http://www.lyx.org/trac/ticket/9866 and
> http://www.lyx.org/trac/ticket/9931

Thanks for finding these.

> I don't know whether they should count as duplicate or whether there are use
> cases for both (see the first error in the log + have the chance to examine
> the complete tmpdir if required).
> 
> Maybe solving 9866 would be a good start -- it would definitely save a lot
> of work when examining test failures.

I'm not sure either. Eventually I'm guessing someone will fix one of
those bugs, but I don't think anyone has plans to work on them
currently.

Scott


signature.asc
Description: PGP signature

Re: ctests (was: Intro with PDF(luatex))

2016-09-14 Thread Guenter Milde 
On 2016-09-14, Scott Kostyshak wrote:

>> A big step towards "easy to maintain" will be storing of LaTeX-log
>> output in the test log. Currently, we always have to "hand-compile"
>> (and in many cases edit the sources before) to find out what went
>> wrong.

> Yes that would be nice. I think we have a ticket for this somewhere. I
> think this should be implemented more generally, for LyX export on the
> command line.

There are two tickets, http://www.lyx.org/trac/ticket/9866 and
http://www.lyx.org/trac/ticket/9931

I don't know whether they should count as duplicate or whether there are use
cases for both (see the first error in the log + have the chance to examine
the complete tmpdir if required).

Maybe solving 9866 would be a good start -- it would definitely save a lot
of work when examining test failures.

Günter

Re: ctests (was: Intro with PDF(luatex))

2016-09-13 Thread Scott Kostyshak 
On Tue, Sep 13, 2016 at 08:36:57PM +, Guenter Milde wrote:
> Dear Scott,
> 
> On 2016-09-12, Scott Kostyshak wrote:
> 
> > OK let's both run the full tests after that and compare again to see if
> > we have any differences.
> 
> I can't run the full tests (no chinese, no japanese, no hebrew, ...; no disk
> space, no computer to run all night).

Ah good to know.

> > At least for the normal (e.g. not the suspicious or unreliable) tests we
> > are approaching zero. 
> 
> Which tests still fail?

I run the tests on current master and post back tomorrow.

> The idea is, to add failures that cannot be solved immediately to
> "invertedTests" (currently called "suspiciousTests"):
> 
> - If the cause is known, under the relevant sublabel.
>   (Normally, there is no need for new sublabels - at least not for just
>   one pattern.)
> 
> - If the cause is not known, under the sublabel TODO
>   (Adding the date and git-hash of the first occurence of the failure will
>   help in tracking down the cause later.)
> 
> This way, it should be easy to reach 0 failing reliable tests. 
> (The remaining task will be to clean up the TODO section every now and
> than...)

OK seems like a good plan.

> > Once we get there, I think it will be easy to
> > maintain.
> 
> A big step towards "easy to maintain" will be storing of LaTeX-log output in
> the test log. Currently, we always have to "hand-compile" (and in many cases
> edit the sources before) to find out what went wrong.

Yes that would be nice. I think we have a ticket for this somewhere. I
think this should be implemented more generally, for LyX export on the
command line.

Scott


signature.asc
Description: PGP signature

ctests (was: Intro with PDF(luatex))

2016-09-13 Thread Guenter Milde 
Dear Scott,

On 2016-09-12, Scott Kostyshak wrote:

> OK let's both run the full tests after that and compare again to see if
> we have any differences.

I can't run the full tests (no chinese, no japanese, no hebrew, ...; no disk
space, no computer to run all night).

> At least for the normal (e.g. not the suspicious or unreliable) tests we
> are approaching zero. 

Which tests still fail?

The idea is, to add failures that cannot be solved immediately to
"invertedTests" (currently called "suspiciousTests"):

- If the cause is known, under the relevant sublabel.
  (Normally, there is no need for new sublabels - at least not for just
  one pattern.)

- If the cause is not known, under the sublabel TODO
  (Adding the date and git-hash of the first occurence of the failure will
  help in tracking down the cause later.)

This way, it should be easy to reach 0 failing reliable tests. 
(The remaining task will be to clean up the TODO section every now and
than...)

> Once we get there, I think it will be easy to
> maintain.

A big step towards "easy to maintain" will be storing of LaTeX-log output in
the test log. Currently, we always have to "hand-compile" (and in many cases
edit the sources before) to find out what went wrong.

Günter

Re: ctests (was: Intro with PDF(luatex))

2016-09-13 Thread Kornel Benko 
Am Montag, 12. September 2016 um 10:08:24, schrieb Guenter Milde 

> On 2016-09-10, Kornel Benko wrote:
> > Am Samstag, 10. September 2016 um 08:03:37, schrieb Guenter Milde 
> > 
> >> On 2016-09-09, Kornel Benko wrote:
> 
> Dear Kornel,
> 
> >> * Can we rename "suspiciousTests" to "invertedTests", please?
> 
> > Sure. Almost alike the original name has been (revertedTests)
> 
> Fine (especially, as ctests calls the process "inversion").
> 
> 
> >> * Do you still need the "suspendeTests"? What for?
> 
> > Yes, we need them. This tests will not be executed with the call 'ctest
> > -L export'.
> 
> suspendeTests were introduced for the "less urgent" test cases like files in
> the attic and export with Xe/LuaTeX and 8-bit TeX fonts when there were >100
> test errors.

My understanding is that they are suspended because of difficult to solve, 
therefore
we do not try to tests them every time.

> In the meantime, we know the particular problem for most of the suspended
> tests.
> Some were fixed. Others require inversion (we know the problem is a
> wontfix or a bug on trac).
> 
> How many of the suspendedTests are still failing?

73% tests passed, 21 tests failed out of 79 (this means 58 failing)

So, 21 of them could be removed from suspiciousTests.

> Do we really still need the suspension or could we lift it?
> 
> If we want to keep it, it would be important to have a way to clearly define
> tests that are "suspended" AND "inverted".

ATM, we have it. All suspended are inverted.

> Thanks
> Günter

Kornel

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

ctests (was: Intro with PDF(luatex))

2016-09-12 Thread Guenter Milde 
On 2016-09-10, Kornel Benko wrote:
> Am Samstag, 10. September 2016 um 08:03:37, schrieb Guenter Milde 
> 
>> On 2016-09-09, Kornel Benko wrote:

Dear Kornel,

>> * Can we rename "suspiciousTests" to "invertedTests", please?

> Sure. Almost alike the original name has been (revertedTests)

Fine (especially, as ctests calls the process "inversion").


>> * Do you still need the "suspendeTests"? What for?

> Yes, we need them. This tests will not be executed with the call 'ctest
> -L export'.

suspendeTests were introduced for the "less urgent" test cases like files in
the attic and export with Xe/LuaTeX and 8-bit TeX fonts when there were >100
test errors.

In the meantime, we know the particular problem for most of the suspended
tests.
Some were fixed. Others require inversion (we know the problem is a
wontfix or a bug on trac).

How many of the suspendedTests are still failing?
Do we really still need the suspension or could we lift it?

If we want to keep it, it would be important to have a way to clearly define
tests that are "suspended" AND "inverted".

Thanks
Günter