Bug 141591
| Summary: | [EFL] 3 inspector tests are being failed | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Gyuyoung Kim <gyuyoung.kim> |
| Component: | WebKit EFL | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | Normal | CC: | chavarria1991, lucas.de.marchi, mcatanzaro, mpakulavelrutka |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Bug Depends on: | |||
| Bug Blocks: | 93353 | ||
Gyuyoung Kim
3 inspector tests regarding breakpoint are being failed. Those tests were added by r159110
inspector-protocol/debugger/breakpoint-eval-with-exception.html [ Failure ]
inspector-protocol/debugger/setBreakpoint-actions.html [ Failure ]
inspector-protocol/debugger/setBreakpoint-dfg-callee-and-examine-dfg-local.html [ Failure ]
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Marcos ChavarrÃa Teijeiro (irc: chavaone)
Layout test inspector-protocol/debugger/breakpoint-eval-with-exception.html is also failing on GTK+ since r178137 (https://trac.webkit.org/changeset/r178137).
--- /home/ch01/wk-tools/layout-test-results/inspector-protocol/debugger/breakpoint-eval-with-exception-expected.txt
+++ /home/ch01/wk-tools/layout-test-results/inspector-protocol/debugger/breakpoint-eval-with-exception-actual.txt
@@ -2,6 +2,6 @@
Found breakpoint.js
inside breakpointBasic
-PASS: Paused in debugger: reason = "other"
+PASS: Paused in debugger: reason = "Breakpoint"
PASS: The debugger should not stop on the exception thrown by a console command while paused on a breakpoint.
Michal Pakula vel Rutka
inspector-protocol/debugger/setBreakpoint-dfg-callee-and-examine-dfg-local.html started to pass on EFL port after r182167 <http://trac.webkit.org/changeset/182167>
Marcos ChavarrÃa Teijeiro (irc: chavaone)
inspector-protocol/debugger/breakpoint-eval-with-exception.html is passing on GTK since r183665 (http://trac.webkit.org/changeset/183665).
Michael Catanzaro
Closing this bug because the EFL port has been removed from trunk.
If you feel this bug applies to a different upstream WebKit port and was closed in error, please either update the title and reopen the bug, or leave a comment to request this.