Bug 206955

Summary: [ macOS wk1 ] inspector/debugger/breakpoints/resolved-dump-each-line.html is flaky failing
Product: WebKit Reporter: Jacob Uphoff <jacob_uphoff>
Component: Web InspectorAssignee: Nobody <webkit-unassigned>
Status: NEW    
Severity: Normal CC: inspector-bugzilla-changes, tsavell, webkit-bot-watchers-bugzilla, webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Update Test Expectations none

Jacob Uphoff
Reported 2020-01-29 11:54:20 PST
inspector/debugger/breakpoints/resolved-dump-each-line.html This test is a flaky failure on macOS wk1 on Catalina and Mojave release This failure appears to be a timeout failure in the test according to the diff. I was able to reproduce this simply by running the test in iterations. History: https://results.webkit.org/?suite=layout-tests&test=inspector%2Fdebugger%2Fbreakpoints%2Fresolved-dump-each-line.html Diff: --- /Volumes/Data/slave/catalina-release-tests-wk1/build/layout-test-results/inspector/debugger/breakpoints/resolved-dump-each-line-expected.txt +++ /Volumes/Data/slave/catalina-release-tests-wk1/build/layout-test-results/inspector/debugger/breakpoints/resolved-dump-each-line-actual.txt @@ -3041,6 +3041,7 @@ INSERTING AT: 210:0 PRODUCES: Could not resolve breakpoint +!! TIMEOUT: took longer than 10000ms -- Running test case: Debugger.resolvedBreakpoint.dumpEachLine.Functions
Attachments
Update Test Expectations (1.83 KB, patch)
2020-01-29 11:58 PST, Jacob Uphoff 		no flags
DetailsFormatted DiffDiff
Show Obsolete (1) View All Add attachment proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1 2020-01-29 11:54:43 PST
<rdar://problem/59000471>
Jacob Uphoff
Comment 2 2020-01-29 11:58:25 PST
Created attachment 389169 [details] Update Test Expectations
Truitt Savell
Comment 3 2020-01-29 13:00:45 PST
Comment on attachment 389169 [details] Update Test Expectations Clearing flags on attachment: 389169 Committed r255377: <https://trac.webkit.org/changeset/255377>
Note You need to log in before you can comment on or make changes to this bug.