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

2017-03-19 Thread ci-lyx
https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools-extended/111/--
[...truncated 1128 lines...]
  CXX  insets/InsetGraphicsParams.o
  CXX  insets/InsetGraphics.o
  CXX  insets/InsetHyperlink.o
  CXX  insets/InsetInclude.o
  CXX  insets/InsetIndex.o
  CXX  insets/InsetInfo.o
  CXX  insets/InsetIPA.o
  CXX  insets/InsetIPAMacro.o
  CXX  insets/InsetLabel.o
  CXX  insets/InsetLayout.o
  CXX  insets/InsetLine.o
  CXX  insets/InsetListings.o
  CXX  insets/InsetListingsParams.o
  CXX  insets/InsetMarginal.o
  CXX  insets/InsetNewline.o
  CXX  insets/InsetNewpage.o
  CXX  insets/InsetNomencl.o
  CXX  insets/InsetNote.o
  CXX  insets/InsetPhantom.o
  CXX  insets/InsetPreview.o
  CXX  insets/InsetQuotes.o
  CXX  insets/InsetRef.o
  CXX  insets/InsetScript.o
  CXX  insets/InsetSeparator.o
  CXX  insets/InsetSpace.o
  CXX  insets/InsetSpecialChar.o
  CXX  insets/InsetTabular.o
  CXX  insets/InsetText.o
  CXX  insets/InsetTOC.o
  CXX  insets/InsetVSpace.o
  CXX  insets/InsetWrap.o
  AR   liblyxinsets.a
  CXX  main.o
  CXX  BiblioInfo.o
  CXX  Box.o
  CXX  Compare.o
  CXX  Dimension.o
  CXX  EnchantChecker.o
  CXX  PersonalWordList.o
  CXX  LaTeXFonts.o
  CXX  PrinterParams.o
  CXX  Thesaurus.o
  CXXLDlyx
make[4]: Leaving directory '/build/workspace/src'
Making all in client
make[4]: Entering directory '/build/workspace/src/client'
make  all-am
make[5]: Entering directory '/build/workspace/src/client'
  CXX  boost.o
  CXX  client.o
  CXXLDlyxclient
make[5]: Leaving directory '/build/workspace/src/client'
make[4]: Leaving directory '/build/workspace/src/client'
Making all in tex2lyx
make[4]: Entering directory '/build/workspace/src/tex2lyx'
  CXX  boost.o
  CXX  Context.o
  CXX  dummy_impl.o
  CXX  math.o
  CXX  Parser.o
  CXX  Preamble.o
  CXX  table.o
  CXX  tex2lyx.o
  CXX  text.o
  CXXLDtex2lyx
make[4]: Leaving directory '/build/workspace/src/tex2lyx'
make[3]: Leaving directory '/build/workspace/src'
make[2]: Leaving directory '/build/workspace/src'
Making all in sourcedoc
make[2]: Entering directory '/build/workspace/sourcedoc'
make[2]: Nothing to be done for 'all'.
make[2]: Leaving directory '/build/workspace/sourcedoc'
Making all in lib
make[2]: Entering directory '/build/workspace/lib'
Making all in doc
make[3]: Entering directory '/build/workspace/lib/doc'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/build/workspace/lib/doc'
Making all in lyx2lyx
make[3]: Entering directory '/build/workspace/lib/lyx2lyx'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/build/workspace/lib/lyx2lyx'
make[3]: Entering directory '/build/workspace/lib'
  GEN  lyx.desktop
  GEN  lyx.png
  GEN  lyx.svg
make[3]: Leaving directory '/build/workspace/lib'
make[2]: Leaving directory '/build/workspace/lib'
Making all in src/client
make[2]: Entering directory '/build/workspace/src/client'
make  all-am
make[3]: Entering directory '/build/workspace/src/client'
make[3]: Nothing to be done for 'all-am'.
make[3]: Leaving directory '/build/workspace/src/client'
make[2]: Leaving directory '/build/workspace/src/client'
Making all in src/tex2lyx
make[2]: Entering directory '/build/workspace/src/tex2lyx'
make[2]: Nothing to be done for 'all'.
make[2]: Leaving directory '/build/workspace/src/tex2lyx'
make[2]: Entering directory '/build/workspace'
make[2]: Leaving directory '/build/workspace'
make[1]: Leaving directory '/build/workspace'
# Executing: make check
Making check in autotests
make[1]: Entering directory '/build/workspace/autotests'
make[1]: Nothing to be done for 'check'.
make[1]: Leaving directory '/build/workspace/autotests'
Making check in config
make[1]: Entering directory '/build/workspace/config'
make[1]: Nothing to be done for 'check'.
make[1]: Leaving directory '/build/workspace/config'
Making check in development
make[1]: Entering directory '/build/workspace/development'
make[2]: Entering directory '/build/workspace/development'
make[2]: Nothing to be done for 'check-am'.
make[2]: Leaving directory '/build/workspace/development'
make[1]: Leaving directory '/build/workspace/development'
Making check in po
make[1]: Entering directory '/build/workspace/po'
make[1]: Nothing to be done for 'check'.
make[1]: Leaving directory '/build/workspace/po'
Making check in 3rdparty
make[1]: Entering directory '/build/workspace/3rdparty'
make[2]: Entering directory '/build/workspace/3rdparty'
make[2]: Nothing to be done for 'check-am'.
make[2]: Leaving directory '/build/workspace/3rdparty'
make[1]: Leaving directory '/build/workspace/3rdparty'
Making check in src
make[1]: Entering directory '/build/workspace/src'
rm -f hash-temp \
@echo "  GEN  lyx_commit_hash.h";hash=`cd ".." && git log -1 

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

2017-03-19 Thread ci-lyx
https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools-extended-parameterised/4/Changes:

[rgheck] Move the global formats and system_formats variables into the LyX

[lasgouttes] Only accept non-negative lyxscale parameters

--
[...truncated 1122 lines...]
  CXX  insets/InsetGraphicsParams.o
  CXX  insets/InsetGraphics.o
  CXX  insets/InsetHyperlink.o
  CXX  insets/InsetInclude.o
  CXX  insets/InsetIndex.o
  CXX  insets/InsetInfo.o
  CXX  insets/InsetIPA.o
  CXX  insets/InsetIPAMacro.o
  CXX  insets/InsetLabel.o
  CXX  insets/InsetLayout.o
  CXX  insets/InsetLine.o
  CXX  insets/InsetListings.o
  CXX  insets/InsetListingsParams.o
  CXX  insets/InsetMarginal.o
  CXX  insets/InsetNewline.o
  CXX  insets/InsetNewpage.o
  CXX  insets/InsetNomencl.o
  CXX  insets/InsetNote.o
  CXX  insets/InsetPhantom.o
  CXX  insets/InsetPreview.o
  CXX  insets/InsetQuotes.o
  CXX  insets/InsetRef.o
  CXX  insets/InsetScript.o
  CXX  insets/InsetSeparator.o
  CXX  insets/InsetSpace.o
  CXX  insets/InsetSpecialChar.o
  CXX  insets/InsetTabular.o
  CXX  insets/InsetText.o
  CXX  insets/InsetTOC.o
  CXX  insets/InsetVSpace.o
  CXX  insets/InsetWrap.o
  AR   liblyxinsets.a
  CXX  main.o
  CXX  BiblioInfo.o
  CXX  Box.o
  CXX  Compare.o
  CXX  Dimension.o
  CXX  EnchantChecker.o
  CXX  PersonalWordList.o
  CXX  LaTeXFonts.o
  CXX  PrinterParams.o
  CXX  Thesaurus.o
  CXXLDlyx
make[4]: Leaving directory '/build/workspace/src'
Making all in client
make[4]: Entering directory '/build/workspace/src/client'
make  all-am
make[5]: Entering directory '/build/workspace/src/client'
  CXX  boost.o
  CXX  client.o
  CXXLDlyxclient
make[5]: Leaving directory '/build/workspace/src/client'
make[4]: Leaving directory '/build/workspace/src/client'
Making all in tex2lyx
make[4]: Entering directory '/build/workspace/src/tex2lyx'
  CXX  boost.o
  CXX  Context.o
  CXX  dummy_impl.o
  CXX  math.o
  CXX  Parser.o
  CXX  Preamble.o
  CXX  table.o
  CXX  tex2lyx.o
  CXX  text.o
  CXXLDtex2lyx
make[4]: Leaving directory '/build/workspace/src/tex2lyx'
make[3]: Leaving directory '/build/workspace/src'
make[2]: Leaving directory '/build/workspace/src'
Making all in sourcedoc
make[2]: Entering directory '/build/workspace/sourcedoc'
make[2]: Nothing to be done for 'all'.
make[2]: Leaving directory '/build/workspace/sourcedoc'
Making all in lib
make[2]: Entering directory '/build/workspace/lib'
Making all in doc
make[3]: Entering directory '/build/workspace/lib/doc'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/build/workspace/lib/doc'
Making all in lyx2lyx
make[3]: Entering directory '/build/workspace/lib/lyx2lyx'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/build/workspace/lib/lyx2lyx'
make[3]: Entering directory '/build/workspace/lib'
  GEN  lyx.desktop
  GEN  lyx.png
  GEN  lyx.svg
make[3]: Leaving directory '/build/workspace/lib'
make[2]: Leaving directory '/build/workspace/lib'
Making all in src/client
make[2]: Entering directory '/build/workspace/src/client'
make  all-am
make[3]: Entering directory '/build/workspace/src/client'
make[3]: Nothing to be done for 'all-am'.
make[3]: Leaving directory '/build/workspace/src/client'
make[2]: Leaving directory '/build/workspace/src/client'
Making all in src/tex2lyx
make[2]: Entering directory '/build/workspace/src/tex2lyx'
make[2]: Nothing to be done for 'all'.
make[2]: Leaving directory '/build/workspace/src/tex2lyx'
make[2]: Entering directory '/build/workspace'
make[2]: Leaving directory '/build/workspace'
make[1]: Leaving directory '/build/workspace'
# Executing: make check
Making check in autotests
make[1]: Entering directory '/build/workspace/autotests'
make[1]: Nothing to be done for 'check'.
make[1]: Leaving directory '/build/workspace/autotests'
Making check in config
make[1]: Entering directory '/build/workspace/config'
make[1]: Nothing to be done for 'check'.
make[1]: Leaving directory '/build/workspace/config'
Making check in development
make[1]: Entering directory '/build/workspace/development'
make[2]: Entering directory '/build/workspace/development'
make[2]: Nothing to be done for 'check-am'.
make[2]: Leaving directory '/build/workspace/development'
make[1]: Leaving directory '/build/workspace/development'
Making check in po
make[1]: Entering directory '/build/workspace/po'
make[1]: Nothing to be done for 'check'.
make[1]: Leaving directory '/build/workspace/po'
Making check in 3rdparty
make[1]: Entering directory '/build/workspace/3rdparty'
make[2]: Entering directory '/build/workspace/3rdparty'
make[2]: Nothing to be done for 'check-am'.
make[2]: Leaving directory '/build/workspace/3rdparty'
make[1]: Leaving directory '/build/workspace/3rdparty'
Making check 

Some of CI jobs failed due to lack of disk space - now back to normal

2017-03-19 Thread Christian Ridderström
Hi,

Just want to let you know that some of the CI jobs simply failed because
the CI workers ran out of disk space. Some CI jobs take 4 GB, and with no
remaining workdirs from CI jobs, the total disk space per slave is about 20
GB. Anyway, I've done some cleaning and this aspect should be back to
normal now.

If anyone's interested, you can see remaining disk space (_if logged in_)
for the CI workers at this link:
  https://ci.inria.fr/lyx/computer/

/Christian


Re: [LyX/master] Nonsense for whoever insists on using gcc4.6 & qt4.8 in 2017

2017-03-19 Thread Pavel Sanda
Guillaume Munch wrote:
> I chose a big interval because it is only useful for cases where
> QFileSystemWatcher does not work.

That's fine.

> If QFileSystemWatcher works, you see the modification instantly. If it
> does not, you now see it when you activate the window.

Hmm this is not what I see here (gcc 4.9.4 & qt 4.8.5).
I need to scroll or cause some movement so some painting is triggered,
activation of window isn't enough. But at least I know work around.

>> BTW do you think it would be hard to paralelize the load of the figures
>> in the previewer machinery? I have lot of reports with hundreds of figs
>> and loading the document with all figs takes mins while only one of my
>> cores is busy.
>
> I am not familiar enough with this part. Are they graphics or previews?
> If graphics, does increasing s_numimages_ and decreasing s_millisecs_ in
> graphics/GraphicsLoader.cpp help?

No, this will not help. I generally use eps graphics files, so the converter
machinery is triggered and the bottleneck is sequential process inside
ForkedCalls. Long time ago I tried poor man's hack inside callNext routine to
trigger second parallel process which worked in the sense that two parallel
converters were indeed issued but results were taken sometimes from wrong
files so images on screen were mismatched :)

So without touching this, do you see easy way how to trigger some signal
which would issue loading all images in the document, not just on the screen.
I could just call such lfun and let lyx work in backgrounds without managing
it for 5min; even that would be relief...

Pavel


Re: [PATCH] Output of en- and em-dashes

2017-03-19 Thread Guenter Milde
On 2017-03-07, Enrico Forestieri wrote:

> The attached patch fixes the regression introduced in 2.2 about the
> output of en- and em-dashes. 
...
> With this patch, documents produced with older versions work again
> as intended 

Not always:

The proposed patch restores the previous behaviour for the subset of
pre-2.2 documents that used ligature dashes (see Details below).

OTOH, the patch will lead to changed output for older documents using
literal EM DASH and EN DASH characters (that were not affected by the
changes in 2.2) as well as 2.2 documents.

If we are going this way, I propose to make the "ligature dash" output an
opt-in. Otherwise, we replace one evil by another - the LyX update again
causing unwanted changes for existing documents.


More problems with the proposed patch:

a) the setting is lost when converting to 2.2

b) There are older documents using literal dash + ZWSP (U+200b)
   for dash with optional line break point
   (https://marc.info/?l=lyx-users=140982011101908=2)
   With the attached patch, the ZWSP will be removed leading to an unwelcome
   surprise. 



Details
===

In versions < 2.2, there were two methods to input and store em- and
en-dashes:

a) ligature input (--- and --)
b) literal EM DASH and EN DASH characters (0x2014 and 0x2013).

While both methods produce the same characters in the output, they behave
differently regarding possible hyphenation of the preceding word and line
break after the dash. Depending on the use case, both methods have
advantages and problems (see
http://www.lyx.org/trac/raw-attachment/ticket/10543/dash-problems.lyx).

Conversion from 2.1 to 2.2 eliminates the difference between ligature dashes
and literal dashes. In 2.2, dashes are always stored as EM DASH and EN DASH
characters.

So, we have 2 problems:

a) Changed LaTeX export for documents using ligature dashes leading to
   different output in some cases.
   
b) Loss of information during the conversion process.


Alternatives


Further information loss (problem b) can be avoided with a change to
Text.cpp which ensures the distinction of ligature vs. literal dash is kept
during the conversion. Of course, this cannot restore lost information if
converted documents are already modified and saved with 2.2.

--- a/src/Text.cpp
+++ b/src/Text.cpp
@@ -506,9 +506,11 @@ void Text::readParToken(Paragraph & par, Lexer & lex,
par.insert(par.size(), from_ascii("---"), font, 
change);
} else {
if (token == "\\twohyphens")
-   par.insertChar(par.size(), 0x2013, font, 
change);
-   else
-   par.insertChar(par.size(), 0x2014, font, 
change);
+   par.insertChar(par.size(), 0x2013, font, 
change); // EN DASH
+   else {
+   par.insertChar(par.size(), 0x2014, font, 
change); // EM DASH
+   par.insertChar(par.size(), 0x200b, font, 
change); // ZWSP
+   }
}
} else if (token == "\\backslash") {
par.appendChar('\\', font, change);



Alternatively to a buffer setting, we could also take up the suggestion to
define the "ligature dashes" as "special characters":

+1 similar to current support for typographical quotes (special char
   parallel to literal Unicode)
   
+1 enables use of ligature dashes and literal dashes in one document

+1 lyx2lyx conversion of 2.1 and 2.2 documents without behaviour change:
   * replace \twohyphens and \threehyphens with
 dash-special-chars in Text.cpp.
   * keep literal dashes.
   
-1 two competing ways to represent dashes   


Günter



Re: Fwd: adding costum spellchecker to lyx

2017-03-19 Thread Jean-Marc Lasgouttes

Le 19/03/17 à 21:06, kobi kolodner a écrit :

Hi

I would be glad if you did point me in the right direction. It will be
an interesting challenge for me to see this project through. I'm glad to
hear you think the project could be useful


A slightly different idea: one of the spell checking backend used by LyX 
is enchant, which is itself a wrapper around various spellcheckers. You 
could try to implement your spell checker idea in enchant. Then it will 
be automatically available in various programs.


https://www.abisource.com/projects/enchant/
https://github.com/AbiWord/enchant

I think that enchant it again active these days. Probably a good time to 
ask for help.


JMarc


Re: Fwd: adding costum spellchecker to lyx

2017-03-19 Thread kobi kolodner
Hi

I would be glad if you did point me in the right direction. It will be an
interesting challenge for me to see this project through. I'm glad to hear
you think the project could be useful

thank you for answering so quickly

kobi

On Sat, Mar 18, 2017 at 6:35 AM, Scott Kostyshak  wrote:

> On Wed, Mar 15, 2017 at 02:31:45PM +0200, kobi kolodner wrote:
> > Hi
> >
> > I am writing a spellchecker based on google suggestions in python.
> > how can I add it to lyx so it will appear as an option in
> > Tools/Preferences/Language Settings/Spellchecker/Spellchecker engine
> >
> > I am very much a novice in writing code so any help\suggestion even if it
> > seems obvious will be much appreciated
>
> Dear Kobi,
>
> Unless I'm mistaken (Stephan will correct me if so), it's not trivial to
> just add a different spellchecker. You would have to add a significant
> amount of C++ code and recompile. If you're willing to do that, we can
> point you in the right direction.
>
> In the future, I think it would be great for LyX to allow such custom
> spellcheckers. We just don't have that capability at the moment.
>
> Let me also say that your project sounds cool. It is scary to me how
> accurate Google's corrections are. Best of luck with your project!
>
> Scott
>


Re: LyX 2.2 cannot read a document from LyX 2.1?

2017-03-19 Thread Georg Baum
José Abílio Matos wrote:

> On Tuesday, 7 March 2017 12.39.19 WET Enrico Forestieri wrote:
>> > Is this a valid process that we should support?
>> 
>> Given that lyx2lyx processes text files, taking into account that they
>> may have a BOM is safer.

I agree. Some text editors decide to add a BOM to utf8 files, so if a user 
did some expert editing with a text editor this can easily happen.

> OK. So I will try to solve this problem.
> 
>> > If so the following patch fixes this for me, for both python 2 and 3.
>> 
>> I think you can safely commit it.
> 
> I send attached another fix that fixes the file as soon as it is read. I
> am happier with this version.
> 
> Again I tried with python2 and python3 and it works. :-)

Looks fine to me.


Georg



Jenkins build is back to normal : Build branch "master" » ubuntu-xenial-qt4-autotools #104

2017-03-19 Thread ci-lyx
https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools/104/


Re: [PATCH] Output of en- and em-dashes

2017-03-19 Thread Enrico Forestieri
On Sat, Mar 18, 2017 at 05:32:01PM +0100, Enrico Forestieri wrote:
> On Sat, Mar 18, 2017 at 03:41:20PM +, Guenter Milde wrote:
> > On 2017-03-18, Enrico Forestieri wrote:
> > > On Sat, Mar 18, 2017 at 03:06:09PM +0100, Guillaume Munch wrote:
> > 
> > ...
> > 
> > >> > I think we have to make do with the ugly zero-space inset.
> > 
> > >> Or special/invisible unicode characters could be made visible by changing
> > >> the character before painting.
> > 
> > > However, this is going to be an issue only when exporting a document
> > > to previous versions and editing it with that version. So, future
> > > possible workarounds are not going to help.
> > 
> > > It would not be an issue if that character could be searched for, but
> > > this is not possible either. 
> > 
> > How did you test this?
> > I could find a text with ZWSP, if I inserted the ZWSP into the search box
> > from Insert>Special Char>Symbols.
> 
> I mean when searching for a single ZWSP. The "simple" search does not
> work because the find next button is not activated,

This is strange. I found out that copying a ZWSP from the lyx window
to the "simple" search box does not work, but copying it from the
Special Character Symbols (or from an external source) does work.
So, it can be actually searched for and thus I am going to commit the
corresponding patch.

-- 
Enrico


Jenkins build is back to normal : Build branch "master" » ubuntu-xenial-qt4-autotools-extended-parameterised #3

2017-03-19 Thread ci-lyx
https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools-extended-parameterised/3/


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

2017-03-19 Thread ci-lyx
https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools-extended/110/--
[...truncated 1127 lines...]
  CXX  insets/InsetGraphicsParams.o
  CXX  insets/InsetGraphics.o
  CXX  insets/InsetHyperlink.o
  CXX  insets/InsetInclude.o
  CXX  insets/InsetIndex.o
  CXX  insets/InsetInfo.o
  CXX  insets/InsetIPA.o
  CXX  insets/InsetIPAMacro.o
  CXX  insets/InsetLabel.o
  CXX  insets/InsetLayout.o
  CXX  insets/InsetLine.o
  CXX  insets/InsetListings.o
  CXX  insets/InsetListingsParams.o
  CXX  insets/InsetMarginal.o
  CXX  insets/InsetNewline.o
  CXX  insets/InsetNewpage.o
  CXX  insets/InsetNomencl.o
  CXX  insets/InsetNote.o
  CXX  insets/InsetPhantom.o
  CXX  insets/InsetPreview.o
  CXX  insets/InsetQuotes.o
  CXX  insets/InsetRef.o
  CXX  insets/InsetScript.o
  CXX  insets/InsetSeparator.o
  CXX  insets/InsetSpace.o
  CXX  insets/InsetSpecialChar.o
  CXX  insets/InsetTabular.o
  CXX  insets/InsetText.o
  CXX  insets/InsetTOC.o
  CXX  insets/InsetVSpace.o
  CXX  insets/InsetWrap.o
  AR   liblyxinsets.a
  CXX  main.o
  CXX  BiblioInfo.o
  CXX  Box.o
  CXX  Compare.o
  CXX  Dimension.o
  CXX  EnchantChecker.o
  CXX  PersonalWordList.o
  CXX  LaTeXFonts.o
  CXX  PrinterParams.o
  CXX  Thesaurus.o
  CXXLDlyx
make[4]: Leaving directory '/build/workspace/src'
Making all in client
make[4]: Entering directory '/build/workspace/src/client'
make  all-am
make[5]: Entering directory '/build/workspace/src/client'
  CXX  boost.o
  CXX  client.o
  CXXLDlyxclient
make[5]: Leaving directory '/build/workspace/src/client'
make[4]: Leaving directory '/build/workspace/src/client'
Making all in tex2lyx
make[4]: Entering directory '/build/workspace/src/tex2lyx'
  CXX  boost.o
  CXX  Context.o
  CXX  dummy_impl.o
  CXX  math.o
  CXX  Parser.o
  CXX  Preamble.o
  CXX  table.o
  CXX  tex2lyx.o
  CXX  text.o
  CXXLDtex2lyx
make[4]: Leaving directory '/build/workspace/src/tex2lyx'
make[3]: Leaving directory '/build/workspace/src'
make[2]: Leaving directory '/build/workspace/src'
Making all in sourcedoc
make[2]: Entering directory '/build/workspace/sourcedoc'
make[2]: Nothing to be done for 'all'.
make[2]: Leaving directory '/build/workspace/sourcedoc'
Making all in lib
make[2]: Entering directory '/build/workspace/lib'
Making all in doc
make[3]: Entering directory '/build/workspace/lib/doc'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/build/workspace/lib/doc'
Making all in lyx2lyx
make[3]: Entering directory '/build/workspace/lib/lyx2lyx'
make[3]: Nothing to be done for 'all'.
make[3]: Leaving directory '/build/workspace/lib/lyx2lyx'
make[3]: Entering directory '/build/workspace/lib'
  GEN  lyx.desktop
  GEN  lyx.png
  GEN  lyx.svg
make[3]: Leaving directory '/build/workspace/lib'
make[2]: Leaving directory '/build/workspace/lib'
Making all in src/client
make[2]: Entering directory '/build/workspace/src/client'
make  all-am
make[3]: Entering directory '/build/workspace/src/client'
make[3]: Nothing to be done for 'all-am'.
make[3]: Leaving directory '/build/workspace/src/client'
make[2]: Leaving directory '/build/workspace/src/client'
Making all in src/tex2lyx
make[2]: Entering directory '/build/workspace/src/tex2lyx'
make[2]: Nothing to be done for 'all'.
make[2]: Leaving directory '/build/workspace/src/tex2lyx'
make[2]: Entering directory '/build/workspace'
make[2]: Leaving directory '/build/workspace'
make[1]: Leaving directory '/build/workspace'
# Executing: make check
Making check in autotests
make[1]: Entering directory '/build/workspace/autotests'
make[1]: Nothing to be done for 'check'.
make[1]: Leaving directory '/build/workspace/autotests'
Making check in config
make[1]: Entering directory '/build/workspace/config'
make[1]: Nothing to be done for 'check'.
make[1]: Leaving directory '/build/workspace/config'
Making check in development
make[1]: Entering directory '/build/workspace/development'
make[2]: Entering directory '/build/workspace/development'
make[2]: Nothing to be done for 'check-am'.
make[2]: Leaving directory '/build/workspace/development'
make[1]: Leaving directory '/build/workspace/development'
Making check in po
make[1]: Entering directory '/build/workspace/po'
make[1]: Nothing to be done for 'check'.
make[1]: Leaving directory '/build/workspace/po'
Making check in 3rdparty
make[1]: Entering directory '/build/workspace/3rdparty'
make[2]: Entering directory '/build/workspace/3rdparty'
make[2]: Nothing to be done for 'check-am'.
make[2]: Leaving directory '/build/workspace/3rdparty'
make[1]: Leaving directory '/build/workspace/3rdparty'
Making check in src
make[1]: Entering directory '/build/workspace/src'
rm -f hash-temp \
@echo "  GEN  lyx_commit_hash.h";hash=`cd ".." && git log -1 

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

