On Sun, Jan 28, 2018 at 12:31 AM, Rene Engelhard <rene@debian.org> wrote:
On Sat, Jan 27, 2018 at 06:20:04PM +0100, Rene Engelhard wrote:
On Mon, Jan 22, 2018 at 09:03:06PM +0000, Luke Benes wrote:
The previous log was heavily trimmed to reduce size. While the OS is different both builds
share the same external drive. Could the path length be a problem? (I trimmed the full path in
the previous log) Or could this be like the "Unit test PythonTest_solenv_python failing on
est_gbuildtojson" issue where a make clean isn't enough and I have to manually remove some
file from the source tree?
That one was "gpg creates files the test could not handle". This
supposedly is different, though but I just saw this on
https://buildd.debian.org/status/fetch.php?pkg=libreoffice&arch=all&ver=1%3A6.0.0~rc3-1&stamp=1517070858&raw=0.
A clean build.
That said, it seems to have been successful in the i386 build:
https://buildd.debian.org/status/fetch.php?pkg=libreoffice&arch=i386&ver=1%3A6.0.0~rc3-1&stamp=1517067740&raw=0
No, it was failed too:
SigningTest::testODFBrokenDsigGPG finished in: 222ms
/<<PKGBUILDDIR>>/unotest/source/cpp/macros_test.cxx:52:SigningTest::testODFEncryptedGPG
assertion failed
- Expression: xComponent.is()
- loading failed:
file:///<<PKGBUILDDIR>>//xmlsecurity/qa/unit/signing/data/encryptedGPG.odt
SigningTest::testODFEncryptedGPG finished in: 34ms
macros_test.cxx:52:Assertion
Test name: SigningTest::testODFEncryptedGPG
assertion failed
- Expression: xComponent.is()
- loading failed:
file:///<<PKGBUILDDIR>>//xmlsecurity/qa/unit/signing/data/encryptedGPG.odt
Failures !!!
Run: 24 Failure total: 1 Failures: 1 Errors: 0
Context
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.