[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linaro-validation
Subject:    [Linaro-validation] Easy reports from LAVA
From:       paul.larson () linaro ! org (Paul Larson)
Date:       2012-03-24 4:35:13
Message-ID: CAD69n1B-gXe0OimDUYgvGKm0wuiAOAw2RxRxx8zBnpwbsKJAyQ () mail ! gmail ! com
[Download RAW message or body]

On Fri, Mar 23, 2012 at 10:48 PM, Andy Doan <andy.doan at linaro.org> wrote:

> On 3/23/12 8:02 PM, Amit Kucheria wrote:
> 
> > Wow, this looks quite involved. Learning Django (and python as a
> > pre-req) is steep. I guess I was hoping for something quick and dirty
> > akin to gnuplot munging some data into a graph.
> > 
> > Hongbo, how is your python?:)
> > 
> > I guess we'll have to see if we can steal some existing code and beat
> > it enough to get something useful for us.
> > 
> 
> You can look at the dashboard's javascript "report" interface:
> 
> 
> http://bazaar.launchpad.net/~**linaro-validation/lava-**
> dashboard/trunk/files/head:/**examples/reports/<http://bazaar.launchpad.net/%7Elinaro-validation/lava-dashboard/trunk/files/head:/examples/reports/>
>  
This really isn't recommended. It's not what I would call easy - as it
requires rooting around in the tables created by the model with sql.  The
sql you write will have to be written for postgres at least, but if you
test using sqlite locally, you may have to adapt it to both.

I just don't know if that's enough for your needs or not.
> 
> I was no Django or Python expert and found copying the existing code easy
> enough to get started.
> 
Agree, the python/django aren't that bad really.  The trickier bits (for me
at least) always seem to be the css and javascript, which are going to be
largely unavoidable if you want to do anything visual.

Thanks,
Paul Larson
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linaro.org/pipermail/linaro-validation/attachments/20120323/7926a853/attachment.html>



[prev in list] [next in list] [prev in thread] [next in thread]