Re: unbreaking LibreOffices tests on at least release architectures

[Omer Turpault]

> Le 18 juin 2023 à 13:37, Steve McIntyre <st...@einval.com> a écrit :
>
> On Sun, Jun 18, 2023 at 10:32:55AM +0200, Rene Engelhard wrote:
>> Hi,
>>
>>> Am 18.06.23 um 10:19 schrieb John Paul Adrian Glaubitz:
>>> On Sun, 2023-06-18 at 09:31 +0200, Rene Engelhard wrote:
>>>> Also note I am not talking about the debian-ports architectures. Those I
>>>> forgot and I have no problems making them stay into "testsuite ran but
>>>> results ignored" set.
>>> Why did you send this mail exclusively to debian-ports then?
>>
>> I (obviously) wrongly assumed that this was the magic address which
>> duplicates to every port.
>>
>> Must have misremembered.
>
> It still does - I got this copy via the debian-arm list...
>
> --
> Steve McIntyre, Cambridge, UK. st...@einval.com
> "This dress doesn't reverse." -- Alden Spiess
>
Same for me, I received it through the Debian-ppc list

-someone

[Kurt Roeckx]

On Tue, Jun 20, 2023 at 05:52:44AM +0200, Rene Engelhard wrote:
> Hi,
>

> Am 19.06.23 um 23:29 schrieb Rene Engelhard:
> > > The pragmatic option would be to run only a smoketest for build success
> > > on architectures not tested by upstream.
> >
> > And have Format->Character in Impress crash with Bus error like on
> > mipsel? That doesn't sound too good for basic quality.
> >
> > There is a "smoketest" but it does just basic start. open, close stuff.
> > Not even basic usage.
>
> That said, that is the smoketest on mipsel:

The problem with a mail like this is that it really doesn't help anybody
in understanding the problem. As porter, it will probably take a lot of
time to get to the point where you can start looking at what the problem
might be. It contains lots of information, but it's not clear what the
problem is and what needs to be looked at.

> (process:8700): dconf-CRITICAL **: 02:36:13.575: unable to create directory
> '/run/user/2952/dconf': Permission denied. dconf will not work properly.
>
> (process:8708): dconf-CRITICAL **: 02:36:19.328: unable to create directory
> '/run/user/2952/dconf': Permission denied. dconf will not work properly.
>
> (process:8815): dconf-CRITICAL **: 02:36:52.467: unable to create directory
> '/run/user/2952/dconf': Permission denied. dconf will not work properly.

Is this something the porter should look at? Is is relevant?

> Fatal exception: Signal 11

It's a segfault, this should normally be trivial for you to debug,
but is probably complicated for a porter to find out how to do things
like attaching a debugger to the relevant process.

> Stack:
> /<<PKGBUILDDIR>>/instdir/program/libuno_sal.so.3(+0x49b18)[0x77d69b18]
> /<<PKGBUILDDIR>>/instdir/program/libuno_sal.so.3(+0x49d48)[0x77d69d48]
> /usr/lib/jvm/java-17-openjdk-mipsel/lib/server/libjvm.so(+0x537b8c)[0x62417b8c]

Is this some openjdk problem, not a problem in libreoffice problem?

> ./smoketest/smoketest.cxx:187:(anonymous namespace)::Test::test
> assertion failed
> - Expression: connection_.isStillAlive()

So the (TCP?) connection is not alive? Why not? That doesn't seem to be
platform specific. Is that a problem in the test suite, and not
libreoffice itself?

> unknown:0:(anonymous namespace)::Test::test
> tearDown() failed
> - An uncaught exception of type com.sun.star.lang.DisposedException
> - Binary URP bridge already disposed at ./binaryurp/source/bridge.cxx:1048
>
> (anonymous namespace)::Test::test finished in: 76764ms
> smoketest.cxx:187:Assertion
> Test name: (anonymous namespace)::Test::test
> assertion failed
> - Expression: connection_.isStillAlive()
>
> ##Failure Location unknown## : Error
> Test name: (anonymous namespace)::Test::test
> tearDown() failed
> - An uncaught exception of type com.sun.star.lang.DisposedException

And then the test suite crashes because it can't actually deal
with the previous the assertion failure, and the segfault above
is not relevant at all?

The most likely thing is that this is not a platform specific issue,
but a either a general issue that just shows up on some platforms for
whatever reason, or some problem in an other piece of software that
libreoffice is using that does have a pratform specific issue.


Kurt

[Rene Engelhard]

Hi,

Am 22.07.23 um 14:34 schrieb Andreas Schwab:
> On Jul 22 2023, Rene Engelhard wrote:
>
>> And that includes LibreOffice-bundled extensions like the
>> english,hungarian,russian grammar checker for example. Ot external finnish
>> spellchecking, hyphenation and grammer checking. Or turkish spellchecing.
>>
>> And those are extensions written in python which neither register when
>> registering manually nor when being installed as bundled extensions (see
>> the discussion in this thread, not going to reiterate)
> How can I test that? I have never used libreoffice before, so I don't
> know what to look for.

https://lists.debian.org/debian-riscv/2023/07/msg00010.html

https://lists.debian.org/debian-riscv/2023/07/msg00014.html


(some of them says mips64el, but as said in my other replies, the
smoketest failure is the same symptom there, just on riscv64 actual
unopkg add does nothing effectively.)


Regards,


Rene

[Andreas Schwab]

On Jul 22 2023, Rene Engelhard wrote:

> Yes. _basically_. (Only with -O0 or maybe -Os as upstreams makefile says,
> though)

On openSUSE Factory, libreoffice is built with the usual compiler flags,
wich includes full optimisation and hardening.

--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."