Opened 2 years ago

Last modified 2 years ago

#9295 assigned defect

Linux nightly build broken, libxkbfile.so.1: cannot open shared object file

Reported by: Tom Goddard Owned by: Greg Couch
Priority: moderate Milestone:
Component: Build System Version:
Keywords: Cc: chimerax-programmers
Blocked By: Blocking:
Notify when closed: Platform: all
Project: ChimeraX

Description

I guess the Linux build machine (singularity image?) changed. So the ChimeraX test suite fails because Qt can't import QWebEngine.

The Linux nightly build fails the test suite importing all Python modules:
Importing chimerax.help_viewer.tool
-> ERROR: libxkbfile.so.1: cannot open shared object file: No such file or directory

Importing chimerax.ui.file_history
-> ERROR: cannot import name 'ChimeraXHtmlView' from 'chimerax.ui.widgets' (/tmp/chx-develop.VvA6nG/ChimeraX.app/lib/python3.11/site-packages/chimerax/ui/widgets/init.py)

and failed building docs

Failed to import chimerax.ui.widgets.htmlview.
Possible hints:

  • AttributeError: module 'chimerax.ui.widgets' has no attribute 'htmlview'
  • ImportError: libxkbfile.so.1: cannot open shared object file: No such file or directory

building [mo]: targets for 0 po files that are out of date

Change History (3)

comment:1 by Greg Couch, 2 years ago

The singularity hasn't changed for a long time. Qt should not be imported in nogui/nooffscreen mode. Whatever caused Qt to be installed should be fixed.

comment:2 by Tom Goddard, 2 years ago

The errors are in the ChimeraX test suite import tests which imports all Python files including those that have Qt imports in them at the top level usually because they are deriving classes from Qt base classes. The Qt modules are being imported but no Qt functions are called.

I'm not sure what changed that broke the Linux build. I did not see any ChimeraX source code change that caused the problem. So it seems that the build environment changed so that the QtWebEngine module no longer imports.

Last edited 2 years ago by Tom Goddard (previous) (diff)

comment:3 by Tom Goddard, 2 years ago

Test suite errors are not supposed to cause the build to fail. So possibly these errors are not the reason the Linux build is not getting to the download page.

We just found that the build system last-commit date from Friday June 30 was April 27 because a branch was merged from that date on Friday. Possibly that unexpected old date is the cause of the Linux build failing.

Note: See TracTickets for help on using tickets.