bug 912806 caused a regression in talos tcheck2 scores. This was known at the time bug 912806 landed, but that bug fixed a more important visual regression so I landed it anyway (see bug 912806 comment 27). I don't believe that this is an actual regression, but that some of the resolution changes affect how the score for this test is reported. My first guess would be to check the code in ComputeRenderIntegrity to see if it uses the resolution or composition bounds and if that needs to be updated.

Also for the record bug 912806 did *not* regress eideticker. In fact it improved eideticker checkerboarding scores, as expected (since it fixed a previous checkerborading regression). See bug 915387 which was filed for the eideticker regression and is now fixed. This adds weight to my theory that this tcheck2 regression is just a measurement change with no user-visible impact.

I was just about to file a bug for this because I noticed that although my patches for bug 913683 appear to have brought tpan numbers back down, they did not fix tcheck2 at all. In fact, they seem to have reduced noise on 2.2 and made the tcheck2 numbers consistently higher, so maybe there is some real regression here. Either that, or this test is just incorrect. http://graphs.mozilla.org/graph.html#tests=[[201,11,20]]&sel=none&displayrange=30&datatype=running http://graphs.mozilla.org/graph.html#tests=[[201,11,29]]&sel=none&displayrange=30&datatype=running

Bug 732971 has now brought this back down to previous levels (and maybe even a bit lower).