Integrate dynamic charts into autotest frontend.

Integrate dynamic charts into autotest frontend.

BUG=chromium-os:14044
TEST=http://truty.i/croschart/server/x86-mario-r12/MARIO_MP/0.12.306.0/0.12.389.0/platform_BootPerfServer/seconds_kernel_to_startup/1280/1024/

Committed: http://chrome-svn/viewvc/chromeos?view=rev&revision=ddd44b2

[truty, 2011-04-13 21:52:46]

Eric, would you please review?

[ericli, 2011-04-13 22:07:47]

http://codereview.chromium.org/6821082/diff/6001/frontend/croschart/gviz_pyth...
File frontend/croschart/gviz_python/README (right):

http://codereview.chromium.org/6821082/diff/6001/frontend/croschart/gviz_pyth...
frontend/croschart/gviz_python/README:16: python ./setup.py install
do I need to do this manually if I am deploying a new frontend setver?

If so, can I add this into utils/build_externals.py?

What if I put this package under site-packages?

http://codereview.chromium.org/6821082/diff/6001/frontend/croschart/models.py
File frontend/croschart/models.py (right):

http://codereview.chromium.org/6821082/diff/6001/frontend/croschart/models.py...
frontend/croschart/models.py:18: new_build = '%s...%s' % (m.group(1),
m.group(3))
I think we agreed to s/.../- ?

http://codereview.chromium.org/6821082/diff/6001/frontend/croschart/models.py...
frontend/croschart/models.py:26: build_pattern = re.compile(
promote this to a CONST str, and you can save one arg in AbbreviateBuild()

http://codereview.chromium.org/6821082/diff/6001/frontend/croschart/views.py
File frontend/croschart/views.py (right):

http://codereview.chromium.org/6821082/diff/6001/frontend/croschart/views.py#...
frontend/croschart/views.py:56: ('platform_BootPerfServer',
'seconds_kernel_to_startup'),
I would refactor it out to some config file, so 
1. I dont need to touch this file just because people are adding a new perfkey
in their tests.
2. I should not deploy and restart the server because this reason either.

http://codereview.chromium.org/6821082/diff/6001/frontend/croschart/views.py#...
frontend/croschart/views.py:109: boards = 'x86-mario-r12'
sounds like boards = ['x86-mario-r12'] is more apprapriate,
otherwise, I would use board = 'x86-mario-r12'

More thought, is there any chance not hard code these values here?

[truty, 2011-04-14 19:01:51]

This is working very well.  Here's another test url:
http://truty.i/croschart/server/charts/x86-alex-r11/ALEX/320/240/

http://codereview.chromium.org/6821082/diff/6001/frontend/croschart/gviz_pyth...
File frontend/croschart/gviz_python/README (right):

http://codereview.chromium.org/6821082/diff/6001/frontend/croschart/gviz_pyth...
frontend/croschart/gviz_python/README:16: python ./setup.py install
On 2011/04/13 22:07:47, ericli wrote:
> do I need to do this manually if I am deploying a new frontend setver?
> 
> If so, can I add this into utils/build_externals.py?
> 
> What if I put this package under site-packages?

Have added code to support build_externals install of gviz_api so these actual
files are now removed.

http://codereview.chromium.org/6821082/diff/6001/frontend/croschart/models.py
File frontend/croschart/models.py (right):

http://codereview.chromium.org/6821082/diff/6001/frontend/croschart/models.py...
frontend/croschart/models.py:18: new_build = '%s...%s' % (m.group(1),
m.group(3))
On 2011/04/13 22:07:47, ericli wrote:
> I think we agreed to s/.../- ?

Done.

http://codereview.chromium.org/6821082/diff/6001/frontend/croschart/models.py...
frontend/croschart/models.py:26: build_pattern = re.compile(
On 2011/04/13 22:07:47, ericli wrote:
> promote this to a CONST str, and you can save one arg in AbbreviateBuild()

Done.

http://codereview.chromium.org/6821082/diff/6001/frontend/croschart/views.py
File frontend/croschart/views.py (right):

http://codereview.chromium.org/6821082/diff/6001/frontend/croschart/views.py#...
frontend/croschart/views.py:56: ('platform_BootPerfServer',
'seconds_kernel_to_startup'),
On 2011/04/13 22:07:47, ericli wrote:
> I would refactor it out to some config file, so 
> 1. I dont need to touch this file just because people are adding a new perfkey
> in their tests.
> 2. I should not deploy and restart the server because this reason either.

I actually spent a fair amount of time trying to get it spelled out in a django
template but django templates do not allow the static declaration of a 2d array
of tuples.  I finally was poking around the django template source code to
verify that.  So, this approach with json is the method that works.

http://codereview.chromium.org/6821082/diff/6001/frontend/croschart/views.py#...
frontend/croschart/views.py:109: boards = 'x86-mario-r12'
On 2011/04/13 22:07:47, ericli wrote:
> sounds like boards = ['x86-mario-r12'] is more apprapriate,
> otherwise, I would use board = 'x86-mario-r12'
> 
> More thought, is there any chance not hard code these values here?

Removed.  This was for demos.

[ericli, 2011-04-14 21:40:47]

LGTM