Change configs/try.py to get the list of config files to use from args.

Change configs/try.py to get the list of config files to use from args.

For example, after uploading this CL, I just ran:

./try.py mac.bisect.blink_perf.cfg linux.perf_test.tab_switching.cfg. I expect it should only start two try jobs.

If you run ./try.py (with no arguments), it prints usage help and a "too few arguments" message.

BUG=415890
Committed: https://crrev.com/aac2930feadd3552151930baa0df2e77782c6f58
Cr-Commit-Position: refs/heads/master@{#302414}

[qyearsley, 2014-10-28 19:42:35]

qyearsley@chromium.org changed reviewers:
+ prasadv@chromium.org, robertocn@chromium.org, sergiyb@chromium.org

[qyearsley, 2014-10-28 19:44:16]

On 2014/10/28 19:43:26, qyearsley wrote:

Note, currently configs/try.py is still broken -- I never meant to start try
jobs for win or android just now, but jobs got started. I suspect something is
wrong with the invocation of "git try".

[Sergiy Byelozyorov, 2014-10-30 11:49:13]

lgtm with comments... but please make sure this works before commiting

https://codereview.chromium.org/687733003/diff/20001/tools/auto_bisect/config...
File tools/auto_bisect/configs/try.py (right):

https://codereview.chromium.org/687733003/diff/20001/tools/auto_bisect/config...
tools/auto_bisect/configs/try.py:117: try_command = ['git', 'try', '-S',
SVN_URL, '-n', job_name]
The previous option name was more readable. Why change? I would also encourage
to change -n into --name.

[qyearsley, 2014-11-02 16:33:00]

On 2014/10/30 11:49:13, Sergiy Byelozyorov wrote:
> lgtm with comments... but please make sure this works before commiting
> 
>
https://codereview.chromium.org/687733003/diff/20001/tools/auto_bisect/config...
> File tools/auto_bisect/configs/try.py (right):
> 
>
https://codereview.chromium.org/687733003/diff/20001/tools/auto_bisect/config...
> tools/auto_bisect/configs/try.py:117: try_command = ['git', 'try', '-S',
> SVN_URL, '-n', job_name]
> The previous option name was more readable. Why change? I would also encourage
> to change -n into --name.

The only reason I changed it before is because I was experimenting with whether
that was a factor in causing the git try command to trigger jobs on all of the
bots at once...

Now, I just realized that one of the builder names was wrong -- it was
"linux_perf_bot". And if the builder name isn't found, then git try starts jobs
on all try bots.

[qyearsley, 2014-11-03 05:30:39]

On 2014/11/02 16:33:00, qyearsley wrote:
> On 2014/10/30 11:49:13, Sergiy Byelozyorov wrote:
> > lgtm with comments... but please make sure this works before commiting
> > 
> >
>
https://codereview.chromium.org/687733003/diff/20001/tools/auto_bisect/config...
> > File tools/auto_bisect/configs/try.py (right):
> > 
> >
>
https://codereview.chromium.org/687733003/diff/20001/tools/auto_bisect/config...
> > tools/auto_bisect/configs/try.py:117: try_command = ['git', 'try', '-S',
> > SVN_URL, '-n', job_name]
> > The previous option name was more readable. Why change? I would also
encourage
> > to change -n into --name.
> 
> The only reason I changed it before is because I was experimenting with
whether
> that was a factor in causing the git try command to trigger jobs on all of the
> bots at once...
> 
> Now, I just realized that one of the builder names was wrong -- it was
> "linux_perf_bot". And if the builder name isn't found, then git try starts
jobs
> on all try bots.

I believe that the failures are not due to changes in this CL, so I'd like to
try to commit this.

[qyearsley, 2014-11-03 05:30:47]

The CQ bit was checked by qyearsley@chromium.org

[commit-bot: I haz the power, 2014-11-03 05:31:43]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/687733003/140001

[commit-bot: I haz the power, 2014-11-03 06:12:01]

Committed patchset #8 (id:140001)

[commit-bot: I haz the power, 2014-11-03 06:12:52]

Patchset 8 (id:??) landed as
https://crrev.com/aac2930feadd3552151930baa0df2e77782c6f58
Cr-Commit-Position: refs/heads/master@{#302414}