2017-03-19 Thread ci-lyx
https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools/103/--
Started by an SCM change
Building remotely on lyx-linux3 (linux) in workspace 

[WS-CLEANUP] Deleting project workspace...
[WS-CLEANUP] Done
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-parameterised #2

2017-03-19 Thread ci-lyx
https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools-extended-parameterised/2/--
[...truncated 2186 lines...]
  GEN  ui_PrefEditUi.h
  GEN  ui_PrefFileformatsUi.h
  GEN  ui_PrefIdentityUi.h
  GEN  ui_PrefInputUi.h
  GEN  ui_PrefLanguageUi.h
  GEN  ui_PrefLatexUi.h
  GEN  ui_PrefPathsUi.h
  GEN  ui_PrefScreenFontsUi.h
  GEN  ui_PrefShortcutsUi.h
  GEN  ui_PrefSpellcheckerUi.h
  GEN  ui_PrefsUi.h
  GEN  ui_PrefUi.h
  GEN  ui_PrintindexUi.h
  GEN  ui_PrintNomenclUi.h
  GEN  ui_ProgressViewUi.h
  GEN  ui_RefUi.h
  GEN  ui_SearchUi.h
  GEN  ui_SendtoUi.h
  GEN  ui_ShortcutUi.h
  GEN  ui_ShowFileUi.h
  GEN  ui_SpellcheckerUi.h
  GEN  ui_SymbolsUi.h
  GEN  ui_TabularCreateUi.h
  GEN  ui_TabularUi.h
  GEN  ui_TexinfoUi.h
  GEN  ui_TextLayoutUi.h
  GEN  ui_ThesaurusUi.h
  GEN  ui_TocUi.h
  GEN  ui_ToggleWarningUi.h
  GEN  ui_ViewSourceUi.h
  GEN  ui_VSpaceUi.h
  GEN  ui_WorkAreaUi.h
  GEN  ui_WrapUi.h
  GEN  moc_Action.cpp
  GEN  moc_BulletsModule.cpp
  GEN  moc_CategorizedCombo.cpp
  GEN  moc_CustomizedWidgets.cpp
  GEN  moc_DialogView.cpp
  GEN  moc_DockView.cpp
  GEN  moc_EmptyTable.cpp
  GEN  moc_FancyLineEdit.cpp
  GEN  moc_FindAndReplace.cpp
  GEN  moc_FloatPlacement.cpp
  GEN  moc_GuiAbout.cpp
  GEN  moc_GuiApplication.cpp
  GEN  moc_GuiBibitem.cpp
  GEN  moc_GuiBibtex.cpp
  GEN  moc_GuiBox.cpp
  GEN  moc_GuiBranches.cpp
  GEN  moc_GuiBranch.cpp
  GEN  moc_GuiChanges.cpp
  GEN  moc_GuiCharacter.cpp
  GEN  moc_GuiCitation.cpp
  GEN  moc_GuiClipboard.cpp
  GEN  moc_GuiCommandBuffer.cpp
  GEN  moc_GuiCommandEdit.cpp
  GEN  moc_GuiCompare.cpp
  GEN  moc_GuiCompareHistory.cpp
  GEN  moc_GuiCompleter.cpp
  GEN  moc_GuiDelimiter.cpp
  GEN  moc_GuiDialog.cpp
  GEN  moc_GuiDocument.cpp
  GEN  moc_GuiErrorList.cpp
  GEN  moc_GuiERT.cpp
  GEN  moc_GuiExternal.cpp
  GEN  moc_GuiGraphics.cpp
  GEN  moc_GuiHSpace.cpp
  GEN  moc_GuiHyperlink.cpp
  GEN  moc_GuiInclude.cpp
  GEN  moc_GuiIndex.cpp
  GEN  moc_GuiIndices.cpp
  GEN  moc_GuiInfo.cpp
  GEN  moc_GuiLabel.cpp
  GEN  moc_GuiLine.cpp
  GEN  moc_GuiListings.cpp
  GEN  moc_GuiLog.cpp
  GEN  moc_GuiMathMatrix.cpp
  GEN  moc_GuiNomenclature.cpp
  GEN  moc_GuiNote.cpp
  GEN  moc_GuiParagraph.cpp
  GEN  moc_GuiPhantom.cpp
  GEN  moc_GuiPrefs.cpp
  GEN  moc_GuiPrintindex.cpp
  GEN  moc_GuiPrintNomencl.cpp
  GEN  moc_GuiProgress.cpp
  GEN  moc_GuiProgressView.cpp
  GEN  moc_GuiRef.cpp
  GEN  moc_GuiSearch.cpp
  GEN  moc_GuiSelection.cpp
  GEN  moc_GuiSelectionManager.cpp
  GEN  moc_GuiSendto.cpp
  GEN  moc_GuiSetBorder.cpp
  GEN  moc_GuiShowFile.cpp
  GEN  moc_GuiSpellchecker.cpp
  GEN  moc_GuiSymbols.cpp
  GEN  moc_GuiTabularCreate.cpp
  GEN  moc_GuiTabular.cpp
  GEN  moc_GuiTexinfo.cpp
  GEN  moc_GuiThesaurus.cpp
  GEN  moc_GuiToc.cpp
  GEN  moc_GuiToolbar.cpp
  GEN  moc_GuiView.cpp
  GEN  moc_GuiViewSource.cpp
  GEN  moc_GuiVSpace.cpp
  GEN  moc_GuiWorkArea.cpp
  GEN  moc_GuiWrap.cpp
  GEN  moc_IconPalette.cpp
  GEN  moc_InGuiThread.cpp
  GEN  moc_InsertTableWidget.cpp
  GEN  moc_InsetParamsDialog.cpp
  GEN  moc_InsetParamsWidget.cpp
  GEN  moc_LayoutBox.cpp
  GEN  moc_LengthCombo.cpp
  GEN  moc_LyXFileDialog.cpp
  GEN  moc_Menus.cpp
  GEN  moc_PanelStack.cpp
  GEN  moc_TocModel.cpp
  GEN  moc_TocWidget.cpp
  GEN  moc_ToolTipFormatter.cpp
  GEN  moc_Validator.cpp
  GEN  Resources.qrc
  GEN  Resources.cpp
