WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED DUPLICATE of
bug 136715
123489
Mavericks WK2: inspector-protocol/debugger/call-frame-this-strict.html and setBreakpoint-column.html are flaky
https://bugs.webkit.org/show_bug.cgi?id=123489
Summary
Mavericks WK2: inspector-protocol/debugger/call-frame-this-strict.html and se...
Ryosuke Niwa
Reported
2013-10-29 20:43:37 PDT
http://webkit-test-results.appspot.com/dashboards/flakiness_dashboard.html#tests=inspector-protocol%2Fdebugger%2Fcall-frame-this-strict.html%2Cinspector-protocol%2Fdebugger%2FsetBreakpoint-column.html
e.g.
http://build.webkit.org/results/Apple%20Mavericks%20Release%20WK2%20(Tests)/r158244%20(82)/results.html
--- /Volumes/Data/slave/mavericks-release-tests-wk2/build/layout-test-results/inspector-protocol/debugger/call-frame-this-strict-expected.txt +++ /Volumes/Data/slave/mavericks-release-tests-wk2/build/layout-test-results/inspector-protocol/debugger/call-frame-this-strict-actual.txt @@ -1,12 +1,8 @@ -Debugger.setBreakpoint on line:column in <script> - -Breakpoints Enabled -Found <script> -Running testFunction -PASS: step 0: type "number" value "2" -PASS: step 1: type "string" value "Hello" -PASS: step 2: type "number" value "2" -PASS: step 3: type "string" value "Hello" -PASS: step 4: type "undefined" value "undefined" -PASS: step 5: type "undefined" value "undefined" - +layer at (0,0) size 800x600 + RenderView at (0,0) size 800x600 +layer at (0,0) size 800x600 + RenderBlock {HTML} at (0,0) size 800x600 + RenderBody {BODY} at (8,8) size 784x576 + RenderBlock {P} at (0,0) size 784x18 + RenderText {#text} at (0,0) size 324x18 + text run at (0,0) width 324: "Debugger.setBreakpoint on line:column in <script>" --- /Volumes/Data/slave/mavericks-release-tests-wk2/build/layout-test-results/inspector-protocol/debugger/setBreakpoint-column-expected.txt +++ /Volumes/Data/slave/mavericks-release-tests-wk2/build/layout-test-results/inspector-protocol/debugger/setBreakpoint-column-actual.txt @@ -1,9 +1,8 @@ -Debugger.setBreakpoint on line:column in <script> - -Breakpoints Enabled -Found <script> -Running testFunction -Hit Breakpoint! -Evaluted value of `a` (expecting number 1) was: {"type":"number","value":1,"description":"1"} -Evaluted value of `b` (expecting undefined) was: {"type":"undefined"} - +layer at (0,0) size 800x600 + RenderView at (0,0) size 800x600 +layer at (0,0) size 800x600 + RenderBlock {HTML} at (0,0) size 800x600 + RenderBody {BODY} at (8,8) size 784x576 + RenderBlock {P} at (0,0) size 784x18 + RenderText {#text} at (0,0) size 324x18 + text run at (0,0) width 324: "Debugger.setBreakpoint on line:column in <script>"
Attachments
Add attachment
proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1
2013-10-29 20:43:49 PDT
<
rdar://problem/15348400
>
Ryosuke Niwa
Comment 2
2013-10-29 23:51:34 PDT
Same problem on inspector-protocol/debugger/setBreakpoint-options-exception.html
http://build.webkit.org/results/Apple%20Mavericks%20Release%20WK2%20(Tests)/r158255%20(92)/results.html
Timothy Hatcher
Comment 3
2013-10-30 06:08:49 PDT
It seems like a tool issue where it isn't dumping as text.
Ryosuke Niwa
Comment 4
2013-10-30 11:00:19 PDT
I think there might be some race here. Either load event handler isn't called or someone is calling notifyDone too soon. e.g. previous test may have scheduled setTimeout that calls notifyDone.
Joseph Pecoraro
Comment 5
2013-10-30 11:36:51 PDT
We can probably remove some setTimeout's from earlier tests, but how are they suddenly leaking between tests… this might be a WebCore / Tools issue.
Alexey Proskuryakov
Comment 6
2014-09-10 14:47:15 PDT
I think that most of these tests are affected by problems leaked from previous tests. Let's track this in
bug 136715
, which has more detail.
Alexey Proskuryakov
Comment 7
2014-09-10 15:13:49 PDT
*** This bug has been marked as a duplicate of
bug 136715
***
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug