Bug 172925 - Layout Test inspector/runtime/change-execution-context-identifier.html is flaky
Summary: Layout Test inspector/runtime/change-execution-context-identifier.html is flaky
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: Web Inspector (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-06-05 10:15 PDT by Matt Lewis
Modified: 2017-06-05 13:58 PDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Matt Lewis 2017-06-05 10:15:50 PDT
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.
-