make  all-am
make[7]: Entering directory 
'/build/workspace/lyx-2.3.0dev/_build/sub/src/frontends/qt4'
  CXX  ButtonPolicy.o
  CXX  Dialog.o
  CXX  Action.o
  CXX  BulletsModule.o
  CXX  ButtonController.o
  CXX  CategorizedCombo.o
  CXX  ColorCache.o
  CXX  CustomizedWidgets.o
  CXX  DialogView.o
  CXX  DockView.o
  CXX  EmptyTable.o
  CXX  FancyLineEdit.o
  CXX  FileDialog.o
  CXX  FindAndReplace.o
  CXX  FloatPlacement.o
  CXX  GuiAbout.o
  CXX  GuiAlert.o
  CXX  GuiApplication.o
  CXX  GuiBibitem.o
  CXX  GuiBibtex.o
  CXX  GuiBox.o
  CXX  GuiBranch.o
  CXX  GuiBranches.o
  CXX  GuiChanges.o
  CXX  GuiCharacter.o
  CXX  GuiCitation.o
  CXX  GuiClipboard.o
  CXX  GuiCommandBuffer.o
  CXX  GuiCommandEdit.o
  CXX  GuiCompare.o
  CXX  GuiCompareHistory.o
  CXX  GuiCompleter.o
  CXX  GuiDelimiter.o
  CXX  GuiDialog.o
  CXX  GuiDocument.o
  CXX  GuiErrorList.o
  CXX  GuiERT.o
  CXX  GuiExternal.o
  CXX  GuiFontExample.o
  CXX  GuiFontLoader.o
  CXX  GuiFontMetrics.o
  

