TWG: discussion on defining process for Continuous Testing on Foorprint/performance/low power

[hakehuang]

For better qulatiy track, below items need to be defined:

1. How to track footprint, and on which boards
   curently we have this application, maybe we need create a list of boards to track for each PR.

2. How to track performance, and on which boards
   currently, we have this application
   we need define a list of boards to track and more system level applications

3. Low power
   same with 1, 2.

[robwoolley]

Here are the slides I presented today

We used “intercept” from Build EAR to gather the compiler and linker information from another RTOS: https://github.com/rizsotto/Bear

We did some post-processing in JSON to gather the relevant pieces of information and visualized the data using Gephi: https://gephi.org/

The compiler graph was generated using the clang -ftime-tracing flag and visualized using Google Chrome Tracing. There is a useful write-up here: https://aras-p.info/blog/2019/01/16/time-trace-timeline-flame-chart-profiler-for-Clang/ this Build Analyzer may be interesting to this group as well: https://aras-p.info/blog/2019/09/28/Clang-Build-Analyzer/