NEW 180703
Layout Test http/tests/resourceLoadStatistics/telemetry-generation.html is flaky 
https://bugs.webkit.org/show_bug.cgi?id=180703
Summary Layout Test http/tests/resourceLoadStatistics/telemetry-generation.html is flaky
Ryan Haddad
Reported 2017-12-12 10:56:10 PST
The following layout test is flaky on macOS WK2: http/tests/resourceLoadStatistics/telemetry-generation.html Flakiness Dashboard: https://webkit-test-results.webkit.org/dashboards/flakiness_dashboard.html#showAllRuns=true&tests=http%2Ftests%2FresourceLoadStatistics%2Ftelemetry-generation.html --- /Volumes/Data/slave/sierra-release-tests-wk2/build/layout-test-results/http/tests/resourceLoadStatistics/telemetry-generation-expected.txt +++ /Volumes/Data/slave/sierra-release-tests-wk2/build/layout-test-results/http/tests/resourceLoadStatistics/telemetry-generation-actual.txt @@ -8,10 +8,11 @@ PASS testResult.totalPrevalentResourcesWithUserInteraction is 0 PASS testResult.top3SubframeUnderTopFrameOrigins is 0 PASS Hosts classified as prevalent resources. -PASS testResult.totalPrevalentResources is 4 -PASS testResult.totalPrevalentResourcesWithUserInteraction is 1 -PASS testResult.top3SubframeUnderTopFrameOrigins is 4 +FAIL testResult.totalPrevalentResources should be 4. Was 0. +FAIL testResult.totalPrevalentResourcesWithUserInteraction should be 1. Was 0. +FAIL testResult.top3SubframeUnderTopFrameOrigins should be 4. Was 0. PASS successfullyParsed is true +Some tests failed. TEST COMPLETE
Attachments
Add attachment proposed patch, testcase, etc.
Ryan Haddad
Comment 1 2017-12-12 10:56:46 PST
Started after the resourceLoadStatistics test directory move in https://trac.webkit.org/changeset/225640/webkit
Matt Lewis
Comment 2 2017-12-18 13:34:26 PST
Marked as flaky in https://trac.webkit.org/changeset/226074/webkit
Ryan Haddad
Comment 3 2017-12-21 10:10:12 PST
(In reply to Matt Lewis from comment #2) > Marked as flaky in https://trac.webkit.org/changeset/226074/webkit This marked the wrong test as flaky. Fixed in https://trac.webkit.org/r226227
Note You need to log in before you can comment on or make changes to this bug.