91490 2012-07-17 04:01:50 -0700 [Qt][WK2] REGRESSION(r122770) - it made ~ 160 fails on WebKit2 2012-07-25 04:42:44 -0700 1 1 1 Unclassified WebKit Tools / Tests 528+ (Nightly build) Unspecified Unspecified RESOLVED DUPLICATE 88064 P2 Normal --- 79666 91425 0 jbadics webkit-unassigned allan.jensen eric hausmann hyatt jturcotte kadam kbalazs kkristof ossy simon.fraser szledan oldest_to_newest 671149 0 jbadics 2012-07-17 04:01:50 -0700 156 tests fail on WebKit2 since r122768 or r122771. 671152 1 kbalazs 2012-07-17 04:04:10 -0700 (In reply to comment #0) > 156 tests fail on WebKit2 since r122768 or r122771. ... or any change in between the two. 671157 2 kbalazs 2012-07-17 04:11:03 -0700 This is definitely not a jsc issue. 671195 3 allan.jensen 2012-07-17 05:21:41 -0700 r122769 is a rounding change (from floored int to rounded int for us), that could likely change metrics slightly all over the place. 671204 4 kbalazs 2012-07-17 05:47:41 -0700 (In reply to comment #3) > r122769 is a rounding change (from floored int to rounded int for us), that could likely change metrics slightly all over the place. I rather suspect on r122770, I'm going to check these changes invidually (on 67). 671213 5 kbalazs 2012-07-17 06:00:40 -0700 This is caused by r122770 (bisected). 671216 6 kbalazs 2012-07-17 06:03:35 -0700 Link of results: http://build.webkit.sed.hu/results/x86-64%20Linux%20Qt%20Release%20WebKit2%20(Amazon%20EC2)/r122771%20(6073)/results.html (it refers to 71 because 67-70 did not build). 671367 7 eric 2012-07-17 10:37:25 -0700 http://trac.webkit.org/changeset/122770 671370 8 eric 2012-07-17 10:38:46 -0700 Links make it easy to see what the change in question was. Also relating to the original bug may help get the attention of the authors of the original change, if that's your goal. 671399 9 simon.fraser 2012-07-17 11:00:20 -0700 I find it hard to believe that r122770 caused those changes. 672147 10 kbalazs 2012-07-18 02:14:29 -0700 (In reply to comment #8) > Links make it easy to see what the change in question was. Also relating to the original bug may help get the attention of the authors of the original change, if that's your goal. Not for making a flame war of it but what is the rationale of blocking a resolved bug? I commented on that bug, I believe it should be enough to get the attention of the authors. Links are good idea, though :) 677923 11 ossy 2012-07-25 04:42:44 -0700 *** This bug has been marked as a duplicate of bug 88064 ***