On 12/11/20 9:49, Jan Lübbe wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> Hi Santi,
>
> On Wed, 2020-11-11 at 18:05 +0000, Santiago.Esteban via info via groups.io wrote:
>> Hi KernelCI,
>>
>> A few months back I contacted you about adding a new lab to KernelCI
>> infrastructure. It took us longer than I wished, but now we finally
>> have been able to connect our farm to an internal KernelCI deployment
>> (using docker).
>>
>> As I explained before, our farm holds 4 boards with different SoCs
>> from Microchip (and Atmel): Sam9x60ek, Sama5d2_xplained,
>> Sama5d3_xplained and Sama5d4_xplained. All of then with mainline
>> support.
>>
>> Our setup, does not uses Lava and it relies on Labgrid to perform the
>> tests. We use "kci_data" tool to publish test results on KernelCI.
> That's very interesting. :) Do you have published the interface code
> somewhere? I've been trying to find some time to do that myself, but it
> seems you've beaten me to it. ;)
>
> Regards
> Jan

Hi Jan,

No, I haven't publish it, till now. I've never though it would be useful 
to anybody but me  ;)

I have a python script that is tailored (too much) to our systems. It 
performs some actions that depend on our infrastructure and how I've 
implemented the labgrid tests (for example, I grab the results from a 
pytest  json report). At the end, it creates a "tmeta_<board>.json" file 
(equivalent to the "bmeta.json") that is later published with "kci_data" 
tool.

It could be used as an inspiration to make a more generic 
"kci_labgrid_test" tool if there are interest, but, all kernelci 
important stuff, still needs to be validated ;)

I have attached it to this email the script and (more important) an 
example of the output it produces.

BR,

Santi

>
>> We would like to work with you to be able to publish these results.
>> Will it be possible to get a token for the staging database? I'm sure
>> that there are things that need to be polished on our json files.
>