Turning down ignition specific benchmark once the project is launched |
||||||
Issue descriptionPlease turn down ignition specific benchmark once the project is launched. +V8 folks: who can I assign this bug to?
,
Dec 1 2016
Tagging with current canary milestone.
,
Dec 1 2016
Ignition won't be launched in m57 so I don't think this is something we want to tag with m57. I can own this bug, I'll make sure to turn down the benchmarks when we launch.
,
Dec 5 2016
,
Feb 23 2017
,
Mar 9 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/44befe2158754becde45c5a07519f5d72aca54a9 commit 44befe2158754becde45c5a07519f5d72aca54a9 Author: Mythri Alle <mythria@chromium.org> Date: Thu Mar 09 11:10:21 2017 Removes the following benchmarks: * speedometer-ignition * v8.browse_desktop_ignition * v8.browse_mobile_ignition, * v8.infiniter_scroll-ignition_tbmv2 * v8.todoMVC-ignition The ignition-staging configuration of v8 used in these benchmarks is no longer the shipping configuration. The corresponding turbo benchmarks are tracking the future shipping configuration of v8. BUG= chromium:670087 Change-Id: Ic7b8d8e69ec2f1aafff750fa07c516d90824e611 Reviewed-on: https://chromium-review.googlesource.com/451657 Commit-Queue: Mythri Alle <mythria@chromium.org> Reviewed-by: Ned Nguyen <nednguyen@google.com> Cr-Commit-Position: refs/heads/master@{#455709} [modify] https://crrev.com/44befe2158754becde45c5a07519f5d72aca54a9/testing/buildbot/chromium.perf.fyi.json [modify] https://crrev.com/44befe2158754becde45c5a07519f5d72aca54a9/testing/buildbot/chromium.perf.json [modify] https://crrev.com/44befe2158754becde45c5a07519f5d72aca54a9/tools/perf/benchmarks/speedometer.py [modify] https://crrev.com/44befe2158754becde45c5a07519f5d72aca54a9/tools/perf/benchmarks/v8.py [modify] https://crrev.com/44befe2158754becde45c5a07519f5d72aca54a9/tools/perf/benchmarks/v8_browsing.py [modify] https://crrev.com/44befe2158754becde45c5a07519f5d72aca54a9/tools/perf/benchmarks/v8_helper.py
,
Mar 13 2017
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by u...@chromium.org
, Dec 1 2016