Collecting U-Boot Testresults: was: [ANN] U-Boot v2020.10 released

[Heiko Schocher]

Hello Heinrich,

Am 09.10.2020 um 08:15 schrieb Heinrich Schuchardt:
> Am 9. Oktober 2020 06:33:14 MESZ schrieb Heiko Schocher <hs at denx.de>:
>> Hi all,
>>
>> Am 05.10.2020 um 17:17 schrieb Tom Rini:
>>> Hey all,
>>>
>>> It is release day and here is the v2020.10 release.  With this
>> release
>>> we have a number of "please migrate to DM" warnings that are now 1
>> year
>>> past their warning date, and well past 1 year of those warnings being
>>> printed.  It's getting up there on my TODO list to see if removing
>>> features or boards in these cases is easier.
>>>
>>> In terms of a changelog,
>>> git log --merges v2020.10-rc5..v2020.10
>>> or
>>> git log --merges v2020.07..v2020.10
>>>
>>> The merge window is once again open and I plan to tag -rc1 on Monday,
>>> October 26th, bi-weekly -rcs thereafter and final release on January
>>> 11th, 2021.
>>>
>>> I am merging the next branch to master shortly and will send a
>> separate
>>> email when that is done.
>>
>> I want to use the chance after a new release is out, to ask if
>> people have interests in sending U-Boot Testresults to
>>
>> [1] http://xeidos.ddns.net/ubtestresults/home
>>
> 
> Unfortunately I could not find the following information in [5]:
> 
> * What is the file format and protocol to upload results? I mean a spec not example code.

may [6] or in special:
https://github.com/EmbLux-Kft/uboot_results/blob/master/src/client.py#L88

helps you here more?

And you are correct, I should write a documentation...

> Are you interested on information on any commit or only release candidates or only releases?

Currently I test on a daily basis, but release candidates or only releases
are also good!

bye,
Heiko
> 
> Best regards
> 
> Heinrich
> 
> 
>> Of course you can use tbot ([2],[7]) for doing all the stuff automated
>> ([2], [3], [4]), but it is enough to create the data by hand and push
>> a testresult to this server (After you get access to it ...) for
>> example
>> with my testscript [6]... but I recommend to use tbot, as you also
>> can use tbot for your daily work.
>>
>> If enough data is collected for a board, you can get a graphic which
>> shows the progress of image size for your board, like:
>>
>> http://xeidos.ddns.net/ubtestresults/stats/wandboard_defconfig/90
>>
>> As the server code is on github [5], I am open for more ideas, what
>> sort of data we want to collect and what we may do with the data...
>>
>> Thanks!
>>
>> bye,
>> Heiko
>>
>> [2] Example tbot implementation I use for the boards which are in [1]
>>      https://github.com/EmbLux-Kft/tbot-tbot2go
>>
>>      Example config for socrates board:
>>
>>      tbot board config:
>> https://github.com/EmbLux-Kft/tbot-tbot2go/blob/devel/boards/socrates.py#L21
>>
>>      config for using U-Boots test.py:
>> https://github.com/EmbLux-Kft/tbot-tbot2go/blob/devel/boards/socrates.py#L27
>>
>>      add patches to U-Boot mainline:
>> https://github.com/EmbLux-Kft/tbot-tbot2go/blob/devel/boards/socrates.py#L39
>>
>>    UBoot builder config (for the "pollux" lab) with enabling some extra
>>      Kconfig options for the U-Boot test:
>> https://github.com/EmbLux-Kft/tbot-tbot2go/blob/devel/boards/pollux.py#L129
>>
>> [3] tbot generator for pushing to the database:
>> https://github.com/EmbLux-Kft/tbot-tbot2go/blob/devel/push-testresult.py
>>
>> [4] Minimal "CI" (something like a cron job, but in python):
>>     https://github.com/EmbLux-Kft/tbot-tbot2go/blob/devel/minimal-ci.py
>>
>>      and the config for my currently 4 boards:
>>   https://github.com/EmbLux-Kft/tbot-tbot2go/blob/devel/minimal-ci.json
>>
>> [5] server code:
>>      https://github.com/EmbLux-Kft/uboot_results
>>
>> [6] script for pushing results to it (by hand):
>>   https://github.com/EmbLux-Kft/uboot_results/blob/master/src/client.py
>>
>>    This is just an test script from me, it needs cleanup, and of course
>>      adaptions to work for others ...
>>
>> [7] tbot documentation
>>      http://tbot.tools/
> 

-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-52   Fax: +49-8142-66989-80   Email: hs at denx.de