On 10/03/18 19:53, Luke Benes wrote:
https://gerrit.libreoffice.org/#/c/50978/ - can you try if that fixes your
issue?
Unfortunately, the build is still failing with this patch. Do you want anything
from the logs?
That matches my understanding (as expressed in the gerrit change), that,
to
> https://gerrit.libreoffice.org/#/c/50978/ - can you try if that fixes your
> issue?
Unfortunately, the build is still failing with this patch. Do you want anything
from the logs?
To reproduce this yourself, you can copy your source tree to a folder as deep
as mine. As I said earlier, by co
I wrote:
> I'll mull over if we can somehow prevent that for this test...
>
https://gerrit.libreoffice.org/#/c/50978/ - can you try if that fixes
your issue?
Cheers,
-- Thorsten
signature.asc
Description: Digital signature
___
LibreOffice mailing lis
Hi Luke,
this one indeed clears it up:
Luke Benes wrote:
> [pid 24144] write(2, "gpg: can't connect to the agent: File name too
> long", 51) = 51
>
This is quite unexpected. There's a thread about it on the upstream
gpg list:
https://lists.gt.net/gnupg/users/79522
I'll mull over if we can someh
On 08.03.2018 04:59, Luke Benes wrote:
> Sorry, copy/paste error. Here is the correct URL:
>
> https://gist.githubusercontent.com/slacka/412bea7ad1012cb60dac6af583712736/raw/3b8309b7a5dd568c35eb6758edbb15e771e290d2/strace2.txt
>
> [pid 24144] write(2, "gpg: can't connect to the agent: File name
Sorry, copy/paste error. Here is the correct URL:
https://gist.githubusercontent.com/slacka/412bea7ad1012cb60dac6af583712736/raw/3b8309b7a5dd568c35eb6758edbb15e771e290d2/strace2.txt
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://l
Here is the updated strace log:
https://gist.githubusercontent.com/slacka/412bea7ad1012cb60dac6af583712736/raw/3b8309b7a5dd568c35eb6758edbb15e771e290d2/strace2.
Made with $ make CppunitTest_xmlsecurity_signing CPPUNITTRACE="strace -f -s 77"
2>&1 | tee trace.log
Let me know if there's anything
On 07.03.2018 01:10, Luke Benes wrote:
> Here is the strace log:
>
> https://gist.githubusercontent.com/slacka/a07fac3b1ab0396df066968e2e216c8d/raw/6e1b1414b9db9da04a306a00dd27e1446f9e1377/strace.txt
>
> Let me know if there's anything else I can do to help.
gpg fails with:
[pid 19515] write(2,
Here is the strace log:
https://gist.githubusercontent.com/slacka/a07fac3b1ab0396df066968e2e216c8d/raw/6e1b1414b9db9da04a306a00dd27e1446f9e1377/strace.txt
Let me know if there's anything else I can do to help.
___
LibreOffice mailing list
LibreOffice@li
One more clue as to what is going on. I copied the source tree from my external
HD to my home folder and the rebuilt. This time the build succeeded without any
errors.
There something about the path on my system that's triggering this bug.
___
LibreOf
Here is the new backtrace:
https://pastebin.com/uKsUJMUX
$ cat autogen.input
--enable-debug
So I think optimizations are all disabled.
Let me know if that helps.
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedeskto
Luke Benes wrote:
> Let me know if there is anything else I can do to help.
>
Hi Luke,
terribly sorry, but the BTs still don't give any useful hint at what's
going wrong. Are you building with optimisation? Since appopen.cxx:240
really contains no throwing (but the called function
decryptGpgSessi
Subject: Re: CppunitTest_xmlsecurity_signing Unit Test Failure on 32-bit Linux
Luke Benes wrote:
> This was on my 64-bit Ubuntu 17.10 box. Anything useful here?
>
Hi Luke,
no, not really - could you please do the 'catch throw' part, too, from
my earlier mail? And then si
Luke Benes wrote:
> This was on my 64-bit Ubuntu 17.10 box. Anything useful here?
>
Hi Luke,
no, not really - could you please do the 'catch throw' part, too, from
my earlier mail? And then single-step inside appopen.cxx, until you
hit an exception?
Cheers,
-- Thorsten
signature.asc
Descripti
Unit Test Failure on 32-bit Linux
Hi Luke,
Luke Benes wrote:
> This is not a 32/64 bit issue, as I'm seeing this on my 64 bit
> Ubuntu 17.10 system. The full, unedited log built with
> SAL_LOG="+WARN.+INFO.xmlsecurity+INFO.comphelper.crypto"
>
Hmm, nothing really he
Hi Luke,
Luke Benes wrote:
> This is not a 32/64 bit issue, as I'm seeing this on my 64 bit
> Ubuntu 17.10 system. The full, unedited log built with
> SAL_LOG="+WARN.+INFO.xmlsecurity+INFO.comphelper.crypto"
>
Hmm, nothing really helpful standing out there. If you please could:
make CppunitTest_
On Mon, Jan 29, 2018 at 05:14:35PM +0700, Andika Triwidada wrote:
> > Anyways, for now I did add that patch to my disable-flaky-tests.diff
> > (just the encrypt test)
>
> something like this?
>
> $ git diff
> diff --git a/xmlsecurity/qa/unit/signing/signing.cxx
> b/xmlsecurity/qa/unit/signing/sig
On Sun, Jan 28, 2018 at 8:16 PM, Rene Engelhard wrote:
> Hi,
>
> On Sun, Jan 28, 2018 at 08:03:58PM +0700, Andika Triwidada wrote:
>> On Sun, Jan 28, 2018 at 12:31 AM, Rene Engelhard wrote:
>> > On Sat, Jan 27, 2018 at 06:20:04PM +0100, Rene Engelhard wrote:
>> >> On Mon, Jan 22, 2018 at 09:03:06
On Mon, Jan 22, 2018 at 09:03:06PM +, 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 t
Hi,
On Sun, Jan 28, 2018 at 08:03:58PM +0700, Andika Triwidada wrote:
> On Sun, Jan 28, 2018 at 12:31 AM, Rene Engelhard wrote:
> > On Sat, Jan 27, 2018 at 06:20:04PM +0100, Rene Engelhard wrote:
> >> On Mon, Jan 22, 2018 at 09:03:06PM +, Luke Benes wrote:
> >> > The previous log was heavily
On Sun, Jan 28, 2018 at 12:31 AM, Rene Engelhard wrote:
> On Sat, Jan 27, 2018 at 06:20:04PM +0100, Rene Engelhard wrote:
>> On Mon, Jan 22, 2018 at 09:03:06PM +, Luke Benes wrote:
>> > The previous log was heavily trimmed to reduce size. While the OS is
>> > different both builds share the
On Sat, Jan 27, 2018 at 06:20:04PM +0100, Rene Engelhard wrote:
> On Mon, Jan 22, 2018 at 09:03:06PM +, 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?
This is not a 32/64 bit issue, as I'm seeing this on my 64 bit Ubuntu 17.10
system. The full, unedited log built with
SAL_LOG="+WARN.+INFO.xmlsecurity+INFO.comphelper.crypto"
Can be found here:
https://pastebin.com/inwx0Hu0
The previous log was heavily trimmed to reduce size. While the OS i
With both gcc and clang on Fedora 25, the build is failing with an assertion
failure. This issue started with commit:
https://cgit.freedesktop.org/libreoffice/core/commit/?id=8242c22f84cef1bbc8c385875b2da4713b542329
[CUT] xmlsecurity_signing
SigningTest::testODFBrokenStreamGPG finished in: 639ms
Luke Benes wrote:
> /core/unotest/source/cpp/macros_test.cxx:52:SigningTest::testODFEncryptedGPG
> assertion failed
> - Expression: xComponent.is()
> - loading failed:
> file:///core//xmlsecurity/qa/unit/signing/data/encryptedGPG.odt
>
Hi Luke,
this is weird - path is constructed exactly the sam
25 matches
Mail list logo
