[Webkit-unassigned] [Bug 281038] New: [GTK] wxPython fails test suite on i586 with webkitgtk 2.46.0

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=281038

            Bug ID: 281038
           Summary: [GTK] wxPython fails test suite on i586 with webkitgtk
                    2.46.0
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: PC
                OS: Linux
            Status: NEW
          Keywords: Gtk
          Severity: Normal
          Priority: P3
         Component: WebKitGTK
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: dimstar at opensuse.org
                CC: bugs-noreply at webkitgtk.org

While preparing the integration of GNOME 47 into openSUSE Tumbleweed, we have noticed that with the update of webkitgtk to 2.46.0 (or 2.46.1), the test suite of wxPython starts failing on i586 (passes on x86_64)

[ 1312s] =========================== short test summary info ============================
[ 1312s] FAILED unittests/test_webview.py::webview_Tests::test_webview1
[ 1312s] FAILED unittests/test_webview.py::webview_Tests::test_webview2
[ 1312s] FAILED unittests/test_webview.py::webview_Tests::test_webview3
[ 1312s] = 3 failed, 1689 passed, 31 skipped, 4 xfailed, 4 warnings in 71.17s (0:01:11) =

Python error: Segmentation fault
[ 1309s] 
[ 1309s] Current thread 0xf77c3700 (most recent call first):
[ 1309s]   File "/home/abuild/rpmbuild/BUILDROOT/python311-wxPython-4.2.1-9.3.i386/usr/lib/python3.11/site-packages/wx/core.py", line 2252 in MainLoop
[ 1309s]   File "/home/abuild/rpmbuild/BUILD/wxPython-4.2.1/unittests/wtc.py", line 34 in tearDown
[ 1309s]   File "/usr/lib/python3.11/unittest/case.py", line 584 in _callTearDown
[ 1309s]   File "/usr/lib/python3.11/unittest/case.py", line 626 in run
[ 1309s]   File "/usr/lib/python3.11/unittest/case.py", line 678 in __call__

Reverting to 2.45.92 gave us a successful result for that test suite

This is just the early findings to have it documented - I'll be trying to
* get some better debug output (stack trace of the segfault if possible)
* bisect 2.45.92..2.46.0 to hopefully identify the failing commit

Unless of course somebody already knows what's wrong based on that little information

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20241008/5510fc3d/attachment.htm>