#3458 closed defect (fixed)

rtems-test should not use the env PATH to find covoar

Reported by: Chris Johns Owned by: Chris Johns <chrisj@…>
Priority: normal Milestone: 5.1
Component: tool Version: 5
Severity: normal Keywords: coverage rtems-test
Cc: Blocked By:
Blocking:

Description

The rtems-test command should know where covoar is when invoking it. It cannot use the environment's path. The path can contain invalid or outdated versions with subtle issues that could be hard to find.

There should be no need to run install to use and test rtems-test with coverage.

The rtems-test python code for running the tests knows where it is and adjusts. For example using an absolute path to rtems-tests in a build directly results in it being able to find the development tree rtemstoolkit and configuration data. The command needs to be taught to find the development version of covoar.

Note, currently covoar needs external tools and this is currently using the environment's path however there is work underway to remove this dependence so there case does not need to be handled.

Change History (2)

comment:1 Changed on Jun 18, 2018 at 5:33:29 AM by Chris Johns

Resolution: fixed
Status: newclosed

comment:2 Changed on Jun 19, 2018 at 3:45:15 AM by Chris Johns <chrisj@…>

Owner: set to Chris Johns <chrisj@…>

In e341a65/rtems-tools:

tester: Make the path to covoar absolute to ignore the env PATH.

Using the environment's path to find covoar allow invalid versions
to be used which may vary in subtle ways. Find and use the covoar
that is build with the version of 'rtems-test'.

This patch means you do not need to install the tools before
running improving the development experience.

Closes #3458

Note: See TracTickets for help on using tickets.