Bug#953235: vtkplotter: autopkgtest arm64 failure: No module named 'vtkIOFFMPEGPython'

[Adrian Bunk]

On Thu, May 07, 2020 at 10:28:33AM +0200, Paul Gevers wrote:
>...
> On 07-05-2020 10:07, Adrian Bunk wrote:
> > This is a toolchain problem affecting many packages:
> > https://sourceware.org/bugzilla/show_bug.cgi?id=25051
> 
> Do you have any rough estimate how many?
>...

Other bugs I can quickly find are #930039 and #945878.

AFAIR I have seen maintainers adding workarounds for arm64+ppc64el FTBFS
caused by this bug that did not have bugs in the BTS.

#951704 looks like a similar but unrelated problem with jemalloc.

> Is there any way to predict which packages are effected,

Anything loading a plugin that is directly or indirectly linked
with libgomp might or might not have this problem.

Python C extensions are the most frequent ones.

Heavy usage of Python code with C extensions tends to be in the more
scientific areas of the archive, I'd guess many of these packages have
no users at all on ppc64el or arm64 who would report bugs (Raspbian is armhf).

python3-vtkplotter -> python3-vtk7 -> libvtk -> FFmpeg libraries
  -> libsoxr -> libgomp

> or to detect which packages are effected?

"import vtk" works, but "import vtkplotter" blows up when importing vtk.

This is similar to the two different OpenSSL versions in stretch, where 
module load order might determine whether Apache segfaults or starts.

>...
> > Is there a non-manual way to express that the autopkgtest must not run 
> > on arm64 and powerpc64el?
> 
> There is currently not even a manual way except for marking the test as
> skippable and exitting with error code 77 on unsupported architectures.
> Mind you, I don't think toolchain issues should be marked at the package
> level (but maybe you didn't mean that).

vtkplotter: flagged for removal in 6.3 days

The big hammer would be to remove the autopkgtest...

> If we can detect this failure
> mode (and similar ones in the future) we can of course generate hints
> based on this heuristics and have the failures ignored until the
> toolchain issues are fixed.

A failing arm64 or ppc64el autopkgtest log containing the string
"libgomp.so.1: cannot allocate memory in static TLS block"
is this bug.

> Paul

cu
Adrian