[Webkit-unassigned] [Bug 97112] New: REGRESSION (r126189): No more mismatch-did-not-occur failures in reftests

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=97112

           Summary: REGRESSION (r126189): No more mismatch-did-not-occur
                    failures in reftests
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: Unspecified
        OS/Version: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Tools / Tests
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: zandobersek at gmail.com
                CC: ossy at webkit.org, ojan at chromium.org,
                    dpranke at chromium.org


On GTK (and possibly other platforms as well, though most skip the test) when running fast/harness/sample-fail-mismatch-reftest.html the following output is shown, originating from SingleTestRunner[1]:
fast/harness/sample-fail-mismatch-reftest.html -> ref test hashes matched but diff failed

The test is expected to (and should) fail but actually passes, that is the reftest matches with its expected mismatch and that's considered an error. The output indicates ImageDiff does not produce the diff image event though there are no differences. I believe this is the current behavior of pixel dumping code throughout platforms when the actual hash matches the expected one[3][4][5]. 

[1] http://trac.webkit.org/browser/trunk/Tools/Scripts/webkitpy/layout_tests/controllers/single_test_runner.py#L328
[2] http://trac.webkit.org/changeset/126189
[3] http://trac.webkit.org/browser/trunk/Tools/DumpRenderTree/PixelDumpSupport.cpp#L71
[4] http://trac.webkit.org/browser/trunk/Tools/DumpRenderTree/qt/DumpRenderTreeQt.cpp#L962
[5] http://trac.webkit.org/browser/trunk/Tools/DumpRenderTree/chromium/TestShell.cpp#L708

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.