Changes between Version 10 and Version 11 of GSoC/2017/RTEMSTesterImprovements


Ignore:
Timestamp:
May 24, 2017, 8:44:49 AM (9 months ago)
Author:
Tanu Hari Dixit
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GSoC/2017/RTEMSTesterImprovements

    v10 v11  
    1414'''Objectives:''' The objectives of the project are:
    1515
    16 * As of now, the configuration file format is a simple text file (with .mc extension) that serves to provide all the needed macros. This is really cryptic and needs to be converted to a suitable configuration format. I believe if I could add support for configuration files in YAML format, which will make it more readable, it would come really handy for developers to understand and tune them to their needs.
     16* As of now, the configuration file format is a simple text file (with .mc extension) that serves to provide all the needed macros. This is really cryptic and needs to be converted to a suitable configuration format. I believe if I could add support for configuration files in ~~YAML~~ INI format, which will make it more readable, it would come really handy for developers to understand and tune them to their needs.
    1717* Also, sometimes a BSP configuration needs some user-specific data to function as expected. For example, look at this[https://git.rtems.org/rtems-tools/tree/tester/rtems/testing/bsps/xilinx_zynq_zc706.mc#n59 1] macro file. Here, the path to the first stage bootloader (fsbl) has to be provided that is placed somewhere in the host machine. For this there should be proper control provided to the user as opposed to the hard coded configuration that is presently the case. This will help in the tunability of the configuration files.
    1818* Currently, the tests that are expected to fail, the results of which are indeterminate and those which timeout because they expect input from user, all are counted as failed (or timeouts in the last case). This masks the actual reasons why a certain test failed (or timed out) and eventuate into test statistics that can be easily misunderstood. Therefore, one objective of the project is to add support for test states “expected-fail”, “indeterminate” and “user-input”, so that they can be tracked separately.
     
    2222* I’ll add simulator recipes for RTEMS to work with gem5 for sparc64/usiii and arm/realview_pbx_a9_qemu BSPs.
    2323* I also plan to export the results of rtems-tester to xml format so that it can be plotted easily and used for other analysis as developers and users deem fit.
    24 Why isn't captcha allowing me to go through with this change :(
     24
     25