Build failed in Jenkins: Build branch "master" » ubuntu-xenial-qt4-autotools-extended #1136

[ci-lyx]

https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools-extended/1136/--
Started by an SCM change
Building remotely on lyx-linux1 (linux) in workspace 

[WS-CLEANUP] Deleting project workspace...
java.io.IOException: Failed to mkdirs: 

at hudson.FilePath.mkdirs(FilePath.java:1191)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1267)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529)
at hudson.model.Run.execute(Run.java:1741)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:410)

Build failed in Jenkins: Build branch "master" » ubuntu-xenial-qt4-autotools-extended #1135

[ci-lyx]

https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools-extended/1135/--
Started by an SCM change
Building remotely on lyx-linux1 (linux) in workspace 

[WS-CLEANUP] Deleting project workspace...
java.io.IOException: Failed to mkdirs: 

at hudson.FilePath.mkdirs(FilePath.java:1191)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1267)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529)
at hudson.model.Run.execute(Run.java:1741)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:410)

Re: Debugging LyX server on Windows

[Will S]

On Tue, Aug 7, 2018 at 12:22 PM Enrico Forestieri  wrote:

>
> No, this seems to be an issue introduced in recent versions of Windows.
> When an overlapped write operation to a pipe is in progress, GetLastError()
> used returning ERROR_IO_PENDING while now it seems to also return NO_ERROR.
> This was confusing the software so that the scheduled replies were never
> actually output. Should be now fixed in master at cf5f2661.
>

Thanks for all the responses. I am interested to see if cf5f2661 fixes the
issue for the affected users, but they are not prepared to compile LyX from
source. How often are pre-release versions built? Just shortly before the
next release?

Build failed in Jenkins: Build branch "master" » ubuntu-xenial-qt4-autotools-extended #1134

[ci-lyx]

https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools-extended/1134/--
Started by an SCM change
Building remotely on lyx-linux1 (linux) in workspace 

[WS-CLEANUP] Deleting project workspace...
java.io.IOException: Failed to mkdirs: 

at hudson.FilePath.mkdirs(FilePath.java:1191)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1267)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529)
at hudson.model.Run.execute(Run.java:1741)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:410)

Re: Micro-typographic extension error

[Guenter Milde]

On 2018-08-10, Daniel wrote:
> On 10/08/2018 11:27, Kornel Benko wrote:
>> Am Freitag, 10. August 2018 10:32:18 CEST schrieb Daniel :
>>> With the attached document on generating output I get a

>>> pdfTeX error (font expansion): auto expansion is only possible with
>>> scalable [fonts.]

>>> It disappears when I disable the micro-typographic extension. I get the
>>> error on Windows 10 (official installer 2.3.0). Scott couldn't reproduce
>>> with his system (I guess Ubuntu 18.04).

>>> Daniel


>> The difference may lay on the font used on your platform.
>> The font in this doc is set to 'Default'. Try to select a different
>> font, like 'TeX Gyre'.

> That works. Since it doesn't even work with the default font on Windows, 
> maybe it is worth mentioning in the Fonts Dialog that the 
> micro-typographic extensions works only with certain fonts. Maybe show a 
> message box that the user has to OK or so.

It does not work with the default fonts on every system, because the LyX
defaults select a bitmap font.
See https://www.lyx.org/trac/ticket/9741 for details.

Günter