Bug 2128024 - Python tests segfault with SWIG 4.1.0
Summary: Python tests segfault with SWIG 4.1.0
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: subversion
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Richard Lescak
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-09-19 16:05 UTC by Jitka Plesnikova
Modified: 2022-11-10 22:14 UTC (History)
3 users (show)

Fixed In Version: subversion-1.14.2-8.fc36 subversion-1.14.2-8.fc37
Clone Of:
Environment:
Last Closed: 2022-10-22 13:51:05 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jitka Plesnikova 2022-09-19 16:05:03 UTC
I am testing rebuild of SWIG dependencies against upcoming version 4.1.0 in Fedora rawhide/38.

The build of subversion-1.14.2 is failing with this version.

+ make check-swig-py
mkdir /builddir/build/BUILD/subversion-1.14.2/subversion/bindings/swig/python/libsvn
if [ "LD_LIBRARY_PATH" = "DYLD_LIBRARY_PATH" ]; then for d in /builddir/build/BUILD/subversion-1.14.2/subversion/bindings/swig/python/libsvn_swig_py /builddir/build/BUILD/subversion-1.14.2/subversion/bindings/swig/python/../../../libsvn_*; do if [ -n "$DYLD_LIBRARY_PATH" ]; then LD_LIBRARY_PATH="$LD_LIBRARY_PATH:$d/.libs"; else LD_LIBRARY_PATH="$d/.libs"; fi; done; export LD_LIBRARY_PATH; fi; \
cd /builddir/build/BUILD/subversion-1.14.2/subversion/bindings/swig/python; \
  /usr/bin/python3 /builddir/build/BUILD/subversion-1.14.2/subversion/bindings/swig/python/tests/run_all.py

RPM build errors:
make: *** [Makefile:947: check-swig-py] Segmentation fault (core dumped)
+ : Python swig test failure.
+ exit 1

I reported it to swig upstream
https://github.com/swig/swig/issues/2373 
and got answer that it is related to change "Remove -py3 command line option"
https://github.com/swig/swig/commit/a343b7e254567a64761bc1be7dc55b7b7424ec52

Recommended fix works. 
https://github.com/swig/swig/issues/2373#issuecomment-1250997124

Successful build with swig 4.1.0
https://copr.fedorainfracloud.org/coprs/jplesnik/swig-rebuild/build/4863479/

Comment 1 Jitka Plesnikova 2022-09-20 07:25:58 UTC
I reported it to upstream. You can check their response here:
https://lists.apache.org/thread/18xcfz5bvc3g972dxvhk3h97thobbmzs

Comment 2 Fedora Update System 2022-10-10 10:56:10 UTC
FEDORA-2022-bccb753a3f has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-bccb753a3f

Comment 3 Fedora Update System 2022-10-11 08:22:01 UTC
FEDORA-2022-bccb753a3f has been pushed to the Fedora 37 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-bccb753a3f`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-bccb753a3f

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 4 Fedora Update System 2022-10-13 13:48:25 UTC
FEDORA-2022-cfb8a8b326 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-cfb8a8b326

Comment 5 Fedora Update System 2022-10-14 14:37:46 UTC
FEDORA-2022-cfb8a8b326 has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-cfb8a8b326`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-cfb8a8b326

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2022-10-22 13:51:05 UTC
FEDORA-2022-cfb8a8b326 has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 7 Fedora Update System 2022-11-10 22:14:10 UTC
FEDORA-2022-bccb753a3f has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.


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