Re: [LyX/master] Nonsense for whoever insists on using gcc4.6 & qt4.8 in 2017

2017-03-19 Thread Guillaume Munch

Le 11/03/2017 à 20:16, Pavel Sanda a écrit :

Guillaume Munch wrote:

On the other hand, for graphics, the
idea of the previous FileMonitor could be adapted to refresh graphics
when they appear on the screen


Perhaps. But it should do that when window gets active (we already catch that
signal for redrawing graphics).
Typical scenario I am in: plotting routine in terminal window changes figs
and I want to see them updated after I switch from terminal back to lyx.


It now checks for modifications using timestamp and checksum whenever
drawn (asynchronously) but not more than once every 10s.

I chose a big interval because it is only useful for cases where
QFileSystemWatcher does not work.

If QFileSystemWatcher works, you see the modification instantly. If it
does not, you now see it when you activate the window.





(but stop doing it when they leave the screen).


Of course, there is no reason for that.


Well, this is what the old code was doing.




In that case, I even wonder whether it is useful to use the file
monitor for graphics files.


It seems to me safer still use them, but don't have strong opinion.

BTW do you think it would be hard to paralelize the load of the figures
in the previewer machinery? I have lot of reports with hundreds of figs
and loading the document with all figs takes mins while only one of my
cores is busy.


