[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1039906: libreoffice: FTBFS on riscv64: uitest throws "index out of range"



tag 1039906 + moreinfo

found 1039906 4:7.5.4-1

forwarded 1039906 https://bugs.documentfoundation.org/show_bug.cgi?id=155937

thanks


Almost all the uitest cases throws such exception:

My gut feeling points to python. I mean it's not really test specific but on "Almost all the uitest" (which all are python).
ERROR: testThemePage (themepage.Test.testThemePage)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/<<PKGBUILDDIR>>/cui/qa/uitest/tabpages/themepage.py", line 19, in testThemePage     with self.ui_test.create_doc_in_start_center("impress") as component:
  File "/usr/lib/python3.11/contextlib.py", line 144, in __exit__
    next(self.gen)
  File "/<<PKGBUILDDIR>>/uitest/uitest/test.py", line 195, in create_doc_in_start_center
    self.close_doc()
  File "/<<PKGBUILDDIR>>/uitest/uitest/test.py", line 221, in close_doc
    frames[0].activate()
    ~~~~~~^^^
IndexError: index out of range

I know, that's why I wrote https://lists.debian.org/debian-riscv/2023/06/msg00000.html in the first place
This exception is always throwed when closing the doc window. As I described in bugzilla[1], the bug should be located between c++ and python environment.
Which is the bridges. Or python itself. I think.

It seems that the exception only throws in current Debian package. If I build LibreOffice (both 7.6 and 7.5 version) with external tarballs (that means, I pass parameters to autogen.sh as less as possible), this bug disappears. Therefore maybe some system-internal component are not configured correctly.

For reference: Which exact options?

Though that does not really matter, see [1]. We are supposed not to use some  random copies of libraries. Here in this case they also just build it using non-default build systems, thus even skipping their testsuite. (Which I or Debian or the respective upstream then fixed up)


Anyway, even then it does not make sense at all to ship a obsolete (3.8!) python version since then anything using pyUNO then would need to build with that python, too. And there's stuff in Debian using pyUNO.


I am building a debug version of LibreOffice with sbuild to debug uitest.

Yes, please.


Or try with a newer python? Unfortunately LibreOffice is not yet ready for python 3.12...


Regards,


Rene


Reply to: