Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Re: unbreaking LibreOffices tests on at least release architectures
1 view
Skip to first unread message
Rene Engelhard
Jun 20, 2023, 11:40:03 AM6/20/23
to
Hi,
Am 20.06.23 um 16:52 schrieb 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.
Except by just starting to build and run into an issue....
>> (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?
No. That also happens everywhere, also on amd64/arm64.
>> Fatal exception: Signal 11
> It's a segfault,
I know :)
> 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.
Well, the command line is there, but I see the point.
Still one could talk about this... I yet have to hear from any porter
talking about actual issues (and the buildlogs *are* there).
>> 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?
In this specific case probably openjdk. I was juat answering Adrian on
the smoketest.
Actually I run a --disable-java build on eller right now.
>> ./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?
Because libreoffice crashed, "obviously", so there of course is no
connection anymore.
The point here is that it even crashes at startup so probably being
completely broken. (and I am not surprised)
>> 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?
It crashes because libreoffice crashed, the connection is not there and
therefore not alive. Yes, I can read that.
As said, I was just pointing at a smoketest example.
> 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.
This specific one might be, yes.
That's probably not true for the other architectures' failures. (E.g.
the Bus error I mentioned earlier or the powerpcs having
"Trace/breakpoint trap (core dumped)" or s390x or armel crashing in
loading tiff files.
And that is all only the first failure on earch archs, there's more,
there's gazillions of failures in the architectures' build logs.
Regards,
Rene
Am 20.06.23 um 16:52 schrieb 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.
Except by just starting to build and run into an issue....
>> (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?
No. That also happens everywhere, also on amd64/arm64.
>> Fatal exception: Signal 11
> It's a segfault,
I know :)
> 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.
Well, the command line is there, but I see the point.
Still one could talk about this... I yet have to hear from any porter
talking about actual issues (and the buildlogs *are* there).
>> 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?
In this specific case probably openjdk. I was juat answering Adrian on
the smoketest.
Actually I run a --disable-java build on eller right now.
>> ./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?
Because libreoffice crashed, "obviously", so there of course is no
connection anymore.
The point here is that it even crashes at startup so probably being
completely broken. (and I am not surprised)
>> 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?
It crashes because libreoffice crashed, the connection is not there and
therefore not alive. Yes, I can read that.
As said, I was just pointing at a smoketest example.
> 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.
This specific one might be, yes.
That's probably not true for the other architectures' failures. (E.g.
the Bus error I mentioned earlier or the powerpcs having
"Trace/breakpoint trap (core dumped)" or s390x or armel crashing in
loading tiff files.
And that is all only the first failure on earch archs, there's more,
there's gazillions of failures in the architectures' build logs.
Regards,
Rene
Rene Engelhard
Jul 22, 2023, 9:40:03 AM7/22/23
to
Hi,
Am 22.07.23 um 15:07 schrieb Andreas Schwab:
>> Which gives the smoketest test failure here I pointed out (again) in my
>> other mail.
> $ find /usr/lib64/libreoffice/ -name "*smoke*"
> /usr/lib64/libreoffice/program/classes/smoketest.jar
>
> How can I run that?
You can't from that, ttbomk. You miss other files needed which are not
ending up in the installation.
You build it and run make subsequentcheck in smoketest (or a general
make check). But you might need to build prereqs first, see
https://salsa.debian.org/libreoffice-team/libreoffice/libreoffice/-/blob/master/rules#L2340
ff.
Regards,
Rene
Am 22.07.23 um 15:07 schrieb Andreas Schwab:
>> Which gives the smoketest test failure here I pointed out (again) in my
>> other mail.
> $ find /usr/lib64/libreoffice/ -name "*smoke*"
> /usr/lib64/libreoffice/program/classes/smoketest.jar
>
> How can I run that?
You can't from that, ttbomk. You miss other files needed which are not
ending up in the installation.
You build it and run make subsequentcheck in smoketest (or a general
make check). But you might need to build prereqs first, see
https://salsa.debian.org/libreoffice-team/libreoffice/libreoffice/-/blob/master/rules#L2340
ff.
Regards,
Rene
Andreas Schwab
Jul 28, 2023, 4:50:04 AM7/28/23
to
On Jul 22 2023, Rene Engelhard wrote:
> Hi,
>
> Am 22.07.23 um 16:09 schrieb Andreas Schwab:
> Hi,
>
>> On Jul 22 2023, Rene Engelhard wrote:
>>
>>> Am 22.07.23 um 15:53 schrieb Andreas Schwab:
>>>> On Jul 22 2023, Rene Engelhard wrote:
>>>>
>>>>> Does opensuse have some public git/$VCS?
>>>> https://build.opensuse.org/package/live_build_log/openSUSE:Factory:RISCV/libreoffice/standard/riscv64
>>> Thanks...
>>>
>>> But maybe I am too blind.
>>>
>>> I don't see the actual spec + related files anywhere?
>> See Overview:
>>
>> https://build.opensuse.org/package/show/openSUSE:Factory:RISCV/libreoffice
>
> Thanks.
>
>
> I don't see anyone obvious there (except not running *any* test) there
> offhand, though.
I tried to enable the smoketest, but it fails even on x86-64:
https://build.opensuse.org/project/show/home:Andreas_Schwab:riscv:libreoffice
Since I don't know much about the libreoffice sources, I have just
copied the %check section from an old revision of our libreoffice
package.
--
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."
0 new messages