Bug 2165173 - gtest failure on s390x
Summary: gtest failure on s390x
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: draco
Version: 38
Hardware: s390x
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Luya Tshimbalanga
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: F-ExcludeArch-s390x
TreeView+ depends on / blocked
 
Reported: 2023-01-28 02:35 UTC by Luya Tshimbalanga
Modified: 2024-05-21 14:26 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-05-21 14:26:54 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Build report done on 1.5.5 release (570.52 KB, text/plain)
2023-01-28 02:35 UTC, Luya Tshimbalanga
no flags Details

Description Luya Tshimbalanga 2023-01-28 02:35:39 UTC
Created attachment 1940835 [details]
Build report done on 1.5.5 release

Description of problem:
gtest failed on s390x architecture when building this package.

Version-Release number of selected component (if applicable):
1.5.5

How reproducible:
Always

Steps to Reproduce:
1. Use build system
2.
3.

Actual results:
Failure

Expected results:
Succeeded

Additional info:
See attached build log and files section on https://src.fedoraproject.org/rpms/draco/tree/rawhide

Comment 1 Ben Beasley 2023-02-06 12:52:20 UTC
I tried adding draco as a BuildRequires for python-trimesh to enable some additional tests, and I found that the draco_encoder throws an unhandled exception on s390x:

E               subprocess.CalledProcessError: Command '['/usr/bin/draco_encoder', '-qp', '28', '-i', '/tmp/tmpd1uz557y.ply', '-o', '/tmp/tmpkbowi3es.drc']' died with <Signals.SIGABRT: 6>.
/usr/lib64/python3.11/subprocess.py:571: CalledProcessError
----------------------------- Captured stderr call -----------------------------
terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc

I wonder whether or not there is enough usable functionality on s390x to keep packaging it with the tests disabled, or whether it should really be ExcludeArch.

Comment 2 Ben Cotton 2023-02-07 15:06:46 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 38 development cycle.
Changing version to 38.

Comment 3 Aoife Moloney 2024-05-07 15:56:15 UTC
This message is a reminder that Fedora Linux 38 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 38 on 2024-05-21.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '38'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 38 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 4 Aoife Moloney 2024-05-21 14:26:54 UTC
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21.

Fedora Linux 38 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.