Hi Maciej,

I do some work on your proposed h5py format file, here is my trial:

https://github.com/hakehuang/test_results/commit/84834483181f2e66e47d8707e2e985fc8f108fd2

my observations are:

1.     h5py is initially to store large numpy data sets, so it is friendly to numbers, but to xml result format I only use a variable string to store all the xml, as

I did not see an ready schema to convert all the result xml content to h5 attribute, tough. But in this way the h5py table function is not supported, as the variable is only comments. Looks like we need at least define a dataset which represents the trend.

2.     We can merge all the report in to several result h5 files named by the version number or further merge them to one file, is this what your proposed?

Regards,

Hake

Hi All,

This is this weekly agenda:

1.     Update the version SHA to 12 digitals merged(https://github.com/zephyrproject-rtos/zephyr/pull/31140)

Note: Last weekly result can not merged, due to this check.

2.     Release document is RST format reviewing.(All, 15 minutes)

https://github.com/zephyrproject-rtos/test_results/pull/154

3.     Round table discussion. (40 mintues)

a)      Pytest has allure plugin, would this possible to merge it to twister?

b)      …

Regards,

Hake

update PR created.

https://github.com/zephyrproject-rtos/zephyr/pull/31140 . @Anas Nashif please review. Thanks in advance.

Regards,

Hake

I find this is because

b9c953c12636a8d8f3d22b10e23218a50a695030

twister: add 12 hexadecimal digits to version

With the earlier version of Git, git describe command will

use the default 7 hexadecimal digits as the abbreviated

object name. But currently the Linux kernel project needs

11 to 12 hexdigits to stay unique.So it's necessary to add

--abbrev=12 to ensure twister always generate the same tags.

In https://testing.zephyrproject.org/daily_tests/versions.json,

all tags have 10 hexadecimal digits.

Signed-off-by: Jingru Wang <jingru@...>

Regards,

hake

Hi All,

Does anyone meet this issue like https://github.com/zephyrproject-rtos/test_results/pull/179?

I find the problem is the version in xml file is zephyr-v2.4.0-2748-gfbb0327d3e29, but the json file is zephyr-v2.4.0-2748-gfbb0327d3e.

Regards,

Hake

Hi All,

1.     Bug scrum meeting for last weekly testing. (hake/all 20 minutes).

a)      Call for board test result on last weekly.

                 i.          https://testing.zephyrproject.org/daily_tests/zephyr-v2.4.0-2126-g7516d5846d/report/index.html

2.     Last weekly action items updates (All, 30 minutes)

a)      Add GHAction for checking test result.

                 i.          https://github.com/PerMac/test_results/pull/2

b)      Release document pr

                 i.          https://github.com/zephyrproject-rtos/test_results/pull/154

                ii.           

3.     Round table discussion. (all 10 minutes)

This is the last weekly meeting of 2020. Thanks all for your participant in TWG.

Best wishes to all TWG members for 2021, Happy New Year and Merry Christmas.

Regards,

Hake

Hi All Zephyer TWG members,

As the winter is coming, would this be more approriate to cancel the last two weekly on 2020/12/21, 2020/12/28, 2021/1/4, so next weekly meeting (12/14)will be our last weekly meeting of this year(2020), and we will start weekly meeting next year on 2021/1/11, any comments? If not, I will inform Brett to cnacel the meetings. Thanks.

Regards,

Hake

Hi All,

1.     Bug scrumb for last weekly testing. (hake/all 20 minutes)

2.    The new format of Doxygen tags for a test case. (Enjia Mai (Intel) 20 minutes)

3.     Round table discussion. (all 20 minutes)

Regards,

Hake

Hi All,

This is this weekly meeting agenda.

1.     Weekly testing status update(All, 20 minuts).

a)      Do we need plan a regular bug scrum meeting?

2.     Round table disscussion. (all, 40 mintues)

Regards,

Hake