On Fri, 23 Nov 2018 at 16:21, Chris Johns <chr...@rtems.org> wrote: > On 23 Nov 2018, at 8:55 pm, Vijay Kumar Banerjee <vijaykumar9...@gmail.com> > wrote: > > On Fri, 23 Nov 2018 at 15:09, Chris Johns <chr...@rtems.org> wrote: > >> On 23/11/18 7:32 pm, Vijay Kumar Banerjee wrote: >> > Hi, >> > I was trying to run coverage with rtems-test on a fresh install, and >> faced >> > the following errors. This is strange as everything was working and I >> can't >> > figure out what went wrong. >> > Also, I don't see covoar executable in the covoar/ directory. >> > >> > I'm using Python 2.7.15 >> >> Are you sure? The latest version selects the python used. >> >> `python --version` returns 2.7.15 > > > The python command may not be used. It could python3. > > If you do ... >> >> $ export RTEMS_PYTHON_OVERRIDE=python2 >> > ... does it work? >> >> Yes, this worked. Now I see > > error: coverage: covoar not found > > > I am not sure about this error but it does mean there maybe some issues > with python3. > > For some reason, the covoar executable is not installed in the tester/covoar directory, where the the script is searching for it.
The covoar is installed in the bin directory. Is there any reason that script searches for covoar in the tester/ instead of the bin directory? > Chris >
_______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
