GNOME Bugzilla – Bug 765188
test-suite failure on mipsel(64) : /testsuite/reftests/button-wrapping.ui: FAIL
Last modified: 2018-05-02 17:03:18 UTC
Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821337 The following test fails reproducibly on mipsel and mipsel64: testsuite/reftests/button-wrapping.ui: FAIL Any help in debugging this would be appreciated. I do have access to a porter box, so if you want me to run further diagnostics, please let me know.
the first step would be finding the screenshots from the failed test. The should be in /tmp. Look for png files with button-wrapping in their name.
Created attachment 326300 [details] button-wrapping.diff.png
Created attachment 326301 [details] button-wrapping.out.png
Created attachment 326302 [details] button-wrapping.ref.png
@Matthias, thanks for the hint. I've attached the files.
Ok, so what you are seeing is that the one file already started the check animation by the time we take the screenshot. Unfortunately, this will be hard to track down. I've asked Benjamin about this, and neither he nor I have any idea why the test would fail in this way on one particular architecture.
As additional information, besides mipsel and mips64el, we now lso see this on hppa. This also didn't happen with 3.18.9
I've ran a git bisect, and the first faulty commit is commit 460aa64c58b6b12d49b132b7c4df0eadf0070e34 Author: Lapo Calamandrei <calamandrei@gmail.com> Date: Thu Feb 11 18:27:25 2016 +0100 Adwaita: animate check and radios Unfortunately, this commit can not be easily reverted, so I couldn't test a revert on top of 3.20.3
well, sure. that commit introduced animated check setting, and that is what you are seeing kicking in here.
We're moving to gitlab! As part of this move, we are moving bugs to NEEDINFO if they haven't seen activity in more than a year. If this issue is still important to you and still relevant with GTK+ 3.22 or master, please reopen it and we will migrate it to gitlab.
This issue is still unfixed in 3.22
(In reply to Matthias Clasen from comment #10) > We're moving to gitlab! As part of this move, we are moving bugs to NEEDINFO > if they haven't seen activity in more than a year. If this issue is still > important to you and still relevant with GTK+ 3.22 or master, please reopen > it and we will migrate it to gitlab. I can't reopen it... Just saying
My guess is that the wording above is imprecise and that NEW is equally fine (because it's not like we'll discard all NEW bugs while migrating!) I've updated the version too; do you have the ability to make edits like that? If not, you probably should. :)
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gtk/issues/614.