I am not familiar enough with this part. Are they graphics or previews?
If graphics, does increasing s_numimages_ and decreasing s_millisecs_ in
graphics/GraphicsLoader.cpp help?


Guillaume



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

2017-03-19 Thread Guillaume Munch

Le 19/03/2017 à 13:17, ci-...@inria.fr a écrit :

Making distclean in .
make[3]: Entering directory '/build/workspace/lyx-2.3.0dev/_build/sub/src'
Makefile:2455: support/tests/.deps/check_ExternalTransforms-dummy_functions.Po: 
No such file or directory
Makefile:2456: support/tests/.deps/check_Length-dummy_functions.Po: No such 
file or directory
Makefile:2457: support/tests/.deps/check_ListingsCaption-dummy_functions.Po: No 
such file or directory
Makefile:2458: support/tests/.deps/check_layout-dummy_functions.Po: No such 
file or directory
make[3]: *** No rule to make target 
'support/tests/.deps/check_layout-dummy_functions.Po'.  Stop.


distclean has been broken here for some time, with the same messages.



Re: Is this a valid .lyx file (created by 2.0.8.1)?

2017-03-19 Thread José Abílio Matos
On Wednesday, 15 March 2017 19.06.07 WET Scott Kostyshak wrote:
> Attached is a minimal example from here:
> 
> http://tex.stackexchange.com/questions/358326/my-font-shows-up-in-the-font-l
> ist-but-the-document-wont-compile
> 
> It was created with 2.0.8.1.
> 
> When I open it in 2.1.0 or 2.2.x I get:
> 
> Warning: Malformed LyX document: Can't find \use_mathdots.
> Warning: Malformed LyX document: Missing \suppress_date.
> Warning: Malformed LyX document: Can't find \use_package.
> Warning: Malformed LyX document: Can't find \use_package amsmath.
> Warning: Malformed LyX document: Can't find \use_package.
> Warning: Malformed LyX document: Can't find \use_package.
> Warning: Malformed LyX document: Can't find \use_package.
> Warning: Malformed LyX document: No \font_sf_scale!
> Warning: Malformed LyX document: No \font_tt_scale!
> 
> Is the document indeed malformed or is there possibly a bug in lyx2lyx?
> 
> Scott

