Hi All,

Today’s meeting agenda:

1.       Demo of GUI result display and  follow up. (Anas 20 minutes)

2.       LTS release items discussion.(30 mintues)

Proposal from Anas in TSC team:

https://docs.google.com/presentation/d/1ucJeyadvA9JSu0i6J3R7xcqbYkHKvZp0Nusaa9s3jU4/edit?usp=sharing

Test plan

https://github.com/zephyrproject-rtos/zephyr/discussions/32749

3.       round table discussion. (All)

Regards,

Hake

Hi All,

This is the discussion link on test plan contents, please share your ideas there.

https://github.com/zephyrproject-rtos/zephyr/discussions/32749 thanks.

Regards,

Hake

Hi,

Sorry for the late notice. I won’t be able to join today.

Anas

Hi All.

Today’s meeting agenda:

1.       Demo of GUI result display. (Anas 20 minutes)

2.       nomenclature of test suites and test cases discussion. (Maciej 20 minutes)

any detailed examples in on discussion?

https://github.com/zephyrproject-rtos/zephyr/discussions/31090  

3.       round table discussion. (All)

Regards,

Hake

Hi All.

Today’s meeting agenda:

1.       Demo of GUI result display. (Anas 20 minutes)

2.       nomenclature of test suites and test cases discussion. (Maciej 20 minutes)

any detailed examples in on discussion?

https://github.com/zephyrproject-rtos/zephyr/discussions/31090  

3.       round table discussion. (All)

Regards,

Hake

Hi All,

1.     Zephyr v2.5.0 tagged.

1.     Release document added for v2.5.0

2.     nomenclature of test suites and test cases discussion. (Maciej 30 minutes)

any detailed examples in on discussion?

https://github.com/zephyrproject-rtos/zephyr/discussions/31090  

3.     round table discussion. (All)

Regards,

Hake

Hi All,

This weekly meeting agenda:

1.      Zephyr v2.5.0 tagged.

1.      Call for review the release document at: https://github.com/zephyrproject-rtos/test_results/pull/154

2.      nomenclature of test suites and test cases discussion. (Maciej 15 minutes)

any detailed examples in on discussion?

https://github.com/zephyrproject-rtos/zephyr/discussions/31090  

3.      round table discussion. (All)

Regards,

Hake

Hi All,

This weekly meeting agenda:

1.      V2.5.0 test release document review. (Hake/ All 15 minutes)

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

Add link to the code base of footprint test(SHA) -> done

Add footprint steps in to appendix-> done

Please upload v2.5.0-rc3 board testing report.

2.      nomenclature of test suites and test cases discussion, a short sync. (Maciej 15 minutes)

https://github.com/zephyrproject-rtos/zephyr/discussions/31090   

Maceij will take AI and create PR for this -> follow up

3.      call for proposal on test result visualization solution.

https://github.com/zephyrproject-rtos/test_results/discussions/190

4.      Round table discussion. (30 minutes)

https://github.com/zephyrproject-rtos/zephyr/pull/29427 please help to review

https://github.com/zephyrproject-rtos/zephyr/pull/29427/files we need more reviewer/maintainer for twister scripts, let continue thinking about how to make it more maintainable.

Regards,

Hake

Hi All,

This weekly meeting agenda:

1.     V2.5.0 test release document review. (Hake/ All 15 mintues)

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

pending items: added platfrom testing status?

2.     nomenclature of test suites and test cases discussion, a short sync. (Maciej 15 mintues)

https://github.com/zephyrproject-rtos/zephyr/discussions/31090   

3.     call for proposal on test result visualiztion solution

https://github.com/zephyrproject-rtos/test_results/discussions/190

4.     Round table discussion. (30 mintues)

Regards,

Hake

Hi All,

I create a discussion here for test result visualization https://github.com/zephyrproject-rtos/test_results/discussions/190

Please provide you ideas and proposal here, Thanks.

Regards,

Hake

Hi All,

This weekly meeting agenda:

1.     V2.5-RC1 tagged, let’s switch to this weekly testing.

1. Discussion on the nomenclature of test suites and test cases. (15 minutes / Maciej/ All)

https://github.com/zephyrproject-rtos/zephyr/discussions/31090  

Note: need consider none-ztest based test cases naming.

Al: we need to vote whether to change the naming as Maciej proposed.

3.     Bug analysis on https://testing.zephyrproject.org/daily_tests/zephyr-v2.4.0-3224-gc77ae15c9967/report/index.html  (10 minutes)

NXP:

l  can driver testing has one issue. (in analysis)

l  counter issue fixed.

l  Some board upstable issues found in kernel / libraries-libc testing retesting is ongoing(FRDM_KW41z, mimxrt1060_evk).

4.     Test result data visualization discussion. (20 minutes/ All)

5.     Release document comments https://github.com/zephyrproject-rtos/test_results/pull/154 (reminds)

6.     Round table discussion. (15 minutes / All)

NXP: any testing data on I2S?

Regards,

Hake

Hi All,

This is this weekly meeting agenda:

1.     Release document is RST format reviewing follow up. Any comments?

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

2.     V2.5.0 is closing, we need prepare the testing plans. (40 minutes)

a)      Testing scope. (boards, plans, doeuments, etc)

b)      Related links:

https://github.com/zephyrproject-rtos/zephyr/projects/9

https://github.com/zephyrproject-rtos/zephyr/issues?q=is%3Aopen+is%3Aissue+milestone%3Av2.5.0

3.     Round table discussion. (20 mintues)

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

b)      H5py format trail. Some questions:

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?

c)      twister.xml and twister_report.xml full path differences. https://zephyrproject.slack.com/archives/CG9H1L6LE/p1610723284017000

Regards,

Hake

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