Bug 176071 - Layout Test inspector/debugger/breakpoints/resolved-dump-each-line.html is flaky.
Summary: Layout Test inspector/debugger/breakpoints/resolved-dump-each-line.html is fl...
Status: RESOLVED CONFIGURATION CHANGED
Alias: None
Product: WebKit
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-08-29 15:09 PDT by Matt Lewis
Modified: 2017-09-13 15:18 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-08-29 15:09:32 PDT
inspector/debugger/breakpoints/resolved-dump-each-line.html is a flaky timeout and failure. Currently the test is marked as a flaky timeout on macOS after this bug: https://bugs.webkit.org/show_bug.cgi?id=161951

History:
https://webkit-test-results.webkit.org/dashboards/flakiness_dashboard.html#showAllRuns=true&tests=inspector%2Fdebugger%2Fbreakpoints%2Fresolved-dump-each-line.html

Currently the test has begun to occasionally fail on Sierra WK2 Release according to the dashboard. There is not a clear regression point however the first failure was with this build:
https://build.webkit.org/builders/Apple%20Sierra%20Release%20WK2%20(Tests)/builds/3577


current builds:

https://build.webkit.org/results/Apple%20Sierra%20Release%20WK2%20(Tests)/r221307%20(3918)/results.html
https://build.webkit.org/builders/Apple%20Sierra%20Release%20WK2%20(Tests)/builds/3918

Diff:

--- /Volumes/Data/slave/sierra-release-tests-wk2/build/layout-test-results/inspector/debugger/breakpoints/resolved-dump-each-line-expected.txt
+++ /Volumes/Data/slave/sierra-release-tests-wk2/build/layout-test-results/inspector/debugger/breakpoints/resolved-dump-each-line-actual.txt
@@ -4487,4 +4487,5 @@
 
 INSERTING AT: 4:0
 PRODUCES: Could not resolve breakpoint
-
+ERROR: TypeError: this._dispatcher is not an Object. (evaluating 'eventName in this._dispatcher')
+
Comment 1 Joseph Pecoraro 2017-09-13 15:18:05 PDT
I have discovered what can cause this. I've made sure tests register a ScriptProfilerObserver and I've made the error message clear about which domain is missing having a dispatcher registered:

    ERROR: No domain dispatcher registered for domain 'ScriptProfiler'

So this shouldn't happen anymore, and if it does we have a clear path to a solution. Closing this.