Re: DesktopLOKTest::testRedlineWriter is failing

David Ostrovsky <d.ostrovsky -AT- gmx.de>
Fri, 02 Jun 2017 06:59:02 +0200

On Thu Jun 1 07:30:13 UTC 2017, Stephan Bergmann wrote:

On 06/01/2017 08:37 AM, David Ostrovsky wrote:
It didn't fix it, unfortunately. I will check whether building
against internal boost version helps.


what's the output of 'locale' in the shell where you do all that 
building/testing?


http://paste.openstack.org/show/611267

Context

DesktopLOKTest::testRedlineWriter is failing · David Ostrovsky
- Re: DesktopLOKTest::testRedlineWriter is failing · Miklos Vajna
- Re: DesktopLOKTest::testRedlineWriter is failing · David Ostrovsky
- Re: DesktopLOKTest::testRedlineWriter is failing · Stephan Bergmann
- Re: DesktopLOKTest::testRedlineWriter is failing · David Ostrovsky
  - Re: DesktopLOKTest::testRedlineWriter is failing · Stephan Bergmann
  - Re: DesktopLOKTest::testRedlineWriter is failing · David Ostrovsky
    - Re: DesktopLOKTest::testRedlineWriter is failing · Stephan Bergmann
- Re: DesktopLOKTest::testRedlineWriter is failing · Tomáš Chvátal
  - Re: DesktopLOKTest::testRedlineWriter is failing · Stephan Bergmann
    - Re: DesktopLOKTest::testRedlineWriter is failing · Tomáš Chvátal
      - Re: DesktopLOKTest::testRedlineWriter is failing · Stephan Bergmann
        
        Re: DesktopLOKTest::testRedlineWriter is failing · Tomáš Chvátal
        
        Re: DesktopLOKTest::testRedlineWriter is failing · Stephan Bergmann

Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.