GNOME Bugzilla – Bug 770653
test-suite failure: testsuite/css/style/test-css-style.c: FAIL
Last modified: 2016-09-04 15:46:40 UTC
Version: 3.21.5 On our Debian buildds we see the following test suite failure on the following architectures: arm64, ppc64el, s390x Failed to open file './test-css-style.gresource.xml': No such file or directory Failed to open file './test-css-style.gresource.xml': No such file or directory TEST: test-css-style... (pid=726) /build/gtk+3.0-Cz8y3X/gtk+3.0-3.21.5/testsuite/css/style/adjacent-states.ui: OK /build/gtk+3.0-Cz8y3X/gtk+3.0-3.21.5/testsuite/css/style/colornames.ui: ** ERROR:/build/gtk+3.0-Cz8y3X/gtk+3.0-3.21.5/./testsuite/css/style/test-css-style.c:115:load_ui_file: assertion failed (error == NULL): colornames.css:120:42'rebeccapurple' is not a valid color name (gtk-css-provider-error-quark, 1) FAIL Full build logs at https://buildd.debian.org/status/fetch.php?pkg=gtk%2B3.0&arch=arm64&ver=3.21.5-1&stamp=1472584391 https://buildd.debian.org/status/fetch.php?pkg=gtk%2B3.0&arch=ppc64el&ver=3.21.5-1&stamp=1472583442 https://buildd.debian.org/status/fetch.php?pkg=gtk%2B3.0&arch=s390x&ver=3.21.5-1&stamp=1472584695
You need a newer pango for that
(In reply to Matthias Clasen from comment #1) > You need a newer pango for that Hm, ok. I see that those buildds picked up pango 1.40.1 as 1.40.2 was not built yet. Should the pango version in configure.ac be bumped accordingly to avoid such an error?
don't see a strong reason to bump the pango dependency, just to make a test pass.
(In reply to Matthias Clasen from comment #3) > don't see a strong reason to bump the pango dependency, just to make a test > pass. Why do the tests require a newer pango then in the first place?