New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 717392 link

Starred by 1 user
Status: Fixed
Owner:
dbasehore@chromium.org
Closed: Sep 28
Cc:
derat@chromium.org
█ ejcaruso@chromium.org
tbroch@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

power_Consumption: v8 benchmark is gone

Project Member Reported by dbasehore@chromium.org, May 2 2017 
It seems that the v8 benchmark that we use for this test is gone. The url in question is http://v8.googlecode.com/svn/data/benchmarks/v7/run.html

We could either put the site in the static_sites.tgz.keep archive, or update the benchmark to Speedometer (or some other benchmark) instead.

I personally prefer just changing to Speedometer. If no one has strong opinions on the topic, I'll switch to that.

Comment 1 by tbroch@chromium.org, May 2 2017 

seems like its been gone for a while,

https://web.archive.org/web/20160506085502/http://v8.googlecode.com/svn/data/benchmarks/v7/run.html

5/6/2016 was the last I could find it.

I'm fine w/ picking another representative V8 benchmark.

My only reservation w/ speedometer is my run was >1min runtime when it 'awww snapped' on mac OSX running chrome. Hopefully thats a one-off ... it did run successfully after a reload.

Original benchmark appears to have been re-landed here: http://www.netchain.com/Tools/v8 if thats an easier short-term fix.

Comment 2 by dbasehore@chromium.org, May 2 2017 

The move isn't particularly hard to make. I'll just move forward with speedometer.
Project Member

Comment 3 by bugdroid1@chromium.org, May 4 2017 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/autotest/+/0ed7f1bb11a8d9bf020431f4aa001e188c469d5e

commit 0ed7f1bb11a8d9bf020431f4aa001e188c469d5e
Author: Derek Basehore <dbasehore@chromium.org>
Date: Thu May 04 13:07:00 2017

autotest: Change v8 subtest to speedometer in power_Consumption

The v8 benchmark that power_Consumption was linking to went away.
Since that benchmark is now depricated, let's move to Speedometer
which is a better benchmark.

BUG= chromium:717392 
TEST=power_Consumption

Change-Id: Ie5417828e31f7e62759110edfa1daba68acaaead
Reviewed-on: https://chromium-review.googlesource.com/494076
Commit-Ready: Hsinyu Chao <hychao@chromium.org>
Tested-by: Derek Basehore <dbasehore@chromium.org>
Reviewed-by: Derek Basehore <dbasehore@chromium.org>

[modify] https://crrev.com/0ed7f1bb11a8d9bf020431f4aa001e188c469d5e/client/site_tests/power_Consumption/control
[modify] https://crrev.com/0ed7f1bb11a8d9bf020431f4aa001e188c469d5e/client/site_tests/power_Consumption/power_Consumption.py

Comment 4 by zalcorn@chromium.org, Sep 28 

Triage nag: This Chrome OS bug has an owner but no component. Please add a component so that this can be tracked by the relevant team.

Comment 5 by dbasehore@chromium.org, Sep 28

Status: Fixed (was: Assigned)
Huh, I forgot to mark this fixed.

Comment 6 by dbasehore@chromium.org, Sep 28

Components: Tests
►

Sign in to add a comment