90091 2012-06-27 12:24:28 -0700 [Qt] REGRESSION(r121348): It made 500+ tests flakey 2012-06-28 00:22:22 -0700 1 1 1 Unclassified WebKit New Bugs 528+ (Nightly build) All All RESOLVED DUPLICATE 87680 Qt, QtTriaged P1 Critical --- 89475 1 ossy webkit-unassigned abecsi achicu hausmann ossy simon.fraser oldest_to_newest 658775 0 ossy 2012-06-27 12:24:28 -0700 http://trac.webkit.org/changeset/121349 made 500+ tests flakey on Qt bots and it made the bots exit early, so the Qt bot is useless because of this bug. http://build.webkit.org/builders/Qt%20Linux%20Release/builds/48817 http://build.webkit.sed.hu/builders/x86-64%20Linux%20Qt%20Release/builds/39264 Could you check it, please? 658787 1 ossy 2012-06-27 12:39:28 -0700 András, have you got any idea what caused this annoying sideeffect bug? Simon, what should we do in this case? Skip 500+ test? Rollout the patch which cause it? Maybe it is innocent and there are a serious bug in QtWebKit somewhere ... Or leave the bots broken? 658795 2 ossy 2012-06-27 12:49:08 -0700 I forgot to mention that it is Qt-WK1 related bug. It is valid on Qt 4.8 and Qt 5.0 WebKit, but everything works on Qt 5.0 WK2. 658807 3 hausmann 2012-06-27 13:06:14 -0700 (In reply to comment #1) > András, have you got any idea what caused this annoying sideeffect bug? > > Simon, what should we do in this case? Skip 500+ test? Rollout the patch which cause it? Maybe it is innocent and there are a serious bug in QtWebKit somewhere ... Or leave the bots broken? My first impression is as well that the patch is innocent. Unfortunately I'm without a build machine for the next couple of days, otherwise I'd give this a try myself, but here's what I'd do: 1) Try to reproduce the failures locally 2) See if reverting just that patch _does_ fix it (I doubt it) 3) Bisect down to the change that caused it or 4) Find out that it's some weird miscompilation or unclean build issue that this particular patch just uncovered by accident. 659276 4 ossy 2012-06-28 00:01:30 -0700 r121349 is innocent, http://trac.webkit.org/changeset/121348 is the culprit. With r121347 everything works, and with r121348 tests are flakey. I tried reverting r121348 on ToT, and it solved the problem for me. Now I'm trying to find what caused the problem. My first idea is that the new css3/filters/blur-filter-page-scroll.html does something wrong. 659288 5 ossy 2012-06-28 00:20:12 -0700 Oh, I got it. AcceleratedCompositingEnabled and MockScrollBarsEnabled isn't reset after each test in Qt's DRT. :-/ What a pathetic bug! Here is the bug report for MockScrollBarsEnabled - https://bugs.webkit.org/show_bug.cgi?id=87680 659290 6 ossy 2012-06-28 00:22:22 -0700 *** This bug has been marked as a duplicate of bug 87680 ***