Fix test media files, that were incorrectly checked-in earlier.

Remove media files used with tough_video_cases in favor of uploading them to google storage. 

Later CL commits local .sha1 files to link to uploaded media files.

BUG=261318
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=216921

[shadi, 2013-07-23 20:26:38]

PTAL

These are the same media files crrev.com/20002004 on behalf of anancd@.

[anandc, 2013-07-23 20:34:38]

On 2013/07/23 20:26:38, shadi wrote:
> PTAL
> 
> These are the same media files crrev.com/20002004 on behalf of anancd@.

LGTM % (anancd@ = anandc@) :-)

[shadi, 2013-07-24 16:27:03]

PING. I need an OWNER's LGTM.

[tonyg, 2013-07-24 16:35:03]

On 2013/07/24 16:27:03, shadi wrote:
> PING. I need an OWNER's LGTM.

How big are these files in total? We try to avoid checking large binary files
into src.

[shadi, 2013-07-24 16:54:41]

On 2013/07/24 16:35:03, tonyg wrote:
> On 2013/07/24 16:27:03, shadi wrote:
> > PING. I need an OWNER's LGTM.
> 
> How big are these files in total? We try to avoid checking large binary files
> into src.

Good point. I think they are large enough (~130MB). 

Is there a telemetry_test data svn we can use? We can probably check it in to a
public repo and check it out on bots running media benchmark. We used to use
http://src.chromium.org/svn/trunk/deps/avperf/ for such purposes. 

WDYT?

[tonyg, 2013-07-24 17:03:47]

On Wed, Jul 24, 2013 at 9:54 AM,  <shadi@chromium.org> wrote:
> On 2013/07/24 16:35:03, tonyg wrote:
>>
>> On 2013/07/24 16:27:03, shadi wrote:
>> > PING. I need an OWNER's LGTM.
>
>
>> How big are these files in total? We try to avoid checking large binary
>> files
>> into src.
>
>
> Good point. I think they are large enough (~130MB).

Thanks for checking. That is way larger than anything we should check into src.

>
> Is there a telemetry_test data svn we can use? We can probably check it in
> to a
> public repo and check it out on bots running media benchmark. We used to use
> http://src.chromium.org/svn/trunk/deps/avperf/ for such purposes.
>
> WDYT?

avperf sounds great. There is also chrome/test/data/perf if that is
helpful. We should be able to just check whatever repo you stash it in
in the DEPS file (see existing cases of chrome/test/data/perf in
src/DEPS).

>
> https://codereview.chromium.org/19784011/

[dtu, 2013-07-24 17:04:22]

On 2013/07/24 16:54:41, shadi wrote:
> On 2013/07/24 16:35:03, tonyg wrote:
> > On 2013/07/24 16:27:03, shadi wrote:
> > > PING. I need an OWNER's LGTM.
> > 
> > How big are these files in total? We try to avoid checking large binary
files
> > into src.
> 
> Good point. I think they are large enough (~130MB). 
> 
> Is there a telemetry_test data svn we can use? We can probably check it in to
a
> public repo and check it out on bots running media benchmark. We used to use
> http://src.chromium.org/svn/trunk/deps/avperf/ for such purposes. 
> 
> WDYT?

We do have a Google Cloud Storage bucket, 'chromium-wpr', that we can stick
large files in, and telemetry has a module to download files from there,
telemetry.page.cloud_storage.

[shadi, 2013-07-24 17:10:46]

On 2013/07/24 17:04:22, Dave Tu wrote:
> On 2013/07/24 16:54:41, shadi wrote:
> > On 2013/07/24 16:35:03, tonyg wrote:
> > > On 2013/07/24 16:27:03, shadi wrote:
> > > > PING. I need an OWNER's LGTM.
> > > 
> > > How big are these files in total? We try to avoid checking large binary
> files
> > > into src.
> > 
> > Good point. I think they are large enough (~130MB). 
> > 
> > Is there a telemetry_test data svn we can use? We can probably check it in
to
> a
> > public repo and check it out on bots running media benchmark. We used to use
> > http://src.chromium.org/svn/trunk/deps/avperf/ for such purposes. 
> > 
> > WDYT?
> 
> We do have a Google Cloud Storage bucket, 'chromium-wpr', that we can stick
> large files in, and telemetry has a module to download files from there,
> telemetry.page.cloud_storage.

Nice! how can I add stuff to the cloud bucket? Do I need to add code to download
those files in our benchmarks, or does telemetry download all automatically?

[dtu, 2013-07-24 19:13:17]

