Remove bzip2-encoded data file left behind when bzip2 support was removed in r34047.

Remove bzip2-encoded test data file left behind when bzip2 support was removed in r34047, as well as supporting code in testserver.py.

BUG=none
TEST=none

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=76603

[jar (doing other things), 2011-02-28 22:32:50]

LGTM.... but... be sure your trybots pass.  bzip2 compression is still used in
the metrics system to *compress* upload, but I don't think it uses this test
file.

If you want to be thorough, you could search the codebase for "bzip" and remove
any dangling references as well.  I saw one in filter.cc.

[adamk, 2011-02-28 22:36:40]

On Mon, Feb 28, 2011 at 2:32 PM, <jar@chromium.org> wrote:

> LGTM.... but... be sure your trybots pass.


Yeah, the trybot failure is troublesome. I suspect some git interaction,
retrying in an svn checkout.


> bzip2 compression is still used in
> the metrics system to *compress* upload, but I don't think it uses this
> test
> file.
>
> If you want to be thorough, you could search the codebase for "bzip" and
> remove
> any dangling references as well.  I saw one in filter.cc.


I'll take a look around and see if I can remove those once I get the trybots
to be happy.


>
>
> http://codereview.chromium.org/6591051/
>

[adamk, 2011-03-01 00:17:44]

The reference to bzip you mentioned in net/base was in a comment and doesn't
seem worth removing, but I found code in testserver.py that was only used in the
test removed in r34047.

As for the try bots, I think I just triggered an edge case in the
patch-handling: a patch consisting only of a deletion of a binary file isn't
treated well.  Adding the testserver.py changes lets the try bots process the
patch.

[adamk, 2011-03-02 18:47:01]

Jim, did you have any other comments here?  If not, I plan to land this later
today to get it off my todo list.

On 2011/03/01 00:17:44, Adam Klein wrote:
> The reference to bzip you mentioned in net/base was in a comment and doesn't
> seem worth removing, but I found code in testserver.py that was only used in
the
> test removed in r34047.
> 
> As for the try bots, I think I just triggered an edge case in the
> patch-handling: a patch consisting only of a deletion of a binary file isn't
> treated well.  Adding the testserver.py changes lets the try bots process the
> patch.

[jar (doing other things), 2011-03-02 19:51:20]

Yes, the LGTM still stands... so you can land when ready.

[commit-bot: I haz the power, 2011-03-02 19:54:35]

Try job failure for 6591051-4001 on mac:
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=mac&number...

[commit-bot: I haz the power, 2011-03-02 20:13:32]

Try job failure for 6591051-4001 on win:
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=win&number...