Bug#946206: esys-particle: autopkgtest times out when module import fails

[Graham Inggs]

Control: reopen -1

The autopkgtest still times out in the salsa pipeline [1].

It is not clear to me whether #1101992 is now fixed, or whether a new
bug needs to be filed for the failing import.

I've copied what I hope is the relevant part of a pipeline job [2] below.


[1] https://salsa.debian.org/science-team/esys-particle/-/pipelines
[2] https://salsa.debian.org/science-team/esys-particle/-/jobs/7458085


Setting up esys-particle (2.3.5+dfsg2-10+salsaci+20250419+9) ...
/usr/lib/python3/dist-packages/esys/lsm/util/OptParse.py:38:
SyntaxWarning: invalid escape sequence '\['
regex = re.compile("\[(.*)\]")
Processing triggers for libc-bin (2.41-7) ...
autopkgtest [15:12:04]: test build1: [-----------------------
CSubLatticeControler::initMPI()
CSubLatticeControler::initMPI()
Traceback (most recent call last):
File "/tmp/tmp.B1HeVeTtB6/compression.py", line 1, in <module>
from esys.lsm import *
File "/usr/lib/python3/dist-packages/esys/lsm/__init__.py", line 15, in <module>
from .util import InstallInfo
File "/usr/lib/python3/dist-packages/esys/lsm/util/__init__.py", line
13, in <module>
from esys.lsm.util.FoundationPy import *
ImportError: libFoundationPy.so.0: cannot open shared object file: No
such file or directory
--------------------------------------------------------------------------
The user-provided time limit for job execution has been reached:
Timeout: 1800 seconds
The job will now be aborted. Please check your code and/or
adjust/remove the job execution time limit (as specified by --timeout
command line option or MPIEXEC_TIMEOUT environment variable).