[Webkit-unassigned] [Bug 172925] New: Layout Test inspector/runtime/change-execution-context-identifier.html is flaky

[bugzilla-daemon at webkit.org]

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

            Bug ID: 172925
           Summary: Layout Test
                    inspector/runtime/change-execution-context-identifier.
                    html is flaky
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: New Bugs
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: jlewis3 at apple.com

inspector/runtime/change-execution-context-identifier.html is a flaky timeout.
According to the flakiness dashboard the test has been timing out on all macOS Debug configurations, starting with El Capitan. The first timeout on the dashboard was on 5/23/2017 with build https://build.webkit.org/builders/Apple%20El%20Capitan%20Debug%20WK2%20(Tests)/builds/1296

The test usually pass in 1-7 seconds but when it timeout out it is a consistent 35 seconds with a "waiting for notifyDone to be called".

History:
https://webkit-test-results.webkit.org/dashboards/flakiness_dashboard.html#showAllRuns=true&tests=inspector%2Fruntime%2Fchange-execution-context-identifier.html

recent build:
https://build.webkit.org/builders/Apple%20Sierra%20Debug%20WK1%20(Tests)/builds/1635
https://build.webkit.org/results/Apple%20Sierra%20Debug%20WK1%20(Tests)/r217778%20(1635)/results.html

diff:
--- /Volumes/Data/slave/sierra-debug-tests-wk1/build/layout-test-results/inspector/runtime/change-execution-context-identifier-expected.txt
+++ /Volumes/Data/slave/sierra-debug-tests-wk1/build/layout-test-results/inspector/runtime/change-execution-context-identifier-actual.txt
@@ -1,29 +1,3 @@
+FAIL: Timed out waiting for notifyDone to be called
+
 Test that RuntimeManager.evaluateInInspectedWindow respects the selected execution context.
-
-
-== Running test suite: RuntimeManager.activeExecutionContext
--- Running test case: InitialScriptExecutionContext
-PASS: The initial active execution context should be the main execution context.
-
--- Running test case: ScriptExecutionContextMainContext
-Passphrase in selected frame: coldwater
-PASS: The passphrase should match the phrase defined in the main frame.
-
--- Running test case: ScriptExecutionContextMainFrameContext
-Passphrase in selected frame: coldwater
-PASS: The passphrase should match the phrase defined in the main frame.
-
--- Running test case: ScriptExecutionContextSubFrame
-PASS: The test page should only have one sub-frame.
-Passphrase in selected frame: rosewater
-PASS: The passphrase should match the phrase defined in the subframe.
-
--- Running test case: ScriptExecutionContextMainFrameAgain
-Passphrase in selected frame: coldwater
-PASS: The passphrase should match the phrase defined in the main frame.
-
--- Running test case: ScriptExecutionContextRemoveSubframe
-PASS: The test page should only have one sub-frame.
-PASS: The test page should now have no sub-frames.
-PASS: When a selected non-top-level execution context is removed, the active execution context should revert to the main frame context.
-

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20170605/87470ddc/attachment.html>