Bug 147713
| Summary: | Web Inspector: inspector-protocol/console/css-source-locations.html times out when repeated | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Blaze Burg <bburg> |
| Component: | Web Inspector | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED CONFIGURATION CHANGED | ||
| Severity: | Normal | CC: | ap, bburg, graouts, hi, joepeck, mattbaker, nvasilyev, timothy, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | 528+ (Nightly build) | ||
| Hardware: | All | ||
| OS: | All | ||
Blaze Burg
This does not affect the bots currently, but it smells like a problem.
Exposed by the command:
Tools/Scripts/run-webkit-tests --time-out-ms=3000 --iterations=10 inspector-protocol/console/css-source-locations.html
When it times out, the console messages from the external <link> stylesheet are not logged. I think there is a race somewhere that's only exposed when the page is already in the cache. Or, maybe those console messages go to the previous test page somehow? It needs more investigation.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Blaze Burg
Devin suggested that perhaps we did not disable the Console when the test is finished, and thus the next execution's console messages are not enqueued in the backend and get dropped on the floor.
I tried sending "Console.disable" before calling InspectorTest.completeTest(), but this did not seem to have any effect.
David Kilzer (:ddkilzer)
<rdar://problem/28229374>
Joseph Pecoraro
No inspector-protocol tests exist anymore.