On 2013/07/24 17:10:46, shadi wrote:
> On 2013/07/24 17:04:22, Dave Tu wrote:
> > On 2013/07/24 16:54:41, shadi wrote:
> > > On 2013/07/24 16:35:03, tonyg wrote:
> > > > On 2013/07/24 16:27:03, shadi wrote:
> > > > > PING. I need an OWNER's LGTM.
> > > > 
> > > > How big are these files in total? We try to avoid checking large binary
> > files
> > > > into src.
> > > 
> > > Good point. I think they are large enough (~130MB). 
> > > 
> > > Is there a telemetry_test data svn we can use? We can probably check it in
> to
> > a
> > > public repo and check it out on bots running media benchmark. We used to
use
> > > http://src.chromium.org/svn/trunk/deps/avperf/ for such purposes. 
> > > 
> > > WDYT?
> > 
> > We do have a Google Cloud Storage bucket, 'chromium-wpr', that we can stick
> > large files in, and telemetry has a module to download files from there,
> > telemetry.page.cloud_storage.
> 
> Nice! how can I add stuff to the cloud bucket? Do I need to add code to
download
> those files in our benchmarks, or does telemetry download all automatically?

You can use gsutil. gsutil cp local_path gs://chromium-wpr/remote_path

Unfortunately, Telemetry doesn't download these things automatically yet. You're
welcome to add that feature :)

[shadi, 2013-07-24 22:18:26]

On 2013/07/24 19:13:17, Dave Tu wrote:
> On 2013/07/24 17:10:46, shadi wrote:
> > On 2013/07/24 17:04:22, Dave Tu wrote:
> > > On 2013/07/24 16:54:41, shadi wrote:
> > > > On 2013/07/24 16:35:03, tonyg wrote:
> > > > > On 2013/07/24 16:27:03, shadi wrote:
> > > > > > PING. I need an OWNER's LGTM.
> > > > > 
> > > > > How big are these files in total? We try to avoid checking large
binary
> > > files
> > > > > into src.
> > > > 
> > > > Good point. I think they are large enough (~130MB). 
> > > > 
> > > > Is there a telemetry_test data svn we can use? We can probably check it
in
> > to
> > > a
> > > > public repo and check it out on bots running media benchmark. We used to
> use
> > > > http://src.chromium.org/svn/trunk/deps/avperf/ for such purposes. 
> > > > 
> > > > WDYT?
> > > 
> > > We do have a Google Cloud Storage bucket, 'chromium-wpr', that we can
stick
> > > large files in, and telemetry has a module to download files from there,
> > > telemetry.page.cloud_storage.
> > 
> > Nice! how can I add stuff to the cloud bucket? Do I need to add code to
> download
> > those files in our benchmarks, or does telemetry download all automatically?
> 
> You can use gsutil. gsutil cp local_path gs://chromium-wpr/remote_path
> 
> Unfortunately, Telemetry doesn't download these things automatically yet.
You're
> welcome to add that feature :)

I will put this CL on hold now. I got few questions, so taking this offline.

[shadi, 2013-07-29 21:22:15]

Let us delete those local media files. All future media files should be on GS.

PTAL

[dtu, 2013-07-30 00:05:59]

A bunch of the files in the patch set still say M. Is that an error?

[anandc, 2013-07-30 00:12:01]

On 2013/07/30 00:05:59, Dave Tu wrote:
> A bunch of the files in the patch set still say M. Is that an error?

All the files labeled M had 0 bytes when originally committed. Perhaps that
explains the labeling?

[dtu, 2013-07-30 00:13:03]

On 2013/07/30 00:12:01, anandc wrote:
> On 2013/07/30 00:05:59, Dave Tu wrote:
> > A bunch of the files in the patch set still say M. Is that an error?
> 
> All the files labeled M had 0 bytes when originally committed. Perhaps that
> explains the labeling?

Hrm, I guess so. lgtm

[commit-bot: I haz the power, 2013-08-01 18:54:35]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/shadi@chromium.org/19784011/14001

[commit-bot: I haz the power, 2013-08-01 19:55:16]

Sorry for I got bad news for ya.
Compile failed with a clobber build on win_x64_rel.
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=win_x64_re...
Your code is likely broken or HEAD is junk. Please ensure your
code is not broken then alert the build sheriffs.
Look at the try server FAQ for more details.

[commit-bot: I haz the power, 2013-08-09 18:14:07]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/shadi@chromium.org/19784011/14001

[commit-bot: I haz the power, 2013-08-09 18:25:19]

Step "update" is always a major failure.
Look at the try server FAQ for more details.
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=win&number...

[commit-bot: I haz the power, 2013-08-12 02:00:00]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/shadi@chromium.org/19784011/14001

[commit-bot: I haz the power, 2013-08-12 05:01:24]

Change committed as 216921