Missing XML-RPC to get list of test names

I added a MP marked as still in progress. I'm trying to get tests working locally for lava-dashboard, but am not able to.

I think you are on the right track here. However, rather than listing all tests, we could probably make this function take some params. For example, if we know:

 device-type (panda, vexpress, origen, etc)
 build-type (android / ubuntu)

You could actually filter down the list of tests more appropriately. Maybe make those two parameters above optional or something?

Hello Andy,

thanks for the input!

On Wed, Sep 19, 2012 at 12:02 AM, Andy Doan <email address hidden> wrote:
> I think you are on the right track here. However, rather than listing
> all tests, we could probably make this function take some params. For
> example, if we know:
>
> device-type (panda, vexpress, origen, etc)
> build-type (android / ubuntu)
>
> You could actually filter down the list of tests more appropriately.

Something like that would be awesome for us, but I guess I need a
little bit of guidance here then.
Looking at the Test model in 'lava_dashboard/dashboard_app/models.py',
the model is pretty simple, there is no information about device or
build.

The only reference about hardware I found is in TestRun model, that
refers to HardwareDevice, but the latter is not really helpful.

> Maybe make those two parameters above optional or something?

I added them, although not used ATM, and pushed into the branch.
Thanks for all the help!

--
Milo Casagrande
Infrastructure Engineer
Linaro.org <www.linaro.org> │ Open source software for ARM SoCs

+Michael who's a DB query wizard.

On 09/19/2012 03:17 AM, Milo Casagrande wrote:
> Hello Andy,
>
> thanks for the input!
>
> On Wed, Sep 19, 2012 at 12:02 AM, Andy Doan <email address hidden> wrote:
>> I think you are on the right track here. However, rather than listing
>> all tests, we could probably make this function take some params. For
>> example, if we know:
>>
>> device-type (panda, vexpress, origen, etc)
>> build-type (android / ubuntu)
>>
>> You could actually filter down the list of tests more appropriately.
>
> Something like that would be awesome for us, but I guess I need a
> little bit of guidance here then.
> Looking at the Test model in 'lava_dashboard/dashboard_app/models.py',
> the model is pretty simple, there is no information about device or
> build.
>
> The only reference about hardware I found is in TestRun model, that
> refers to HardwareDevice, but the latter is not really helpful.
>

Michael - do you think there's a way to query for this semi-efficiently.
ie somehow doing a "SELECT test where device_type=='panda'"

Andy Doan <email address hidden> writes:

> +Michael who's a DB query wizard.
>
> On 09/19/2012 03:17 AM, Milo Casagrande wrote:
>> Hello Andy,
>>
>> thanks for the input!
>>
>> On Wed, Sep 19, 2012 at 12:02 AM, Andy Doan <email address hidden> wrote:
>>> I think you are on the right track here. However, rather than listing
>>> all tests, we could probably make this function take some params. For
>>> example, if we know:
>>>
>>> device-type (panda, vexpress, origen, etc)
>>> build-type (android / ubuntu)

FWIW, I don't see a particularly clean or reliable way to tell tests
that have run on android from tests that have run on ubuntu currently...

>>> You could actually filter down the list of tests more appropriately.
>>
>> Something like that would be awesome for us, but I guess I need a
>> little bit of guidance here then.
>> Looking at the Test model in 'lava_dashboard/dashboard_app/models.py',
>> the model is pretty simple, there is no information about device or
>> build.
>>
>> The only reference about hardware I found is in TestRun model, that
>> refers to HardwareDevice, but the latter is not really helpful.
>>
>
> Michael - do you think there's a way to query for this semi-efficiently.
> ie somehow doing a "SELECT test where device_type=='panda'"

models.Test.objects.filter(
    test_runs__attributes__name='target.device_type',
    test_runs__attributes__value='panda').distinct()

returns all the tests that have evey been run on panda and seems to be
reasonably efficient (0.1s or so). Is that what you meant?

Cheers,
mwh

On 09/19/2012 08:58 PM, Michael Hudson-Doyle wrote:
> models.Test.objects.filter(
> test_runs__attributes__name='target.device_type',
> test_runs__attributes__value='panda').distinct()
>
> returns all the tests that have evey been run on panda and seems to be
> reasonably efficient (0.1s or so). Is that what you meant?

Yeah, something like that helps.

Too bad we can filter android/ubuntu.

Hello everyone!

Thanks for the suggestion! I updated the branch with that change.
Am still not able to make tests run locally, so for the moment the MP does not containt tests.