[petsc-users] Running PETSc/SLEPc tests inside/outside a singularity container

[Jan Grießer]

Hello all,
I have a question about the tests for PETSc/PETSc4Py and SLEPc4Py when these libraries are compiled inside a Singularity container (The .def file for compilation is attached). The compilation of the libraries is no problem, only if you call "make all check" for PETSc and "make check" for SLEPC at the end of the compilation, error messages appear for PETSc or the Singularity build aborts for SLEPc (see output.txt). I guess the problems are only related to the "sudo" rights, which are needed to build the containers. With slepc I don't even have access to the makelog because the container can't be built at all. For the 4Py versions I could navigate via singularity shell into the corresponding directories and execute the runtests. These returned an ok for all tests.
Is there a clever way to start tests for the c-Versions of PETSc/SLEPc afterwards to check for the correct build of the Libaries? Using the singularity shell to navigate into petsc and using gmakefile test throws an „Read-only file system“ error, as expected. 

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: output.txt
URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20210113/d9e90849/attachment-0001.txt>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: petsc_slepc.def
Type: application/octet-stream
Size: 3324 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20210113/d9e90849/attachment-0001.obj>