Hi,

* Gianfranco Costamagna <locutusofb...@debian.org> [2019-12-22 12:29]:
Hello, looks like we still have segfaults/failures on:
armhf: http://autopkgtest.ubuntu.com/packages/a/assimp/focal/armhf

I wasn't able to reproduce this on harris.d.o nor on a private machine.

ppc64el: http://autopkgtest.ubuntu.com/packages/a/assimp/focal/ppc64el

This works fine on plummer.d.o as well. Also note that 5.0.0~ds2-4 passes but the diff to -4build1 is only the changelog. Looks rather like a hiccup on the test machine.

s390x: http://autopkgtest.ubuntu.com/packages/a/assimp/focal/s390x

This fails on zelenka.d.o as well. Seems like the importers for gltf, fbx and glb are broken on s390x. I'm not sure it's worth the effort for that architecture, so I would propose to skip it by adding this to d/t/quicktest.py:

import platform
if platform.machine() == 's390x':
    extensions.remove(".gltf")
    extensions.remove(".fbx")
    extensions.remove(".glb")

they previously passed, so this is why they should be considered probably RC 
(and why I'm reopening this bug)...

I guess by "previously" you are referring to version 4.1.0? Note that the test back then was quiet different:

https://sources.debian.org/src/assimp/4.1.0%7Edfsg-7/debian/tests/

The file types failing on s390x where not present and the test failing on the Ubuntu armhf is not even there. (Just mentioning, not arguing about the severity.)

Also, a successful testlog still looks a little sad:

https://ci.debian.net/data/autopkgtest/unstable/amd64/a/assimp/3806302/log.gz

| > Trying to open '/usr/share/assimp/models/FBX/transparentTest.fbx' with 
assimp
| Launching asset import ...           OK
| Validating postprocessing flags ...  OK
| ERROR: Failed to load file: FBX-Tokenize (offset 0x23) block offset is out of 
range
| assimp info: Unable to load input file 
/usr/share/assimp/models/FBX/transparentTest.fbx

| > Trying to open '/usr/share/assimp/models/MDL/MDL3 (3DGS 
A4)/minigun_readme.txt' with assimp
| Launching asset import ...           OK
| Validating postprocessing flags ...  OK
| ERROR: Failed to load file: No suitable reader found for the file format of file 
"/usr/share/assimp/models/MDL/MDL3 (3DGS A4)/minigun_readme.txt".
| assimp info: Unable to load input file /usr/share/assimp/models/MDL/MDL3 
(3DGS A4)/minigun_readme.txt

| trying: /usr/share/assimp/models/FBX/transparentTest.fbx
| Error encountered while loading 
'/usr/share/assimp/models/FBX/transparentTest.fbx'
| Traceback (most recent call last):
|   File "./debian/tests/quicktest.py", line 192, in do_load
|     load(filename)
|   File "./debian/tests/quicktest.py", line 108, in load
|     filename, processing=pyassimp.postprocess.aiProcess_Triangulate
|   File "/usr/lib/python3/dist-packages/pyassimp/core.py", line 319, in load
|     raise AssimpError('Could not import file!')
| pyassimp.errors.AssimpError: Could not import file!

As far es I checked are the assimp-info and quicktest.py failures consistent, so these are probably limitations of the library or broken files.

I would propose to add the workaround for s390x and wait for new test results for armhf resp. ignore them for ppc64el, as they where not reproducible. If no one disagrees I will do a NMU and close this bug next Sunday.

Cheers Jochen

Attachment: signature.asc
Description: PGP signature

Reply via email to