Bug 210062

Summary: [ macOS ] inspector/debugger/break-in-constructor-before-super.html is a flaky failure
Product: WebKit Reporter: Jacob Uphoff <jacob_uphoff>
Component: New BugsAssignee: Devin Rousso <hi>
Status: RESOLVED FIXED    
Severity: Normal CC: hi, timothy, webkit-bot-watchers-bugzilla, webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Patch none

Jacob Uphoff
Reported 2020-04-06 11:33:54 PDT
inspector/debugger/break-in-constructor-before-super.html This test has been a flaky failure for all visible history on macOS debug for wk1 & wk2 History: https://results.webkit.org/?suite=layout-tests&test=inspector%2Fdebugger%2Fbreak-in-constructor-before-super.html&limit=50000 Diff: --- /Volumes/Data/slave/catalina-debug-tests-wk1/build/layout-test-results/inspector/debugger/break-in-constructor-before-super-expected.txt +++ /Volumes/Data/slave/catalina-debug-tests-wk1/build/layout-test-results/inspector/debugger/break-in-constructor-before-super-actual.txt @@ -5,7 +5,5 @@ == Running test suite: PauseInConstructorBeforeSuper -- Running test case: TriggerPauseInConstructorBeforeSuper -PASS: Paused -PASS: `this` should be undefined and not cause a crash. -PASS: Resumed +!! TIMEOUT: took longer than 10000ms
Attachments
Patch (3.15 KB, patch)
2020-06-05 20:23 PDT, Devin Rousso 		no flags
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1 2020-04-06 11:34:13 PDT
<rdar://problem/61351481>
Jacob Uphoff
Comment 2 2020-04-06 11:55:47 PDT
Set expectations here: https://trac.webkit.org/changeset/259586/webkit
Devin Rousso
Comment 3 2020-06-05 20:23:59 PDT
Created attachment 401229 [details] Patch this fixed the test for me with 1000 iterations
EWS
Comment 4 2020-06-06 05:51:55 PDT
Committed r262674: <https://trac.webkit.org/changeset/262674> All reviewed patches have been landed. Closing bug and clearing flags on attachment 401229 [details].
Note You need to log in before you can comment on or make changes to this bug.