On 2016-10-08, Scott Kostyshak wrote: > [-- Type: text/plain, Encoding: quoted-printable --]
> On Sat, Oct 08, 2016 at 06:37:53PM +0100, Jean-Pierre Chrétien wrote: >> Hello, >> I've setup the test machinery on my Debian Jessie, TeXLive 2016: >> * ran automake in /ext/lyx/master >> * ran cmake on Debian Jessie in /ext/lyx/cbuildmaster as >> /ext/lyx/cbuildmaster$ cmake -DLYX_ENABLE_EXPORT_TESTS=ON -DLYX_RELEASE=ON >> -DLYX_PROGRAM_SUFFIX=ON -DLYX_ENABLE_CXX11=AUTO -DLYX_USE_QT=QT5 >> -DLYX_INSTALL_PREFIX="git-" ../master >> * ran make >> For a first try, I ran cmake -R 'seminar*' to check recent improvements with >> the seminar example file, and I get the attached result. >> What surprises me is that >> - the English version of seminar.lyx is not tested for all output formats; >> - the French one fails for dvi3, pdf4 and pdf5, that is for dvi (LuaTeX), >> pdf (XeTeX) and pdf (LuaTeX), for both fonts. > This has to do with whether the "Default output format" is set. > If I set it back to "default", and rerun cmake and then rerun the tests, > then all of the tests pass. This makes me think we should change the > format back to default. Günter do you have an opinion on this? The default output format setting is intended. Seminar does not work sensibly with DVI (except for landscape slides) and requires different settings for different output formats, thus * it is advisable to set an output format in the document (and therefore a good to do this in the example). * it does not make sense to test for formats we know to result in wrong output. >> Running exports manually, I find that >> - there is no failure for the texF tests (TeX fonts) >> - the compilation with systemF tests fails with message: >> Missing character: There is no ✗ in font >> [lmroman10-regular]:mapping=tex-text! >> The manual export of the original English seminar.lyx file (not tested by >> ctest, as said) fails also with the same message, so this looks like a >> missing font in my installation. This is expected: with TeX fonts, the ✗ is taken from a symbols package loaded by request from "unicodesymbols". With Unicode fonts, we would need to change the font to e.g. FreeSerif etc. >> So manually there are 3 false alarms, but I must say also that the texF >> tests did fail once in a weird manner which I cannot reproduce: I got and >> error looking like polyglossia language change error, but with no error >> showing in the log window. (however, there cannot be a polyglossia error with texF, as polyglossia requires fontspec (i.e. Unicode fonts)). >> This is a bit mysterious but could explain the ctest failures. Is >> there somwhere a log of the test compilation (or an option to activate >> it?). Unfortunately not (yet). Günter
