The following layout tests are flaky (TEXT) on XP: fast/history/history-subframe-with-name.html fast/history/history-traversal-is-asynchronous.html http://test-results.appspot.com/dashboards/flakiness_dashboard.html#tests=fast%2Fhistory%2Fhistory-subframe-with-name.html%2Cfast%2Fhistory%2Fhistory-traversal-is-asynchronous.html Flakiness predates WKr117722 and CRr138073 Diff is of the form: --- e:\b\build\slave\Webkit_Win\build\layout-test-results\fast/history/history-subframe-with-name-expected.txt +++ e:\b\build\slave\Webkit_Win\build\layout-test-results\fast/history/history-subframe-with-name-actual.txt @@ -1,4 +1,3 @@ -main frame - has 1 onunload handler(s) main frame - has 1 onunload handler(s) main frame - has 1 onunload handler(s) Verifies that we can go back and forward from the top level of a frame set where a window changes its name after the initial load. --- e:\b\build\slave\Webkit_Win\build\layout-test-results\fast/history/history-traversal-is-asynchronous-expected.txt +++ e:\b\build\slave\Webkit_Win\build\layout-test-results\fast/history/history-traversal-is-asynchronous-actual.txt @@ -1,3 +1,4 @@ +main frame - has 1 onunload handler(s) Checks that session history traversal is done asynchronously. On success, you will see a series of "PASS" messages, followed by "TEST COMPLETE".
> fast/history/history-subframe-with-name.html This was already tracked in bug 51039. > fast/history/history-traversal-is-asynchronous.html Not flaky any more. Was probably a leak from preceding test, likely fixed with some improvement to DumpRenderTree logging. *** This bug has been marked as a duplicate of bug 51039 ***