[RTEMS Project] #3442: merge test_run and coverage_run into a single command in coverage script

[RTEMS trac]

#3442: merge test_run and coverage_run into a single command in coverage script
------------------------+-------------------------
 Reporter:  thelunatic  |       Owner:  (none)
     Type:  task        |      Status:  new
 Priority:  normal      |   Milestone:  Indefinite
Component:  admin       |     Version:
 Severity:  normal      |  Resolution:
 Keywords:  coverage    |  Blocked By:
 Blocking:              |
------------------------+-------------------------

Comment (by Chris Johns):

 Replying to [comment:4 thelunatic]:
 > Replying to [comment:3 Chris Johns]:
 > > Replying to [comment:2 thelunatic]:
 > > > There was a suggestion to merge these two, but no clear objectives
 were decided, I think it's better to keep them separate.
 > >
 > > I am not sure yet. It comes down to covoar and if it has to run as a
 single instance or on each test on common data.
 > I is needed to run them as a single instance? I mean, would there be any
 advantage of it?

 This is what we need to examine which we can do there.

 Covoar has evolved independently to `rtems-test` and as time has gone on
 we have settled on `rtems-test` and the standard interface for users to
 testing executables and covoar has been brought under it.

 Covoar wants to create a union of all the instructions tested across all
 test executables. Running on each executable one at a time lets the
 overall task be split and run in parallel automatically as separate jobs
 which `rtems-test` does already. If we can process each test and generate
 the needed data we can look at making the final report at the end of the
 run.

 I think we need to simplify covoar. I wonder if moving to the report
 generation would be better. We could use markdown or rest and we could
 create more complex reports via Python which is easier to do.

 It would also let covoar concentrate on what it needs to do and that is
 the low level analysis of the trace data against the executable's image.

--
Ticket URL: <http://devel.rtems.org/ticket/3442#comment:5>
RTEMS Project <http://www.rtems.org/>
RTEMS Project