As Enrico said usually lyx generated files have a larger header. So if this 
file has been produced by lyx it is not in its pristine form.

With that said we could probably improve the warnings.

One example is when there is a new file format change that introduces new 
header elements. The corresponding lyx2lyx change should add those headers 
with the default values. I am not sure that we do this for all those cases.

What happens when lyx reads a file where those headers are not present is to 
assume the default values. It happens sometimes that we change the default 
values between major versions, a file that has the headers set is immune to 
the change in the default values because those only apply to new files.

One other problem with labeling this files as malformed is that there are 
several levels of malformed, from the the minor warning to the case where lyx 
is not able to read the file.

OK, that is all for the little rambling that I had one this issue. Thanks for 
reading it. :-)

Regards,
-- 
José Abílio


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

2017-03-19 Thread ci-lyx
https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-xenial-qt4-autotools-extended-parameterised/1/--
[...truncated 4887 lines...]
-exec chmod u+rwx,go+rx {} \; -o \
  ! -type d ! -perm -444 -links 1 -exec chmod a+r {} \; -o \
  ! -type d ! -perm -400 -exec chmod a+r {} \; -o \
  ! -type d ! -perm -444 -exec /bin/bash 
/build/workspace/lyx-2.3.0dev/config/install-sh -c -m a+r {} {} \; \
|| chmod -R a+r "lyx-2.3.0dev"
tardir=lyx-2.3.0dev && tar --format=ustar -chf - "$tardir" | BZIP2=${BZIP2--9} 
bzip2 -c >lyx-2.3.0dev.tar.bz2
tardir=lyx-2.3.0dev && tar --format=ustar -chf - "$tardir" | GZIP=--best gzip 
-c >lyx-2.3.0dev.tar.gz
make[2]: Leaving directory '/build/workspace/lyx-2.3.0dev/_build/sub'
if test -d "lyx-2.3.0dev"; then find "lyx-2.3.0dev" -type d ! -perm -200 -exec 
chmod u+w {} ';' && rm -rf "lyx-2.3.0dev" || { sleep 5 && rm -rf 
"lyx-2.3.0dev"; }; else :; fi
make[1]: Leaving directory '/build/workspace/lyx-2.3.0dev/_build/sub'
make[1]: Entering directory '/build/workspace/lyx-2.3.0dev/_build/sub'
Making distclean in 3rdparty
make[2]: Entering directory '/build/workspace/lyx-2.3.0dev/_build/sub/3rdparty'
Making distclean in boost
make[3]: Entering directory 
'/build/workspace/lyx-2.3.0dev/_build/sub/3rdparty/boost'
test -z "liblyxboost.a" || rm -f liblyxboost.a
rm -f *.o
rm -f libs/regex/src/*.o
rm -f *.tab.c
test -z "" || rm -f 
test . = "../../../../3rdparty/boost" || test -z "" || rm -f 
rm -f libs/regex/src/.deps/.dirstamp
rm -f libs/regex/src/.dirstamp
test -z "*.orig *.rej *~ *.bak core" || rm -f *.orig *.rej *~ *.bak core
rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
rm -rf ./.deps libs/regex/src/.deps
rm -f Makefile
make[3]: Leaving directory 
'/build/workspace/lyx-2.3.0dev/_build/sub/3rdparty/boost'
Making distclean in hunspell
make[3]: Entering directory 
'/build/workspace/lyx-2.3.0dev/_build/sub/3rdparty/hunspell'
test -z "liblyxhunspell.a" || rm -f liblyxhunspell.a
rm -f *.o
rm -f 1.3.3/src/hunspell/*.o
rm -f 1.3.3/src/parsers/*.o
rm -f *.tab.c
test -z "" || rm -f 
test . = "../../../../3rdparty/hunspell" || test -z "" || rm -f 
rm -f 1.3.3/src/hunspell/.deps/.dirstamp
rm -f 1.3.3/src/hunspell/.dirstamp
rm -f 1.3.3/src/parsers/.deps/.dirstamp
rm -f 1.3.3/src/parsers/.dirstamp
test -z "*.orig *.rej *~ *.bak core" || rm -f *.orig *.rej *~ *.bak core
rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
rm -rf 1.3.3/src/hunspell/.deps 1.3.3/src/parsers/.deps
rm -f Makefile
make[3]: Leaving directory 
'/build/workspace/lyx-2.3.0dev/_build/sub/3rdparty/hunspell'
Making distclean in mythes
make[3]: Entering directory 
'/build/workspace/lyx-2.3.0dev/_build/sub/3rdparty/mythes'
test -z "liblyxmythes.a" || rm -f liblyxmythes.a
rm -f *.o
rm -f 1.2.5/*.o
rm -f *.tab.c
test -z "" || rm -f 
test . = "../../../../3rdparty/mythes" || test -z "" || rm -f 
rm -f 1.2.5/.deps/.dirstamp
rm -f 1.2.5/.dirstamp
test -z "*.orig *.rej *~ *.bak core" || rm -f *.orig *.rej *~ *.bak core
rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
rm -rf 1.2.5/.deps
rm -f Makefile
make[3]: Leaving directory 
'/build/workspace/lyx-2.3.0dev/_build/sub/3rdparty/mythes'
Making distclean in libiconv
make[3]: Entering directory 
'/build/workspace/lyx-2.3.0dev/_build/sub/3rdparty/libiconv'
test -z "liblyxiconv.a" || rm -f liblyxiconv.a
rm -f *.o
rm -f 1.14/lib/*.o
rm -f 1.14/libcharset/lib/*.o
rm -f *.tab.c
test -z "" || rm -f 
test . = "../../../../3rdparty/libiconv" || test -z "" || rm -f 
rm -f 1.14/lib/.deps/.dirstamp
rm -f 1.14/lib/.dirstamp
rm -f 1.14/libcharset/lib/.deps/.dirstamp
rm -f 1.14/libcharset/lib/.dirstamp
test -z "*.orig *.rej *~ *.bak core" || rm -f *.orig *.rej *~ *.bak core
rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
rm -rf 1.14/lib/.deps 1.14/libcharset/lib/.deps
rm -f Makefile
make[3]: Leaving directory 
'/build/workspace/lyx-2.3.0dev/_build/sub/3rdparty/libiconv'
Making distclean in zlib
make[3]: Entering directory 
'/build/workspace/lyx-2.3.0dev/_build/sub/3rdparty/zlib'
test -z "liblyxzlib.a" || rm -f liblyxzlib.a
rm -f *.o
rm -f 1.2.8/*.o
rm -f *.tab.c
test -z "" || rm -f 
test . = "../../../../3rdparty/zlib" || test -z "" || rm -f 
rm -f 1.2.8/.deps/.dirstamp
rm -f 1.2.8/.dirstamp
test -z "*.orig *.rej *~ *.bak core" || rm -f *.orig *.rej *~ *.bak core
rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
rm -rf 1.2.8/.deps
rm -f Makefile
make[3]: Leaving directory 
'/build/workspace/lyx-2.3.0dev/_build/sub/3rdparty/zlib'
make[3]: Entering directory '/build/workspace/lyx-2.3.0dev/_build/sub/3rdparty'
test -z "" || rm -f 
test . = "../../../3rdparty" || test -z "" || rm -f 
test -z "*.orig *.rej *~ *.bak core" || rm -f *.orig *.rej *~ *.bak core
rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
make[3]: Leaving directory '/build/workspace/lyx-2.3.0dev/_build/sub/3rdparty'
rm -f Makefile
make[2]: Leaving directory '/build/workspace/lyx-2.3.0dev/_build/sub/3rdparty'
Making distclean in autotests
make[2]: Entering directory '/build/workspace/lyx-2.3.0dev/_build/sub/autotests'
test -z "" 

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

2017-03-19 Thread Jean-Marc Lasgouttes
Yes, it is probably the reason : this patch has moved the dummy functions file 
around. It is probably possible to fix it, though.

JMarc

Le 19 mars 2017 12:26:23 GMT+01:00, "Christian Ridderström"  a 
écrit :
>On 19 March 2017 at 12:14, Christian Ridderström  wrote:
>
>>
>> But I think someone should take a log at the error output and see if
>they
>> can figure out why it's breaking, I think it's a real breakage.
>>
>
>Could perhaps the following line in the CI job's configuration be
>related...:
>
># Temporary fix: Apply JMarc's patch to allow 'make distcheck' to
>complete
>patch -p1 <
>/builds/0001-Fix-distclean-for-recent-automake-versions.patch
>
>
>Jean-Marc, perhaps that patch should no longer be applied?  It was
>needed
>earlier to make the checks pass.
>I've created another CI job that's not applying that patch and that's
>currently running, so we'll see what happens.
>/Christian


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

2017-03-19 Thread Christian Ridderström
On 19 March 2017 at 12:14, Christian Ridderström  wrote:

>
> But I think someone should take a log at the error output and see if they
> can figure out why it's breaking, I think it's a real breakage.
>

Could perhaps the following line in the CI job's configuration be
related...:

# Temporary fix: Apply JMarc's patch to allow 'make distcheck' to complete
patch -p1 < /builds/0001-Fix-distclean-for-recent-automake-versions.patch


Jean-Marc, perhaps that patch should no longer be applied?  It was needed
earlier to make the checks pass.
I've created another CI job that's not applying that patch and that's
currently running, so we'll see what happens.
/Christian


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

2017-03-19 Thread Christian Ridderström
On 18 March 2017 at 22:20, Christian Ridderström  wrote:

> Christian, does the check start from a fresh tree? If you do 'make
>>> clean' and the rules have changed, it might be that some .o files remain
>>> at the wrong place
>>>
>>
>> I think most CI jobs are configured to start from a completely empty work
>> folders.
>>
>
> I checked just now by looking here (you may have to be logged in):
>https://ci.inria.fr/lyx/job/build-master-head/job/ubuntu-
> xenial-qt4-autotools-extended/configure
> and under the section
>Build environment
> the setting
>Delete workspace before build starts
> is checked...  So the build really should be starting from a clean slate.
>

The build still fails, so I don't think it's related to the build process...
I'm going to see if I can set up a CI job for "parametrised build", where
it's possible to provide e.g. the commit hash. We can then go back and
re-build "#104" to confirm that commit build. Then we can step forward and
see where it breaks.

But I think someone should take a log at the error output and see if they
can figure out why it's breaking, I think it's a real breakage.
/Christian