inspector/debugger/tail-deleted-frames/tail-deleted-frames-scopes.html This test has been flaky timing out and you can see the first time out on commit 253875 Seems to only be affecting debug on wk1 Ran iteration test x500 and did not get a timeout History: https://results.webkit.org/?suite=layout-tests&test=inspector%2Fdebugger%2Ftail-deleted-frames%2Ftail-deleted-frames-scopes.html&limit=50000 Diff: --- /Volumes/Data/slave/catalina-debug-tests-wk1/build/layout-test-results/inspector/debugger/tail-deleted-frames/tail-deleted-frames-scopes-expected.txt +++ /Volumes/Data/slave/catalina-debug-tests-wk1/build/layout-test-results/inspector/debugger/tail-deleted-frames/tail-deleted-frames-scopes-actual.txt @@ -1,29 +1,2 @@ +FAIL: Timed out waiting for notifyDone to be called Ensure proper scopes in tail deleted frames. - - -== Running test suite: Debugger.TailDeletedFrames.Scopes --- Running test case: Debugger.TailDeletedFrames.Scopes -PAUSED -CALL STACK: -0: [F] a - ----Scope---- - x: 20 - ------------- -1: -F- b - ----Scope---- - y: 40 - ------------- -2: -F- c - ----Scope---- - z: 60 - ------------- -3: [F] startABC - ----Scope---- - -- empty -- - ------------- -4: [P] Global Code - ----Scope---- - -- empty -- - ------------- -RESUMED -
<rdar://problem/59128753>
Created attachment 389583 [details] Update Test Expectations
Comment on attachment 389583 [details] Update Test Expectations Clearing flags on attachment: 389583 Committed r255612: <https://trac.webkit.org/changeset/255612>
> This test has been flaky timing out and you can see the first time out on commit 253875 This doesn't seem right, I see timeouts older than that, e.g. with r251183. Given how rare these are, I think that this counts as "all visible history".