On 2017-08-20, Christian Ridderström wrote: > Guenter Milde <mi...@users.sf.net> writes: >> On 2017-08-11, Christian Ridderström wrote: >>> On 11 August 2017 at 13:03, Pavel Sanda <sa...@lyx.org> wrote: >>>> Christian Ridderström wrote:
>>>> > [*] It might make sense to have a CI job that builds PDFs etc from the >>>> > manuals as a separate test. ... > Some months ago I created a CI job that runs (some of?) the tests. ... > Due to the many tests failing it didn't seem so useful to deploy. > Here's the (presumably) relevant line from the log: > 68% tests passed, 2073 tests failed out of 6522 This warrants a look into the test setup, but may be no problem if the very small subset of tests exporting documentation to the default output format works fine. However, ... > From there I then navigated to e.g. > > https://ci.inria.fr/lyx/job/testing-Jenkins/job/ctest/ws/build/autotests/out-home/sv/splash_defaultF.pdf3 > I was able to download that file and view it, although my mac required > me (!!!???) to first rename the extension from .pdf3 to .pdf, even when > I tried to launch 'Preview' on the file from the command line. We would need to: * select the *.pdf2 (PDF(pdflatex) files matching the manuals and rename them to *.pdf * select required graphic files * move them into a sensible directory hierarchy All in all, it seems simpler to keep the documentation generation as a separate task. Günter
