Issue metadata
Sign in to add a comment
|
v8.runtimestats.browsing_mobile failing on chromium.perf/Android One Perf |
||||||||||||||||||||||
Issue descriptionv8.runtimestats.browsing_mobile failing on chromium.perf/Android One Perf Builders failed on: - Android One Perf: https://build.chromium.org/p/chromium.perf/builders/Android%20One%20Perf From logs: Exception raised while closing platform backend Traceback (most recent call last): __init__ at /b/swarming/w/ir/third_party/catapult/telemetry/telemetry/internal/browser/browser.py:70 self.Close() Close at /b/swarming/w/ir/third_party/catapult/telemetry/telemetry/internal/browser/browser.py:268 logging.info('Closing browser (pid=%s) ...', self._browser_backend.pid) pid at /b/swarming/w/ir/third_party/catapult/telemetry/telemetry/internal/backends/chrome/android_browser_backend.py:236 '%s' % (self._backend_settings.package, pids)) Exception: At most one instance of process org.chromium.chrome expected but found pids: defaultdict(<type 'list'>, {'org.chromium.chrome:sandboxed_process0': ['10156'], 'org.chromium.chrome': ['10125', '10224']}) Locals: pids : defaultdict(<type 'list'>, {'org.chromium.chrome:sandboxed_process0': ['10156'], 'org.chromium.chrome': ['10125', '10224']})
,
Sep 22 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/f753568b76eb830cc227669e43bdad6475eea9de commit f753568b76eb830cc227669e43bdad6475eea9de Author: Simon <simonhatch@chromium.org> Date: Fri Sep 22 20:29:16 2017 Disable pages on v8.runtimestats.browsing_mobile TBR=rnephew@chromium.org Bug: 767970 Change-Id: Ifffdc6628e0825d3c96efd8c8d47d28cae762070 Reviewed-on: https://chromium-review.googlesource.com/679263 Reviewed-by: Simon Hatch <simonhatch@chromium.org> Reviewed-by: rnephew <rnephew@chromium.org> Commit-Queue: Simon Hatch <simonhatch@chromium.org> Cr-Commit-Position: refs/heads/master@{#503837} [modify] https://crrev.com/f753568b76eb830cc227669e43bdad6475eea9de/tools/perf/benchmarks/v8_browsing.py
,
Sep 26 2017
Update: the following stories are failing consistently on mobile: browse:shopping:flipkart browse:news:cnn We need to disable them on all mobile.
,
Sep 26 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/fa355f0035fa621cdb4de9a778984cf564aa6c63 commit fa355f0035fa621cdb4de9a778984cf564aa6c63 Author: Ned Nguyen <nednguyen@google.com> Date: Tue Sep 26 19:12:53 2017 Disable failing mobile stories of v8.runtimestats.browsing_mobile benchmark Bug: 767970 Change-Id: I9d8ccbd188c4e38bf1059d7b850ccc43b1a079c4 Reviewed-on: https://chromium-review.googlesource.com/684617 Reviewed-by: Ned Nguyen <nednguyen@google.com> Reviewed-by: Annie Sullivan <sullivan@chromium.org> Commit-Queue: Ned Nguyen <nednguyen@google.com> Cr-Commit-Position: refs/heads/master@{#504450} [modify] https://crrev.com/fa355f0035fa621cdb4de9a778984cf564aa6c63/tools/perf/benchmarks/v8_browsing.py
,
Oct 12 2017
browse:news:cnn is failing because of crbug.com/759777 . alph@ is looking into it. I think flipkart is failing on all of the benchmarks. v8.browse, v8.runtimestats.browse and system_heath. It fails while waiting for javascript condition when I run it locally. I suspect it is the problem with the page. Is there another bug for flipkart?
,
Oct 13 2017
Also cc'ing ssid@ who recorded the page.
,
Dec 13 2017
,
Dec 14 2017
,
Dec 14 2017
Flipkart not running at all sounds serious.
,
Dec 14
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 17
This bot no longer exists. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by simonhatch@chromium.org
, Sep 22 2017