Collecting U-Boot Testresults: was: [ANN] U-Boot v2020.10 released
xypron.glpk at gmx.de
Fri Oct 9 08:15:48 CEST 2020
Am 9. Oktober 2020 06:33:14 MESZ schrieb Heiko Schocher <hs at denx.de>:
>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
>> we have a number of "please migrate to DM" warnings that are now 1
>> 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
>> 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
>> 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
Unfortunately I could not find the following information in :
* What is the file format and protocol to upload results? I mean a spec not example code.
Are you interested on information on any commit or only release candidates or only releases?
>Of course you can use tbot (,) for doing all the stuff automated
>(, , ), but it is enough to create the data by hand and push
>a testresult to this server (After you get access to it ...) for
>with my testscript ... 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:
>As the server code is on github , I am open for more ideas, what
>sort of data we want to collect and what we may do with the data...
> Example tbot implementation I use for the boards which are in 
> Example config for socrates board:
> tbot board config:
> config for using U-Boots test.py:
> add patches to U-Boot mainline:
> UBoot builder config (for the "pollux" lab) with enabling some extra
> Kconfig options for the U-Boot test:
> tbot generator for pushing to the database:
> Minimal "CI" (something like a cron job, but in python):
> and the config for my currently 4 boards:
> server code:
> script for pushing results to it (by hand):
> This is just an test script from me, it needs cleanup, and of course
> adaptions to work for others ...
> tbot documentation
More information about the U-Boot-Board-Maintainers