[armhf-linux] inkscape 1.1.1 test failures

  • Open
  • quality assurance status badge
Details
One participant
  • Maxim Cournoyer
Owner
unassigned
Submitted by
Maxim Cournoyer
Severity
normal
M
M
Maxim Cournoyer wrote on 16 Dec 2022 14:26
(name . bug-guix)(address . bug-guix@gnu.org)
87fsdfbhue.fsf@gmail.com
Hi,

When attempting to build inkscape 1.1.1 for armhf-linux, there are two
test failures:

The following tests FAILED:
231 - cli_export-png-color-mode-gray-8_png (Bus error)
233 - cli_export-png-color-mode-rgb-8_png (Bus error)


Toggle snippet (26 lines)
231/300 Test #231: cli_export-png-color-mode-gray-8_png ................................Bus error***Except
Unable to init server: Could not connect: Connection refused
Background RRGGBBAA: ffffff00
Area 0:0:453.543:396.85 exported to 454 x 397 pixels (96 dpi)

Emergency save activated!
Emergency save completed. Inkscape will close now.
If you can reproduce this crash, please file a bug at https://inkscape.org/report
with a detailed description of the steps leading to the crash, so we can fix it.
** Message: 05:56:45.905: Error: Inkscape encountered an internal error and will close now.

[...]

Start 233: cli_export-png-color-mode-rgb-8_png
233/300 Test #233: cli_export-png-color-mode-rgb-8_png .................................Bus error***Except
Unable to init server: Could not connect: Connection refused
Background RRGGBBAA: ffffff00
Area 0:0:453.543:396.85 exported to 454 x 397 pixels (96 dpi)

Emergency save activated!
Emergency save completed. Inkscape will close now.
If you can reproduce this crash, please file a bug at https://inkscape.org/report
with a detailed description of the steps leading to the crash, so we can fix it.
** Message: 05:56:46.879: Error: Inkscape encountered an internal error and will close now.

The above failures were encountered when building natively on
overdrive1.

--
Thanks,
Maxim
?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 60121@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 60121
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch