chromium-status: tests: handle -vv and -vvv flags

chromium-status: tests: handle -vv and -vvv flags

People like to pack flags like -vv rather than doing -v -v.
Support that too.

BUG=chromium:314501
TEST=`./tests/main_test.py -vv` uses more verbose logging

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

[cmp, 2013-11-04 22:27:48]

https://codereview.chromium.org/47623004/diff/1/tests/main_test.py
File tests/main_test.py (right):

https://codereview.chromium.org/47623004/diff/1/tests/main_test.py#newcode364
tests/main_test.py:364: (sys.argv.count('-vvv') * 3))])
Does optparse natively support this?  If it does, can we use that directly
instead?

[vapier, 2013-11-04 22:30:23]

https://codereview.chromium.org/47623004/diff/1/tests/main_test.py
File tests/main_test.py (right):

https://codereview.chromium.org/47623004/diff/1/tests/main_test.py#newcode364
tests/main_test.py:364: (sys.argv.count('-vvv') * 3))])
shouldn't be hard to rewrite with standard optparse.  seemed like this code
wanted to stay hacky so i extended it as is :).

[vapier, 2013-11-04 23:52:48]

this version handles -v -vv -vvvvvv sanely.

it will barf if you do something like -vvf.  -vv -f will work.  argparse has
support for parse_known_args(), but optparse doesn't.  it'd take a bit more
logic to make that work w/optparse (since i don't think we want to start relying
on argparse just yet).

i think this code is an acceptable middle ground.

[cmp, 2013-11-10 16:08:22]

lgtm

[commit-bot: I haz the power, 2013-11-10 16:08:53]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/vapier@chromium.org/47623004/70001

[commit-bot: I haz the power, 2013-11-10 16:09:10]

Change committed as 234178