Add test binary files for Issue 15908002.

Add test binary files for Issue 15908002.
Since binary files break the try server, and Issue 15908002 would like to use
the try server, it is necessary to upload these files separately.

BUG=245318

[waffles, 2013-05-29 22:14:00]

Hi Carlos,

If you think we're going in the right direction with the other CL (we agree with
your comments thus far), we'd like to upload the binary files separately so that
we can start successfully using the try server.

Thanks!

[cpu_(ooo_6.6-7.5), 2013-05-30 00:56:31]

Adding rsleevi for pem usage

[cpu_(ooo_6.6-7.5), 2013-05-30 00:57:45]

https://codereview.chromium.org/15875020/diff/1/chrome/test/data/components/i...
File
chrome/test/data/components/ihfokbkgjpifnbbojhneepfflplebdkc/ihfokbkgjpifnbbojhneepfflplebdkc_1to2/commands.json
(right):

https://codereview.chromium.org/15875020/diff/1/chrome/test/data/components/i...
chrome/test/data/components/ihfokbkgjpifnbbojhneepfflplebdkc/ihfokbkgjpifnbbojhneepfflplebdkc_1to2/commands.json:1:
[["manifest.json",
"1cf8d0b433c09c465994e952a79ff6980c68cc7493609f0233a4634de6276e9c", "create",
"f0"], ["a_static_text_file",
"806bfdfbf05afab546b3741e84fb1ccffdf75eef8629c24c5f84add2785b7bcc", "copy",
"a_static_text_file"], ["a_changing_text_file",
"aa607adc0b3cd83e7e9f3ebd4ae84671e2b0b288c9b7fed1e0c710025719caf5", "create",
"f2"], ["a_changing_binary_file",
"dbd6da0fd6f748b7ec95f0eed6c1f6a046d161bebb04994fe1ce730e237a733d", "bsdiff",
"a_changing_binary_file", "f3"]]
could we format this so it is readable?

[waffles, 2013-05-30 01:10:48]

On 2013/05/30 00:57:45, cpu wrote:
>
https://codereview.chromium.org/15875020/diff/1/chrome/test/data/components/i...
> File
>
chrome/test/data/components/ihfokbkgjpifnbbojhneepfflplebdkc/ihfokbkgjpifnbbojhneepfflplebdkc_1to2/commands.json
> (right):
> 
>
https://codereview.chromium.org/15875020/diff/1/chrome/test/data/components/i...
>
chrome/test/data/components/ihfokbkgjpifnbbojhneepfflplebdkc/ihfokbkgjpifnbbojhneepfflplebdkc_1to2/commands.json:1:
> [["manifest.json",
> "1cf8d0b433c09c465994e952a79ff6980c68cc7493609f0233a4634de6276e9c", "create",
> "f0"], ["a_static_text_file",
> "806bfdfbf05afab546b3741e84fb1ccffdf75eef8629c24c5f84add2785b7bcc", "copy",
> "a_static_text_file"], ["a_changing_text_file",
> "aa607adc0b3cd83e7e9f3ebd4ae84671e2b0b288c9b7fed1e0c710025719caf5", "create",
> "f2"], ["a_changing_binary_file",
> "dbd6da0fd6f748b7ec95f0eed6c1f6a046d161bebb04994fe1ce730e237a733d", "bsdiff",
> "a_changing_binary_file", "f3"]]
> could we format this so it is readable?

This file is written by a machine; I could do a one-off hack the script to make
it generate a more readable file, but we don't intend to do that for production,
and I feel like there is some value in using files that are 1) regenerate-able,
2) as close as possible to production files.

The script that generates this is also responsible for signing the .crx, hashing
it, etc, so manually constructing one of these things is a bit painful. I would
prefer to leave it.

Let me know what you think.

[Ryan Sleevi, 2013-05-30 01:59:15]

Please make sure to add/update the BUG= line to point to an appropriate tracking
bug for this change.

The PEM file for the test seems fine. It's not strictly necessary to include,
other than it makes it simple to re-generate the test data w/o having to update
the extension ID (a point I'm neither here nor there on, since if you're
updating test data, flopping IDs should be fine).

The important thing is, of course, to never ever ever ever ever use that key nor
trust that extension. I haven't checked https://codereview.chromium.org/15908002
to know that this is true, but I both hope and imagine it to be fine.

[Ryan Sleevi, 2013-05-30 01:59:39]

lgtm

[cpu_(ooo_6.6-7.5), 2013-05-30 17:26:42]

lgtm

[commit-bot: I haz the power, 2013-05-30 20:13:16]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/waffles@chromium.org/15875020/1

[commit-bot: I haz the power, 2013-05-30 20:13:26]

Failed to apply patch for chrome/test/data/components/binary_input.bin:
While running patch -p1 --forward --force --no-backup-if-mismatch;
  patching file chrome/test/data/components/binary_input.bin

Patch:   N   chrome/test/data/components/binary_input.bin
Index: chrome/test/data/components/binary_input.bin
diff --git a/chrome/test/data/components/binary_input.bin
b/chrome/test/data/components/binary_input.bin
new file mode 100644
index
0000000000000000000000000000000000000000..1b22a54123115b660579697bf9ce2b9a167ecf44
--- /dev/null
+++ b/chrome/test/data/components/binary_input.bin
@@ -0,0 +1,2 @@
+UþÛ$9ÿ¥9$M
<­ß«NÚ+wØaüϳ“ç¸PŽ5*ӈŒV)«Wo31cñå%ö4å†1
+-¤…Ú/7žø’xÿ9¤ÑʾȵVZl½±=
ý*r—#ÐÓÉØO½²¾Óng¶`WH/;žÇÅõ‚·›iŒâԛæ¹°<†:»
j.ÿJ±E
³ò’J·O Z«mœÜ\%ÁêÛ¤öŸ*`¢nÉ&윶*™ùQ™–Ïj“ËöÏyð÷9Ü¡Ù֔4íͲ¶EïꚮÀ/LŒé)îq4ø‡žüNrŸÌ;'s,0LóÆv[±G²ÕËn>knÁ±ßþÚ¢0O3°¾Ób©Ø–¦DÅVÝñސnïxßÖ:­¬Á«5Mr¨`ý š»¯©»¬;Y9é6I¸ó¶žð=ÁV½®èNml‰Ê¸âÅï
[š"êåÅXwє:
\ No newline at end of file

[cpu_(ooo_6.6-7.5), 2013-05-30 21:06:30]

Not sure what happened but could it be that some files don't have the right svn
property set for binaries?

[waffles, 2013-05-30 21:28:17]

On 2013/05/30 21:06:30, cpu wrote:
> Not sure what happened but could it be that some files don't have the right
svn
> property set for binaries?

Hm, well, I hope not, I'm using git.
I'm not aware of any binary limitations on git except that it can be tricky to
merge binaries... but applying a patch from /dev/null should be trivial.

[Ryan Sleevi, 2013-05-30 21:32:14]

On 2013/05/30 21:28:17, waffles wrote:
> On 2013/05/30 21:06:30, cpu wrote:
> > Not sure what happened but could it be that some files don't have the right
> svn
> > property set for binaries?
> 
> Hm, well, I hope not, I'm using git.
> I'm not aware of any binary limitations on git except that it can be tricky to
> merge binaries... but applying a patch from /dev/null should be trivial.


You can't CQ binary files. You have to git svn dcommit directly.

[waffles, 2013-05-30 21:42:35]

On 2013/05/30 21:32:14, Ryan Sleevi wrote:
> On 2013/05/30 21:28:17, waffles wrote:
> > On 2013/05/30 21:06:30, cpu wrote:
> > > Not sure what happened but could it be that some files don't have the
right
> > svn
> > > property set for binaries?
> > 
> > Hm, well, I hope not, I'm using git.
> > I'm not aware of any binary limitations on git except that it can be tricky
to
> > merge binaries... but applying a patch from /dev/null should be trivial.
> 
> 
> You can't CQ binary files. You have to git svn dcommit directly.

cpu@, would you commit on my behalf, then, as I lack committer access?

[waffles, 2013-05-31 00:30:03]

On 2013/05/30 21:42:35, waffles wrote:
> On 2013/05/30 21:32:14, Ryan Sleevi wrote:
> > On 2013/05/30 21:28:17, waffles wrote:
> > > On 2013/05/30 21:06:30, cpu wrote:
> > > > Not sure what happened but could it be that some files don't have the
> right
> > > svn
> > > > property set for binaries?
> > > 
> > > Hm, well, I hope not, I'm using git.
> > > I'm not aware of any binary limitations on git except that it can be
tricky
> to
> > > merge binaries... but applying a patch from /dev/null should be trivial.
> > 
> > 
> > You can't CQ binary files. You have to git svn dcommit directly.
> 
> cpu@, would you commit on my behalf, then, as I lack committer access?

Actually, please wait 20 hours, Sorin and I are debating a protocol change that
would mean regenerating these binaries anyways. (Sorry about this.)

[waffles, 2013-05-31 19:41:48]

On 2013/05/31 00:30:03, waffles wrote:
> On 2013/05/30 21:42:35, waffles wrote:
> > On 2013/05/30 21:32:14, Ryan Sleevi wrote:
> > > On 2013/05/30 21:28:17, waffles wrote:
> > > > On 2013/05/30 21:06:30, cpu wrote:
> > > > > Not sure what happened but could it be that some files don't have the
> > right
> > > > svn
> > > > > property set for binaries?
> > > > 
> > > > Hm, well, I hope not, I'm using git.
> > > > I'm not aware of any binary limitations on git except that it can be
> tricky
> > to
> > > > merge binaries... but applying a patch from /dev/null should be trivial.
> > > 
> > > 
> > > You can't CQ binary files. You have to git svn dcommit directly.
> > 
> > cpu@, would you commit on my behalf, then, as I lack committer access?
> 
> Actually, please wait 20 hours, Sorin and I are debating a protocol change
that
> would mean regenerating these binaries anyways. (Sorry about this.)

Thanks for waiting; new binaries uploaded.

[cpu_(ooo_6.6-7.5), 2013-06-03 19:14:37]

Ryan, can you dcommit his for him?

I have windows and the git to svn is busted.

[sorin, 2013-06-04 16:56:26]

bump.

Sorry for the nag, we appreciate any help submitting this, it is blocking a
lot of work since we can't try the real code until these binaries are in.

Thank you!


On Mon, Jun 3, 2013 at 12:14 PM, <cpu@chromium.org> wrote:

> Ryan, can you dcommit his for him?
>
> I have windows and the git to svn is busted.
>
>
https://codereview.chromium.**org/15875020/<https://codereview.chromium.org/1...
>

[Ryan Sleevi, 2013-06-04 18:28:34]

I am unable to land this.

The .tar.gz2 file contains just empty files (for both a/ and b/), and the raw
patchset is unable to apply because of the binary files.

On 2013/06/04 16:56:26, sorin wrote:
> bump.
> 
> Sorry for the nag, we appreciate any help submitting this, it is blocking a
> lot of work since we can't try the real code until these binaries are in.
> 
> Thank you!
> 
> 
> On Mon, Jun 3, 2013 at 12:14 PM, <mailto:cpu@chromium.org> wrote:
> 
> > Ryan, can you dcommit his for him?
> >
> > I have windows and the git to svn is busted.
> >
> >
>
https://codereview.chromium.**org/15875020/%3Chttps://codereview.chromium.org...>
> >

[Ryan Sleevi, 2013-06-04 21:45:04]

https://codereview.chromium.org/16380002/