RESOLVED INVALID 86683
Web Inspector: heap-snapshot-summary-show-ranges.html shows "Profiler was disabled" twice
https://bugs.webkit.org/show_bug.cgi?id=86683
Summary Web Inspector: heap-snapshot-summary-show-ranges.html shows "Profiler was dis...
Peter Kasting
Reported 2012-05-16 15:20:05 PDT
See http://test-results.appspot.com/dashboards/flakiness_dashboard.html#showExpectations=true&tests=inspector%2Fprofiler%2Fheap-snapshot-summary-show-ranges.html . For some reason the Windows and Linux debug bots have started showing "Profiler was disabled." twice at the end of the test. The Linux bot regression range includes http://trac.webkit.org/changeset/117241/ , hence my assignee for this bug; but the Windows bot range stops one revision shy. I'm mystified. The only change these both have in common is http://src.chromium.org/viewvc/chrome?view=rev&revision=137387 , but pliard doesn't seem to have a WebKit bugzilla account I can find. Can you inspector guys triage? Meanwhile I'm marking this test as expected to fail.
Attachments
Peter Kasting
Comment 1 2012-05-16 16:29:20 PDT
Marked failing from Win & Linux debug in r117360.
Yury Semikhatsky
Comment 2 2012-05-17 10:01:22 PDT
As I can see it is WebKit blamelist r117233:r117240 for Wind(dbg) and WebKit blamelist r117238:r117241 for Linux(dbg) which gives us r117238:r117240 in intersection(http://trac.webkit.org/log/?verbose=on&rev=117240&stop_rev=117238) and all the patches in the range are EFL-specific, not sure how the could affect the heap profiler test.
Yury Semikhatsky
Comment 3 2012-05-17 10:06:23 PDT
(In reply to comment #2) > As I can see it is > WebKit blamelist r117233:r117240 for Wind(dbg) and > WebKit blamelist r117238:r117241 for Linux(dbg) which gives us > > r117238:r117240 in intersection(http://trac.webkit.org/log/?verbose=on&rev=117240&stop_rev=117238) and all the patches in the range are EFL-specific, not sure how the could affect the heap profiler test. Both bots have been red since the run when heap-snapshot-summary-show-ranges.html started failing. I suspect there might be something wrong with them.
Brian Burg
Comment 4 2014-12-12 14:37:20 PST
Closing as invalid, as this bug pertains to the old inspector UI and/or its tests. Please file a new bug (https://www.webkit.org/new-inspector-bug) if the bug/feature/issue is still relevant to WebKit trunk.
Note You need to log in before you can comment on or make changes to this bug.