Re: error while running rtems-test with coverage

Getting this error now seems like something is missing. RTEMS Testing - Tester, 5 (b2ba08b0da42 modified) Coverage environment prepared Traceback (most recent call last): File "/home/lunatic/development/rtems/test/rtems-tools/tester/rtems-test", line 40, in rt.test.run() File

Re: error while running rtems-test with coverage

On 13 April 2018 at 23:51, Cillian O'Donnell wrote: > Hmmm it's not there. Even so I can almost guarantee you, the reason it's > not running is that coverage_supported variable is not being found as true > in qemu.cfg and so the the command to generated the trace files

Re: error while running rtems-test with coverage

Hmmm it's not there. Even so I can almost guarantee you, the reason it's not running is that coverage_supported variable is not being found as true in qemu.cfg and so the the command to generated the trace files isn't run and there's no .cov files in the end. So that's what you'll have to dig

Re: error while running rtems-test with coverage

It just shows this.(with only hello) Running covoar for score WARNING: Unable to read coverage file /home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/hello/hello.exe.cov ERROR: No information to analyze ***Cleaning tempfiles*** error: covoar failure exit code: 1

Re: error while running rtems-test with coverage

Is there anywhere in that output that it shows the qemu command that is running? On Fri, 13 Apr 2018, 19:02 Vijay Kumar Banerjee, wrote: > > -- vijay > > On 13 April 2018 at 23:29, Cillian O'Donnell > wrote: > >> I can't say for certain but I

Re: error while running rtems-test with coverage

-- vijay On 13 April 2018 at 23:29, Cillian O'Donnell wrote: > I can't say for certain but I don't think that will be visible to qemu.cfg > unless it's a global variable. Chris might know off the top of his head. > > On Fri, 13 Apr 2018, 18:51 Vijay Kumar Banerjee,

Re: error while running rtems-test with coverage

I can't say for certain but I don't think that will be visible to qemu.cfg unless it's a global variable. Chris might know off the top of his head. On Fri, 13 Apr 2018, 18:51 Vijay Kumar Banerjee, wrote: > can we set it in [coverage] ? > > -- vijay > > On 13 April 2018

Re: error while running rtems-test with coverage

can we set it in [coverage] ? -- vijay On 13 April 2018 at 23:15, Cillian O'Donnell wrote: > Alright so we're back to ini update stuff. That error is because in the > old leon3-qemu.mc we had this global variable set. So you need to find > out how to get that global

Re: error while running rtems-test with coverage

Alright so we're back to ini update stuff. That error is because in the old leon3-qemu.mc we had this global variable set. So you need to find out how to get that global variable set in the new leon3-qemu.ini Heres the old version from the .MC file [global] bsp: none,

Re: MMU was Re: Contribute to a project under GSOC 2018

Sir, I have read following papers and have gained a good knowledge of RTEMS and RTEMS memory management. https://dl.acm.org/ft_gateway.cfm?id=2597459=pdf http://adsabs.harvard.edu/full/2005ESASP.602E..26S http://ieeexplore.ieee.org/abstract/document/4958736/ I would like to begin with the code

Re: error while running rtems-test with coverage

It shows the following error ... RTEMS Testing - Tester, 5 (58acb6d61ac7 modified) Coverage environment prepared [ 3/13] p:0 f:0 u:0 e:0 I:0 B:0 t:0 i:0 W:0 | sparc/leon3_qemu: cdtest.exe [ 1/13] p:0 f:0 u:0 e:0 I:0 B:0 t:0 i:0 W:0 | sparc/leon3_qemu: base_sp.exe [ 2/13] p:0

Re: error while running rtems-test with coverage

Ah yes, your missing the qemu arguments to run the coverage. Try this # # Coverage analysis # %define coverage_arg %{nil} %if %{defined _coverage} %if %{coverage_supported} %define coverage_arg -exec-trace %{test_executable}.cov %else %error "Coverage analysis unsupported

Re: error while running rtems-test with coverage

sure . # # RTEMS Tools Project (http://www.rtems.org/) # Copyright 2010-2014 Chris Johns (chr...@rtems.org) # All rights reserved. # # This file is part of the RTEMS Tools package in 'rtems-tools'. # # Redistribution and use in source and binary forms, with or without # modification, are

Re: error while running rtems-test with coverage

Yeah that's fine but can you just paste the contents here anyway. I'm not near a laptop and I can't remember which branch your starting from. On Fri, 13 Apr 2018, 13:51 Vijay Kumar Banerjee, wrote: > I haven't made any local changes to qemu.cfg > > -- vijay > > On 13

Re: error while running rtems-test with coverage

I haven't made any local changes to qemu.cfg -- vijay On 13 April 2018 at 11:43, Cillian O'Donnell wrote: > No that's the right one. I think it might be something to do with qemu.cfg > in rtems-tools then. What's in your qemu.cfg? It's in >

Re: [PATCH v2] build: Make entering the directories silent when building silent.

On 13/04/2018 16:10, Amaan Cheval wrote: > On Fri, Apr 13, 2018 at 5:49 AM Chris Johns wrote: > >> --- >> c/src/automake/subdirs.am | 3 ++- >> cpukit/automake/subdirs.am | 3 ++- >> testsuites/automake/subdirs.am | 3 ++- >> 3 files changed, 6 insertions(+), 3

Re: error while running rtems-test with coverage

No that's the right one. I think it might be something to do with qemu.cfg in rtems-tools then. What's in your qemu.cfg? It's in rtems-tools/tester/rtems/testing On Fri, 13 Apr 2018, 06:39 Vijay Kumar Banerjee, wrote: > I manually built qemu from here > >

Re: [PATCH v2] build: Make entering the directories silent when building silent.

On Fri, Apr 13, 2018 at 5:49 AM Chris Johns wrote: > --- > c/src/automake/subdirs.am | 3 ++- > cpukit/automake/subdirs.am | 3 ++- > testsuites/automake/subdirs.am | 3 ++- > 3 files changed, 6 insertions(+), 3 deletions(-) > diff --git