Bug#1050075: gtk4: 4.12 regression: FTBFS on arm*|ppc64el|s390x: several checkerboard tests failing
Simon McVittie
smcv at debian.org
Sat Aug 19 12:17:50 BST 2023
Source: gtk4
Version: 4.12.0+ds-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
gtk4 4.12.0 in experimental has test failures on multiple buildds.
Of those, arm64, armel, armhf, ppc64el and s390x all seem to have the same
failure mode:
36/1464 gtk:gsk+gsk-compare+gsk-gl+gsk-compare-gl+wayland_gles_failing / gl big-checkerboard-scaled-down2 FAIL 3.48s exit status 1
37/1464 gtk:gsk+gsk-compare+gsk-gl+gsk-compare-gl+wayland_gles_failing+gsk-compare-flipped-gl / gl big-checkerboard-scaled-down2 flipped FAIL 3.50s exit status 1
38/1464 gtk:gsk+gsk-compare+gsk-gl+gsk-compare-gl+wayland_gles_failing+gsk-compare-repeated-gl / gl big-checkerboard-scaled-down2 repeated FAIL 3.78s exit status 1
39/1464 gtk:gsk+gsk-compare+gsk-gl+gsk-compare-gl+wayland_gles_failing+gsk-compare-rotated-gl / gl big-checkerboard-scaled-down2 rotated FAIL 3.62s exit status 1
42/1464 gtk:gsk+gsk-compare+gsk-gl+gsk-compare-gl+wayland_gles_failing+gsk-compare-masked-gl / gl big-checkerboard-scaled-down2 masked FAIL 4.00s exit status 1
I'm unsure why we are running tests that appear to be flagged as "failing".
Perhaps it just needs some --no-suite=failing added?
Test failures on i386 and mips64el are out of scope for this bug report.
smcv
More information about the pkg-gnome-maintainers
mailing list