Don't run the testing script on debian

Don't run the testing script on debian

We currently can't execute it since the checked in binaries are compiled on precise machines.

I have filed http://dartbug.com/18742 to track us updating it

R=sgjesse@google.com

Committed: https://code.google.com/p/dart/source/detail?r=35963

[Søren Gjesse, 2014-05-09 08:42:06]

lgtm

https://codereview.chromium.org/272003003/diff/20001/tools/bots/linux_distrib...
File tools/bots/linux_distribution_support.py (right):

https://codereview.chromium.org/272003003/diff/20001/tools/bots/linux_distrib...
tools/bots/linux_distribution_support.py:155: if (build_info.builder_tag ==
'ubuntu_precise'):
Could a temporary hack be to copy the newly built dart executable over the
checked in binary? Maybe just waiting until we can check in a wheezy binary will
be OK.

[ricow1, 2014-05-09 09:08:46]

https://codereview.chromium.org/272003003/diff/20001/tools/bots/linux_distrib...
File tools/bots/linux_distribution_support.py (right):

https://codereview.chromium.org/272003003/diff/20001/tools/bots/linux_distrib...
tools/bots/linux_distribution_support.py:155: if (build_info.builder_tag ==
'ubuntu_precise'):
On 2014/05/09 08:42:06, Søren Gjesse wrote:
> Could a temporary hack be to copy the newly built dart executable over the
> checked in binary? Maybe just waiting until we can check in a wheezy binary
will
> be OK.

We should just put in the wheezy binary, how about doing it when we have 1.4
ready (we could even do it now, just take it from the current dev channel build,
I don't think it makes a big differece)

[ricow1, 2014-05-09 09:09:10]

Committed patchset #2 manually as r35963 (presubmit successful).