Re: while running rtems-test with coverage

[Joel Sherrill]

On Sun, May 16, 2021, 11:20 AM Vijay Kumar Banerjee  wrote:

> (Resending for the list)
>
> On Sun, May 16, 2021 at 10:18 AM Vijay Kumar Banerjee
>  wrote:
> >
> > Hi Mohammadreza,
> >
> > Sorry for the delay in replying :)
> >
> >
> > On Tue, May 11, 2021 at 11:39 AM mohammadreza tahzibi
> >  wrote:
> > >
> > > Dear Sir
> > > Hi,
> > >
> > > I am new in rtems and I am trying to run rtems-test ith enabling
> coverage.
> > >
> > Great.
> >
> > > But after many attempts I encountered the same problem and I am not
> able to handle this issue.
> > >
> > > I would be glad if you could resolve this issue.
> >
> > please try --rtems-bsp=xilinx_zynq_a9_qemu-cov
> >
> > As a convention, there are two versions of the config for the targets
> > that support coverage. The one with "-cov" suffix has the right
> > configuration to use with `--coverage` option.
> >
> >
> > Hope this helps.
> >
> > Best regards,
> > Vijay
> >
> >
> > > The error messages are attached below (atttachment).
> > >
> > > =
> > > root@xen:/home/work/sandbox2# rtems/5/bin/rtems-test
> --rtems-tools=/home/work/sandbox2/rtems/5/  --log=coverage-analysis.log
> --rtems-bsp=xilinx_zynq_a9_qemu --target=arm-rtems5   --coverage
> rtems-libbsd/build/arm-rtems5-xilinx_zynq_a9_qemu-default/selectpollkqueue01.exe
> > > RTEMS Testing - Tester, 5 (d697769d4682 modified)
> > > Traceback (most recent call last):
> > >   File "rtems/5/share/rtems/tester/rt/cmd-test.py", line 42, in
> 
> > > test.run(sys.argv[1:], command_path = base)
> > >   File "/home/work/sandbox2/rtems/5/share/rtems/tester/rt/test.py",
> line 446, in run
> > > trace = cov_trace)
> > >   File
> "/home/work/sandbox2/rtems/5/share/rtems/tester/rt/coverage.py", line 385,
> in __init__
> > > self.target = self.macros['target']
> > >   File
> "/home/work/sandbox2/rtems/5/share/rtems/rtemstoolkit/macros.py", line 195,
> in __getitem__
> > > raise IndexError('key: %s' % (key))
> > > IndexError: key: target
> > >
> > >
> > > =
>

Coverage was broken until a lot of recent work by Alex. You have to have
qemu-couverture and must be on the master.

There hasn't been any talk of back porting all this.  It would likely be a
heavy copy and paste from 6 to 5 and a lot of testing.


> >
> > >
> > > Thank you for your assistance.
> > > Regards
> > >
> > >
> > >
> ___
> devel mailing list
> devel@rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: while running rtems-test with coverage

[Vijay Kumar Banerjee]

(Resending for the list)

On Sun, May 16, 2021 at 10:18 AM Vijay Kumar Banerjee
 wrote:
>
> Hi Mohammadreza,
>
> Sorry for the delay in replying :)
>
>
> On Tue, May 11, 2021 at 11:39 AM mohammadreza tahzibi
>  wrote:
> >
> > Dear Sir
> > Hi,
> >
> > I am new in rtems and I am trying to run rtems-test ith enabling coverage.
> >
> Great.
>
> > But after many attempts I encountered the same problem and I am not able to 
> > handle this issue.
> >
> > I would be glad if you could resolve this issue.
>
> please try --rtems-bsp=xilinx_zynq_a9_qemu-cov
>
> As a convention, there are two versions of the config for the targets
> that support coverage. The one with "-cov" suffix has the right
> configuration to use with `--coverage` option.
>
>
> Hope this helps.
>
> Best regards,
> Vijay
>
>
> > The error messages are attached below (atttachment).
> >
> > =
> > root@xen:/home/work/sandbox2# rtems/5/bin/rtems-test 
> > --rtems-tools=/home/work/sandbox2/rtems/5/  --log=coverage-analysis.log  
> > --rtems-bsp=xilinx_zynq_a9_qemu --target=arm-rtems5   --coverage  
> > rtems-libbsd/build/arm-rtems5-xilinx_zynq_a9_qemu-default/selectpollkqueue01.exe
> > RTEMS Testing - Tester, 5 (d697769d4682 modified)
> > Traceback (most recent call last):
> >   File "rtems/5/share/rtems/tester/rt/cmd-test.py", line 42, in 
> > test.run(sys.argv[1:], command_path = base)
> >   File "/home/work/sandbox2/rtems/5/share/rtems/tester/rt/test.py", line 
> > 446, in run
> > trace = cov_trace)
> >   File "/home/work/sandbox2/rtems/5/share/rtems/tester/rt/coverage.py", 
> > line 385, in __init__
> > self.target = self.macros['target']
> >   File "/home/work/sandbox2/rtems/5/share/rtems/rtemstoolkit/macros.py", 
> > line 195, in __getitem__
> > raise IndexError('key: %s' % (key))
> > IndexError: key: target
> >
> >
> > =
> >
> >
> > Thank you for your assistance.
> > Regards
> >
> >
> >
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: error while running rtems-test with coverage

[Cillian O'Donnell]

Yup good idea.

On Mon, 16 Apr 2018, 08:23 Vijay Kumar Banerjee, 
wrote:

> the coverage is running now, shall we start a new mail thread for
> covoar report ?
>
> -- vijay
>
> On 16 April 2018 at 12:35, Vijay Kumar Banerjee 
> wrote:
>
>> Ok thanks, so now we need to look into covoar.
>> Do you have any sample output that will give me an idea of what it should
>> look like ?
>>
>> On Mon, 16 Apr 2018, 11:13 Cillian O'Donnell, 
>> wrote:
>>
>>> Probably what'll happen is, when the reports are generating properly,
>>> Chris will review the changes and come up with a list of blockers that must
>>> be fixed before he would be happy accepting the code into rtems-tools
>>> master. Then when that's done you can submit the patches.
>>>
>>> The thing with the data missing from the reports is tricky because
>>> there's no error messages or log output to go on. Last time I seen that it
>>> was because we were changing how the symbols were parsed and they were
>>> being chopped up in odd ways and so none of them were found and so the
>>> report was empty. This time I'm not sure because we haven't changed
>>> anything like that. If I think of any clues, I'll let you know.
>>>
>>> On Mon, 16 Apr 2018, 05:36 Vijay Kumar Banerjee, <
>>> vijaykumar9...@gmail.com> wrote:
>>>


 On 15 April 2018 at 15:33, Cillian O'Donnell 
 wrote:

>
>
> On 15 April 2018 at 10:09, Cillian O'Donnell 
> wrote:
>
>> Not sure what's happening there. Send me a link to your github branch.
>>
>> On 15 April 2018 at 09:35, Vijay Kumar Banerjee <
>> vijaykumar9...@gmail.com> wrote:
>>
>>>
>>>
>>> On 15 April 2018 at 14:02, Cillian O'Donnell 
>>> wrote:
>>>


 On 15 April 2018 at 06:46, Vijay Kumar Banerjee <
 vijaykumar9...@gmail.com> wrote:

>
>
> On 15 April 2018 at 01:45, Cillian O'Donnell <
> cpodonne...@gmail.com> wrote:
>
>> Switch one of these lines out in qemu.cfg.
>>
>> #%define qemu_opts_base -no-reboot -monitor none -serial stdio
>> -nographic
>> #%define qemu_opts_base -no-reboot -serial null -serial
>> mon:stdio -nographic
>> %define qemu_opts_base -no-reboot -monitor null -serial stdio
>> -nographic
>>
>> Just comment out the one that's being used and uncomment one of
>> the others. It should cause a complaint when the tests are run and 
>> the qemu
>> cmd should show up in the log so we can take a look at it.
>>
>
>
> error: qemu.cfg:71: execute failed: qemu-system-sparc -no-reboot
> -monitor null -serial stdio -nographic -no-reboot -monitor null 
> -serial
> stdio -nographic -M leon3_generic -kernel
> /home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/unlimited/unlimited.exe:
> exit-code:1
>
> run: qemu-system-sparc -no-reboot -monitor null -serial stdio
> -nographic -no-reboot -monitor null -serial stdio -nographic -M
> leon3_generic -kernel /home/lunatic/development/rtem
> s/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/unlimited/unlimited.exe
> -exec-trace
>  
> /home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/unlimi
>   ted/unlimited.exe.cov
>

 Are those line breaks actually there or is it from the copy and
 paste. Like  unlimited. If so that's definitely the problem. What 
 does
 your last section in qemu.cfg look like now? The execute section.

>>> They are from copy paste .
>>> I'm pasting the qemu.cfg here
>>> .
>>>
>>> #
>>> # 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 permitted provided that the following conditions
>>> are met:
>>> #
>>> # 1. Redistributions of source code must retain the above copyright
>>> notice,
>>> # this list of conditions and the following disclaimer.
>>> #
>>> # 2. Redistributions in binary form must reproduce the above
>>> copyright notice,
>>> # this list of conditions and the following disclaimer in the
>>> documentation
>>> # and/or other materials provided with the distribution.
>>> #
>>> # this software is provided by the copyright holders and
>>> contributors "as is"
>>> # and any express or implied warranties, including, but not limited
>>> to, the
>>> # implied warranties of merchantability and fitness for a particular
>>> purpose
>>> # are disclaimed. in no eve

Re: error while running rtems-test with coverage

[Vijay Kumar Banerjee]

the coverage is running now, shall we start a new mail thread for
covoar report ?

-- vijay

On 16 April 2018 at 12:35, Vijay Kumar Banerjee 
wrote:

> Ok thanks, so now we need to look into covoar.
> Do you have any sample output that will give me an idea of what it should
> look like ?
>
> On Mon, 16 Apr 2018, 11:13 Cillian O'Donnell, 
> wrote:
>
>> Probably what'll happen is, when the reports are generating properly,
>> Chris will review the changes and come up with a list of blockers that must
>> be fixed before he would be happy accepting the code into rtems-tools
>> master. Then when that's done you can submit the patches.
>>
>> The thing with the data missing from the reports is tricky because
>> there's no error messages or log output to go on. Last time I seen that it
>> was because we were changing how the symbols were parsed and they were
>> being chopped up in odd ways and so none of them were found and so the
>> report was empty. This time I'm not sure because we haven't changed
>> anything like that. If I think of any clues, I'll let you know.
>>
>> On Mon, 16 Apr 2018, 05:36 Vijay Kumar Banerjee, <
>> vijaykumar9...@gmail.com> wrote:
>>
>>>
>>>
>>> On 15 April 2018 at 15:33, Cillian O'Donnell 
>>> wrote:
>>>


 On 15 April 2018 at 10:09, Cillian O'Donnell 
 wrote:

> Not sure what's happening there. Send me a link to your github branch.
>
> On 15 April 2018 at 09:35, Vijay Kumar Banerjee <
> vijaykumar9...@gmail.com> wrote:
>
>>
>>
>> On 15 April 2018 at 14:02, Cillian O'Donnell 
>> wrote:
>>
>>>
>>>
>>> On 15 April 2018 at 06:46, Vijay Kumar Banerjee <
>>> vijaykumar9...@gmail.com> wrote:
>>>


 On 15 April 2018 at 01:45, Cillian O'Donnell >>> > wrote:

> Switch one of these lines out in qemu.cfg.
>
> #%define qemu_opts_base -no-reboot -monitor none -serial stdio
> -nographic
> #%define qemu_opts_base -no-reboot -serial null -serial mon:stdio
> -nographic
> %define qemu_opts_base -no-reboot -monitor null -serial stdio
> -nographic
>
> Just comment out the one that's being used and uncomment one of
> the others. It should cause a complaint when the tests are run and 
> the qemu
> cmd should show up in the log so we can take a look at it.
>


 error: qemu.cfg:71: execute failed: qemu-system-sparc -no-reboot
 -monitor null -serial stdio -nographic -no-reboot -monitor null -serial
 stdio -nographic -M leon3_generic -kernel 
 /home/lunatic/development/rtem
 s/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/unlimited/unlimited.exe:
 exit-code:1

 run: qemu-system-sparc -no-reboot -monitor null -serial stdio
 -nographic -no-reboot -monitor null -serial stdio -nographic -M
 leon3_generic -kernel /home/lunatic/development/rtem
 s/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/unlimited/unlimited.exe
 -exec-trace /home/lunatic/development/rte
 ms/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/unlimi
 ted/unlimited.exe.cov

>>>
>>> Are those line breaks actually there or is it from the copy and
>>> paste. Like  unlimited. If so that's definitely the problem. What 
>>> does
>>> your last section in qemu.cfg look like now? The execute section.
>>>
>> They are from copy paste .
>> I'm pasting the qemu.cfg here
>> .
>>
>> #
>> # 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 permitted provided that the following conditions
>> are met:
>> #
>> # 1. Redistributions of source code must retain the above copyright
>> notice,
>> # this list of conditions and the following disclaimer.
>> #
>> # 2. Redistributions in binary form must reproduce the above
>> copyright notice,
>> # this list of conditions and the following disclaimer in the
>> documentation
>> # and/or other materials provided with the distribution.
>> #
>> # this software is provided by the copyright holders and contributors
>> "as is"
>> # and any express or implied warranties, including, but not limited
>> to, the
>> # implied warranties of merchantability and fitness for a particular
>> purpose
>> # are disclaimed. in no event shall the copyright holder or
>> contributors be
>> # liable for any direct, indirect, incidental, special, exemplary, or
>> # consequential damages (including, but not limited to, procurement of
>> # substitute goods or 

Re: error while running rtems-test with coverage

[Cillian O'Donnell]

I don't have a screen shot of it. If you firefox report.html and have a
look, all the bits that are NaN and all that will be filled with a
percentage coverage for all symbol sets tested (the only set in
symbol-sets.cfg is score at the moment so the coverage will be the tests
that were run on that set) it should be fairly obvious when it has worked,
there'll actually be something decent to look at so you'll probably know it
when you see it.

On Mon, 16 Apr 2018, 08:05 Vijay Kumar Banerjee, 
wrote:

> Ok thanks, so now we need to look into covoar.
> Do you have any sample output that will give me an idea of what it should
> look like ?
>
> On Mon, 16 Apr 2018, 11:13 Cillian O'Donnell, 
> wrote:
>
>> Probably what'll happen is, when the reports are generating properly,
>> Chris will review the changes and come up with a list of blockers that must
>> be fixed before he would be happy accepting the code into rtems-tools
>> master. Then when that's done you can submit the patches.
>>
>> The thing with the data missing from the reports is tricky because
>> there's no error messages or log output to go on. Last time I seen that it
>> was because we were changing how the symbols were parsed and they were
>> being chopped up in odd ways and so none of them were found and so the
>> report was empty. This time I'm not sure because we haven't changed
>> anything like that. If I think of any clues, I'll let you know.
>>
>> On Mon, 16 Apr 2018, 05:36 Vijay Kumar Banerjee, <
>> vijaykumar9...@gmail.com> wrote:
>>
>>>
>>>
>>> On 15 April 2018 at 15:33, Cillian O'Donnell 
>>> wrote:
>>>


 On 15 April 2018 at 10:09, Cillian O'Donnell 
 wrote:

> Not sure what's happening there. Send me a link to your github branch.
>
> On 15 April 2018 at 09:35, Vijay Kumar Banerjee <
> vijaykumar9...@gmail.com> wrote:
>
>>
>>
>> On 15 April 2018 at 14:02, Cillian O'Donnell 
>> wrote:
>>
>>>
>>>
>>> On 15 April 2018 at 06:46, Vijay Kumar Banerjee <
>>> vijaykumar9...@gmail.com> wrote:
>>>


 On 15 April 2018 at 01:45, Cillian O'Donnell >>> > wrote:

> Switch one of these lines out in qemu.cfg.
>
> #%define qemu_opts_base -no-reboot -monitor none -serial stdio
> -nographic
> #%define qemu_opts_base -no-reboot -serial null -serial mon:stdio
> -nographic
> %define qemu_opts_base -no-reboot -monitor null -serial stdio
> -nographic
>
> Just comment out the one that's being used and uncomment one of
> the others. It should cause a complaint when the tests are run and 
> the qemu
> cmd should show up in the log so we can take a look at it.
>


 error: qemu.cfg:71: execute failed: qemu-system-sparc -no-reboot
 -monitor null -serial stdio -nographic -no-reboot -monitor null -serial
 stdio -nographic -M leon3_generic -kernel
 /home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/unlimited/unlimited.exe:
 exit-code:1

 run: qemu-system-sparc -no-reboot -monitor null -serial stdio
 -nographic -no-reboot -monitor null -serial stdio -nographic -M
 leon3_generic -kernel /home/lunatic/development/rtem
 s/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/unlimited/unlimited.exe
 -exec-trace
  
 /home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/unlimi
   ted/unlimited.exe.cov

>>>
>>> Are those line breaks actually there or is it from the copy and
>>> paste. Like  unlimited. If so that's definitely the problem. What 
>>> does
>>> your last section in qemu.cfg look like now? The execute section.
>>>
>> They are from copy paste .
>> I'm pasting the qemu.cfg here
>> .
>>
>> #
>> # 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 permitted provided that the following conditions
>> are met:
>> #
>> # 1. Redistributions of source code must retain the above copyright
>> notice,
>> # this list of conditions and the following disclaimer.
>> #
>> # 2. Redistributions in binary form must reproduce the above
>> copyright notice,
>> # this list of conditions and the following disclaimer in the
>> documentation
>> # and/or other materials provided with the distribution.
>> #
>> # this software is provided by the copyright holders and contributors
>> "as is"
>> # and any express or implied warranties, including, but not limited
>> to, the
>> # implie

Re: error while running rtems-test with coverage

[Vijay Kumar Banerjee]

Ok thanks, so now we need to look into covoar.
Do you have any sample output that will give me an idea of what it should
look like ?

On Mon, 16 Apr 2018, 11:13 Cillian O'Donnell,  wrote:

> Probably what'll happen is, when the reports are generating properly,
> Chris will review the changes and come up with a list of blockers that must
> be fixed before he would be happy accepting the code into rtems-tools
> master. Then when that's done you can submit the patches.
>
> The thing with the data missing from the reports is tricky because there's
> no error messages or log output to go on. Last time I seen that it was
> because we were changing how the symbols were parsed and they were being
> chopped up in odd ways and so none of them were found and so the report was
> empty. This time I'm not sure because we haven't changed anything like
> that. If I think of any clues, I'll let you know.
>
> On Mon, 16 Apr 2018, 05:36 Vijay Kumar Banerjee, 
> wrote:
>
>>
>>
>> On 15 April 2018 at 15:33, Cillian O'Donnell 
>> wrote:
>>
>>>
>>>
>>> On 15 April 2018 at 10:09, Cillian O'Donnell 
>>> wrote:
>>>
 Not sure what's happening there. Send me a link to your github branch.

 On 15 April 2018 at 09:35, Vijay Kumar Banerjee <
 vijaykumar9...@gmail.com> wrote:

>
>
> On 15 April 2018 at 14:02, Cillian O'Donnell 
> wrote:
>
>>
>>
>> On 15 April 2018 at 06:46, Vijay Kumar Banerjee <
>> vijaykumar9...@gmail.com> wrote:
>>
>>>
>>>
>>> On 15 April 2018 at 01:45, Cillian O'Donnell 
>>> wrote:
>>>
 Switch one of these lines out in qemu.cfg.

 #%define qemu_opts_base -no-reboot -monitor none -serial stdio
 -nographic
 #%define qemu_opts_base -no-reboot -serial null -serial mon:stdio
 -nographic
 %define qemu_opts_base -no-reboot -monitor null -serial stdio
 -nographic

 Just comment out the one that's being used and uncomment one of the
 others. It should cause a complaint when the tests are run and the 
 qemu cmd
 should show up in the log so we can take a look at it.

>>>
>>>
>>> error: qemu.cfg:71: execute failed: qemu-system-sparc -no-reboot
>>> -monitor null -serial stdio -nographic -no-reboot -monitor null -serial
>>> stdio -nographic -M leon3_generic -kernel /home/lunatic/development/
>>> rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/
>>> samples/unlimited/unlimited.exe: exit-code:1
>>>
>>> run: qemu-system-sparc -no-reboot -monitor null -serial stdio
>>> -nographic -no-reboot -monitor null -serial stdio -nographic -M
>>> leon3_generic -kernel /home/lunatic/development/rtem
>>> s/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/unlimited/unlimited.exe
>>> -exec-trace /home/lunatic/development/rtems/kernel/leon3/sparc-
>>> rtems5/c/leon3/testsuites/samples/unlimited/unlimited.exe.cov
>>>
>>
>> Are those line breaks actually there or is it from the copy and
>> paste. Like  unlimited. If so that's definitely the problem. What 
>> does
>> your last section in qemu.cfg look like now? The execute section.
>>
> They are from copy paste .
> I'm pasting the qemu.cfg here
> .
>
> #
> # 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 permitted provided that the following conditions
> are met:
> #
> # 1. Redistributions of source code must retain the above copyright
> notice,
> # this list of conditions and the following disclaimer.
> #
> # 2. Redistributions in binary form must reproduce the above copyright
> notice,
> # this list of conditions and the following disclaimer in the
> documentation
> # and/or other materials provided with the distribution.
> #
> # this software is provided by the copyright holders and contributors
> "as is"
> # and any express or implied warranties, including, but not limited
> to, the
> # implied warranties of merchantability and fitness for a particular
> purpose
> # are disclaimed. in no event shall the copyright holder or
> contributors be
> # liable for any direct, indirect, incidental, special, exemplary, or
> # consequential damages (including, but not limited to, procurement of
> # substitute goods or services; loss of use, data, or profits; or
> business
> # interruption) however caused and on any theory of liability, whether
> in
> # contract, strict liability, or tort (including negligence or
> otherwise)
> # arising in any way out of the use of this software, even if advised
> of the

Re: error while running rtems-test with coverage

[Cillian O'Donnell]

Probably what'll happen is, when the reports are generating properly, Chris
will review the changes and come up with a list of blockers that must be
fixed before he would be happy accepting the code into rtems-tools master.
Then when that's done you can submit the patches.

The thing with the data missing from the reports is tricky because there's
no error messages or log output to go on. Last time I seen that it was
because we were changing how the symbols were parsed and they were being
chopped up in odd ways and so none of them were found and so the report was
empty. This time I'm not sure because we haven't changed anything like
that. If I think of any clues, I'll let you know.

On Mon, 16 Apr 2018, 05:36 Vijay Kumar Banerjee, 
wrote:

>
>
> On 15 April 2018 at 15:33, Cillian O'Donnell 
> wrote:
>
>>
>>
>> On 15 April 2018 at 10:09, Cillian O'Donnell 
>> wrote:
>>
>>> Not sure what's happening there. Send me a link to your github branch.
>>>
>>> On 15 April 2018 at 09:35, Vijay Kumar Banerjee <
>>> vijaykumar9...@gmail.com> wrote:
>>>


 On 15 April 2018 at 14:02, Cillian O'Donnell 
 wrote:

>
>
> On 15 April 2018 at 06:46, Vijay Kumar Banerjee <
> vijaykumar9...@gmail.com> wrote:
>
>>
>>
>> On 15 April 2018 at 01:45, Cillian O'Donnell 
>> wrote:
>>
>>> Switch one of these lines out in qemu.cfg.
>>>
>>> #%define qemu_opts_base -no-reboot -monitor none -serial stdio
>>> -nographic
>>> #%define qemu_opts_base -no-reboot -serial null -serial mon:stdio
>>> -nographic
>>> %define qemu_opts_base -no-reboot -monitor null -serial stdio
>>> -nographic
>>>
>>> Just comment out the one that's being used and uncomment one of the
>>> others. It should cause a complaint when the tests are run and the qemu 
>>> cmd
>>> should show up in the log so we can take a look at it.
>>>
>>
>>
>> error: qemu.cfg:71: execute failed: qemu-system-sparc -no-reboot
>> -monitor null -serial stdio -nographic -no-reboot -monitor null -serial
>> stdio -nographic -M leon3_generic -kernel
>> /home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/unlimited/unlimited.exe:
>> exit-code:1
>>
>> run: qemu-system-sparc -no-reboot -monitor null -serial stdio
>> -nographic -no-reboot -monitor null -serial stdio -nographic -M
>> leon3_generic -kernel /home/lunatic/development/rtem
>> s/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/unlimited/unlimited.exe
>> -exec-trace
>>  
>> /home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/unlimi
>>   ted/unlimited.exe.cov
>>
>
> Are those line breaks actually there or is it from the copy and paste.
> Like  unlimited. If so that's definitely the problem. What does your
> last section in qemu.cfg look like now? The execute section.
>
 They are from copy paste .
 I'm pasting the qemu.cfg here
 .

 #
 # 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 permitted provided that the following conditions
 are met:
 #
 # 1. Redistributions of source code must retain the above copyright
 notice,
 # this list of conditions and the following disclaimer.
 #
 # 2. Redistributions in binary form must reproduce the above copyright
 notice,
 # this list of conditions and the following disclaimer in the
 documentation
 # and/or other materials provided with the distribution.
 #
 # this software is provided by the copyright holders and contributors
 "as is"
 # and any express or implied warranties, including, but not limited to,
 the
 # implied warranties of merchantability and fitness for a particular
 purpose
 # are disclaimed. in no event shall the copyright holder or
 contributors be
 # liable for any direct, indirect, incidental, special, exemplary, or
 # consequential damages (including, but not limited to, procurement of
 # substitute goods or services; loss of use, data, or profits; or
 business
 # interruption) however caused and on any theory of liability, whether
 in
 # contract, strict liability, or tort (including negligence or
 otherwise)
 # arising in any way out of the use of this software, even if advised
 of the
 # possibility of such damage.
 #

 #
 # qemu
 #
 # use a qemu command to run the executable in the qemu simulator.
 #

 %include %{_configdir}/base.cfg
 %include %{_configdir}/checks.cfg

 #
 # console.
 #
 %define console_stdio
 %include %{_configdir}/c

Re: error while running rtems-test with coverage

[Vijay Kumar Banerjee]

On 15 April 2018 at 15:33, Cillian O'Donnell  wrote:

>
>
> On 15 April 2018 at 10:09, Cillian O'Donnell 
> wrote:
>
>> Not sure what's happening there. Send me a link to your github branch.
>>
>> On 15 April 2018 at 09:35, Vijay Kumar Banerjee > > wrote:
>>
>>>
>>>
>>> On 15 April 2018 at 14:02, Cillian O'Donnell 
>>> wrote:
>>>


 On 15 April 2018 at 06:46, Vijay Kumar Banerjee <
 vijaykumar9...@gmail.com> wrote:

>
>
> On 15 April 2018 at 01:45, Cillian O'Donnell 
> wrote:
>
>> Switch one of these lines out in qemu.cfg.
>>
>> #%define qemu_opts_base -no-reboot -monitor none -serial stdio
>> -nographic
>> #%define qemu_opts_base -no-reboot -serial null -serial mon:stdio
>> -nographic
>> %define qemu_opts_base -no-reboot -monitor null -serial stdio
>> -nographic
>>
>> Just comment out the one that's being used and uncomment one of the
>> others. It should cause a complaint when the tests are run and the qemu 
>> cmd
>> should show up in the log so we can take a look at it.
>>
>
>
> error: qemu.cfg:71: execute failed: qemu-system-sparc -no-reboot
> -monitor null -serial stdio -nographic -no-reboot -monitor null -serial
> stdio -nographic -M leon3_generic -kernel /home/lunatic/development/rtem
> s/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/unlimited/unlimited.exe:
> exit-code:1
>
> run: qemu-system-sparc -no-reboot -monitor null -serial stdio
> -nographic -no-reboot -monitor null -serial stdio -nographic -M
> leon3_generic -kernel /home/lunatic/development/rtem
> s/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/unlimited/unlimited.exe
> -exec-trace /home/lunatic/development/rte
> ms/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/unlimi
> ted/unlimited.exe.cov
>

 Are those line breaks actually there or is it from the copy and paste.
 Like  unlimited. If so that's definitely the problem. What does your
 last section in qemu.cfg look like now? The execute section.

>>> They are from copy paste .
>>> I'm pasting the qemu.cfg here
>>> .
>>>
>>> #
>>> # 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 permitted provided that the following conditions are
>>> met:
>>> #
>>> # 1. Redistributions of source code must retain the above copyright
>>> notice,
>>> # this list of conditions and the following disclaimer.
>>> #
>>> # 2. Redistributions in binary form must reproduce the above copyright
>>> notice,
>>> # this list of conditions and the following disclaimer in the
>>> documentation
>>> # and/or other materials provided with the distribution.
>>> #
>>> # this software is provided by the copyright holders and contributors
>>> "as is"
>>> # and any express or implied warranties, including, but not limited to,
>>> the
>>> # implied warranties of merchantability and fitness for a particular
>>> purpose
>>> # are disclaimed. in no event shall the copyright holder or contributors
>>> be
>>> # liable for any direct, indirect, incidental, special, exemplary, or
>>> # consequential damages (including, but not limited to, procurement of
>>> # substitute goods or services; loss of use, data, or profits; or
>>> business
>>> # interruption) however caused and on any theory of liability, whether in
>>> # contract, strict liability, or tort (including negligence or otherwise)
>>> # arising in any way out of the use of this software, even if advised of
>>> the
>>> # possibility of such damage.
>>> #
>>>
>>> #
>>> # qemu
>>> #
>>> # use a qemu command to run the executable in the qemu simulator.
>>> #
>>>
>>> %include %{_configdir}/base.cfg
>>> %include %{_configdir}/checks.cfg
>>>
>>> #
>>> # console.
>>> #
>>> %define console_stdio
>>> %include %{_configdir}/console.cfg
>>>
>>> #
>>> # rtems version
>>> #
>>> %include %{_rtdir}/rtems/version.cfg
>>>
>>> #
>>> # qemu common option patterns.
>>> #
>>> %define qemu_opts_base   -no-reboot -monitor none -serial stdio
>>> -nographic
>>> #%define qemu_opts_base   -no-reboot -serial null -serial mon:stdio
>>> -nographic
>>> #%define qemu_opts_base  -no-reboot -monitor null -serial stdio
>>> -nographic
>>> %define qemu_opts_no_net -net none
>>> #
>>> # qemu executable
>>> #
>>> %ifn %{defined bsp_qemu_opts}
>>>  %define bsp_qemu_opts %{nil}
>>> %endif
>>> %define qemu_cmd  qemu-system-%{bsp_arch}
>>> %define qemu_opts %{bsp_qemu_opts}
>>>
>>>
>>> #
>>> # 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 for %{bsp}"
>>>

Re: error while running rtems-test with coverage

[Cillian O'Donnell]

On 15 April 2018 at 10:09, Cillian O'Donnell  wrote:

> Not sure what's happening there. Send me a link to your github branch.
>
> On 15 April 2018 at 09:35, Vijay Kumar Banerjee 
> wrote:
>
>>
>>
>> On 15 April 2018 at 14:02, Cillian O'Donnell 
>> wrote:
>>
>>>
>>>
>>> On 15 April 2018 at 06:46, Vijay Kumar Banerjee <
>>> vijaykumar9...@gmail.com> wrote:
>>>


 On 15 April 2018 at 01:45, Cillian O'Donnell 
 wrote:

> Switch one of these lines out in qemu.cfg.
>
> #%define qemu_opts_base -no-reboot -monitor none -serial stdio
> -nographic
> #%define qemu_opts_base -no-reboot -serial null -serial mon:stdio
> -nographic
> %define qemu_opts_base -no-reboot -monitor null -serial stdio
> -nographic
>
> Just comment out the one that's being used and uncomment one of the
> others. It should cause a complaint when the tests are run and the qemu 
> cmd
> should show up in the log so we can take a look at it.
>


 error: qemu.cfg:71: execute failed: qemu-system-sparc -no-reboot
 -monitor null -serial stdio -nographic -no-reboot -monitor null -serial
 stdio -nographic -M leon3_generic -kernel /home/lunatic/development/rtem
 s/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/unlimited/unlimited.exe:
 exit-code:1

 run: qemu-system-sparc -no-reboot -monitor null -serial stdio
 -nographic -no-reboot -monitor null -serial stdio -nographic -M
 leon3_generic -kernel /home/lunatic/development/rtem
 s/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/unlimited/unlimited.exe
 -exec-trace /home/lunatic/development/rte
 ms/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/unlimi
 ted/unlimited.exe.cov

>>>
>>> Are those line breaks actually there or is it from the copy and paste.
>>> Like  unlimited. If so that's definitely the problem. What does your
>>> last section in qemu.cfg look like now? The execute section.
>>>
>> They are from copy paste .
>> I'm pasting the qemu.cfg here
>> .
>>
>> #
>> # 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 permitted provided that the following conditions are
>> met:
>> #
>> # 1. Redistributions of source code must retain the above copyright
>> notice,
>> # this list of conditions and the following disclaimer.
>> #
>> # 2. Redistributions in binary form must reproduce the above copyright
>> notice,
>> # this list of conditions and the following disclaimer in the
>> documentation
>> # and/or other materials provided with the distribution.
>> #
>> # this software is provided by the copyright holders and contributors "as
>> is"
>> # and any express or implied warranties, including, but not limited to,
>> the
>> # implied warranties of merchantability and fitness for a particular
>> purpose
>> # are disclaimed. in no event shall the copyright holder or contributors
>> be
>> # liable for any direct, indirect, incidental, special, exemplary, or
>> # consequential damages (including, but not limited to, procurement of
>> # substitute goods or services; loss of use, data, or profits; or business
>> # interruption) however caused and on any theory of liability, whether in
>> # contract, strict liability, or tort (including negligence or otherwise)
>> # arising in any way out of the use of this software, even if advised of
>> the
>> # possibility of such damage.
>> #
>>
>> #
>> # qemu
>> #
>> # use a qemu command to run the executable in the qemu simulator.
>> #
>>
>> %include %{_configdir}/base.cfg
>> %include %{_configdir}/checks.cfg
>>
>> #
>> # console.
>> #
>> %define console_stdio
>> %include %{_configdir}/console.cfg
>>
>> #
>> # rtems version
>> #
>> %include %{_rtdir}/rtems/version.cfg
>>
>> #
>> # qemu common option patterns.
>> #
>> %define qemu_opts_base   -no-reboot -monitor none -serial stdio -nographic
>> #%define qemu_opts_base   -no-reboot -serial null -serial mon:stdio
>> -nographic
>> #%define qemu_opts_base  -no-reboot -monitor null -serial stdio -nographic
>> %define qemu_opts_no_net -net none
>> #
>> # qemu executable
>> #
>> %ifn %{defined bsp_qemu_opts}
>>  %define bsp_qemu_opts %{nil}
>> %endif
>> %define qemu_cmd  qemu-system-%{bsp_arch}
>> %define qemu_opts %{bsp_qemu_opts}
>>
>>
>> #
>> # 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 for %{bsp}"
>> %endif
>> %endif
>>
>> #
>> # executable
>> #
>>
>> #%execute %{qemu_cmd} %{qemu_opts} -kernel %{test_executable}
>> %execute %{qemu_cmd} %{qemu_opts_base} %{qemu_opts} -kernel
>> %{test_executable} %{coverage_arg}
>>
>

Re: error while running rtems-test with coverage

[Cillian O'Donnell]

Not sure what's happening there. Send me a link to your github branch.

On 15 April 2018 at 09:35, Vijay Kumar Banerjee 
wrote:

>
>
> On 15 April 2018 at 14:02, Cillian O'Donnell 
> wrote:
>
>>
>>
>> On 15 April 2018 at 06:46, Vijay Kumar Banerjee > > wrote:
>>
>>>
>>>
>>> On 15 April 2018 at 01:45, Cillian O'Donnell 
>>> wrote:
>>>
 Switch one of these lines out in qemu.cfg.

 #%define qemu_opts_base -no-reboot -monitor none -serial stdio
 -nographic
 #%define qemu_opts_base -no-reboot -serial null -serial mon:stdio
 -nographic
 %define qemu_opts_base -no-reboot -monitor null -serial stdio -nographic

 Just comment out the one that's being used and uncomment one of the
 others. It should cause a complaint when the tests are run and the qemu cmd
 should show up in the log so we can take a look at it.

>>>
>>>
>>> error: qemu.cfg:71: execute failed: qemu-system-sparc -no-reboot
>>> -monitor null -serial stdio -nographic -no-reboot -monitor null -serial
>>> stdio -nographic -M leon3_generic -kernel /home/lunatic/development/rtem
>>> s/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/unlimited/unlimited.exe:
>>> exit-code:1
>>>
>>> run: qemu-system-sparc -no-reboot -monitor null -serial stdio -nographic
>>> -no-reboot -monitor null -serial stdio -nographic -M leon3_generic
>>> -kernel /home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/
>>> leon3/testsuites/samples/unlimited/unlimited.exe -exec-trace
>>>  /home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c
>>> /leon3/testsuites/samples/unlimited/unlimited.exe.cov
>>>
>>
>> Are those line breaks actually there or is it from the copy and paste.
>> Like  unlimited. If so that's definitely the problem. What does your
>> last section in qemu.cfg look like now? The execute section.
>>
> They are from copy paste .
> I'm pasting the qemu.cfg here
> .
>
> #
> # 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 permitted provided that the following conditions are
> met:
> #
> # 1. Redistributions of source code must retain the above copyright notice,
> # this list of conditions and the following disclaimer.
> #
> # 2. Redistributions in binary form must reproduce the above copyright
> notice,
> # this list of conditions and the following disclaimer in the documentation
> # and/or other materials provided with the distribution.
> #
> # this software is provided by the copyright holders and contributors "as
> is"
> # and any express or implied warranties, including, but not limited to, the
> # implied warranties of merchantability and fitness for a particular
> purpose
> # are disclaimed. in no event shall the copyright holder or contributors be
> # liable for any direct, indirect, incidental, special, exemplary, or
> # consequential damages (including, but not limited to, procurement of
> # substitute goods or services; loss of use, data, or profits; or business
> # interruption) however caused and on any theory of liability, whether in
> # contract, strict liability, or tort (including negligence or otherwise)
> # arising in any way out of the use of this software, even if advised of
> the
> # possibility of such damage.
> #
>
> #
> # qemu
> #
> # use a qemu command to run the executable in the qemu simulator.
> #
>
> %include %{_configdir}/base.cfg
> %include %{_configdir}/checks.cfg
>
> #
> # console.
> #
> %define console_stdio
> %include %{_configdir}/console.cfg
>
> #
> # rtems version
> #
> %include %{_rtdir}/rtems/version.cfg
>
> #
> # qemu common option patterns.
> #
> %define qemu_opts_base   -no-reboot -monitor none -serial stdio -nographic
> #%define qemu_opts_base   -no-reboot -serial null -serial mon:stdio
> -nographic
> #%define qemu_opts_base  -no-reboot -monitor null -serial stdio -nographic
> %define qemu_opts_no_net -net none
> #
> # qemu executable
> #
> %ifn %{defined bsp_qemu_opts}
>  %define bsp_qemu_opts %{nil}
> %endif
> %define qemu_cmd  qemu-system-%{bsp_arch}
> %define qemu_opts %{bsp_qemu_opts}
>
>
> #
> # 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 for %{bsp}"
> %endif
> %endif
>
> #
> # executable
> #
>
> #%execute %{qemu_cmd} %{qemu_opts} -kernel %{test_executable}
> %execute %{qemu_cmd} %{qemu_opts_base} %{qemu_opts} -kernel
> %{test_executable} %{coverage_arg}
>
>
> #%define qemu_opts_base -no-reboot -monitor none -serial stdio -nographic
> #%define qemu_opts_base -no-reboot -serial null -serial mon:stdio
> -nographic
> #%define qemu_opts_base -no-reboot -monitor null -serial stdio -nographic
>
>
>
>
>>
>>>
>>>
>>>
>>>

Re: error while running rtems-test with coverage

[Vijay Kumar Banerjee]

On 15 April 2018 at 14:02, Cillian O'Donnell  wrote:

>
>
> On 15 April 2018 at 06:46, Vijay Kumar Banerjee 
> wrote:
>
>>
>>
>> On 15 April 2018 at 01:45, Cillian O'Donnell 
>> wrote:
>>
>>> Switch one of these lines out in qemu.cfg.
>>>
>>> #%define qemu_opts_base -no-reboot -monitor none -serial stdio
>>> -nographic
>>> #%define qemu_opts_base -no-reboot -serial null -serial mon:stdio
>>> -nographic
>>> %define qemu_opts_base -no-reboot -monitor null -serial stdio -nographic
>>>
>>> Just comment out the one that's being used and uncomment one of the
>>> others. It should cause a complaint when the tests are run and the qemu cmd
>>> should show up in the log so we can take a look at it.
>>>
>>
>>
>> error: qemu.cfg:71: execute failed: qemu-system-sparc -no-reboot -monitor
>> null -serial stdio -nographic -no-reboot -monitor null -serial stdio
>> -nographic -M leon3_generic -kernel /home/lunatic/development/rtem
>> s/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/unlimited/unlimited.exe:
>> exit-code:1
>>
>> run: qemu-system-sparc -no-reboot -monitor null -serial stdio -nographic
>> -no-reboot -monitor null -serial stdio -nographic -M leon3_generic
>> -kernel /home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/
>> leon3/testsuites/samples/unlimited/unlimited.exe -exec-trace
>>  /home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/
>> c/leon3/testsuites/samples/unlimited/unlimited.exe.cov
>>
>
> Are those line breaks actually there or is it from the copy and paste.
> Like  unlimited. If so that's definitely the problem. What does your
> last section in qemu.cfg look like now? The execute section.
>
They are from copy paste .
I'm pasting the qemu.cfg here
.

#
# 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 permitted provided that the following conditions are
met:
#
# 1. Redistributions of source code must retain the above copyright notice,
# this list of conditions and the following disclaimer.
#
# 2. Redistributions in binary form must reproduce the above copyright
notice,
# this list of conditions and the following disclaimer in the documentation
# and/or other materials provided with the distribution.
#
# this software is provided by the copyright holders and contributors "as
is"
# and any express or implied warranties, including, but not limited to, the
# implied warranties of merchantability and fitness for a particular purpose
# are disclaimed. in no event shall the copyright holder or contributors be
# liable for any direct, indirect, incidental, special, exemplary, or
# consequential damages (including, but not limited to, procurement of
# substitute goods or services; loss of use, data, or profits; or business
# interruption) however caused and on any theory of liability, whether in
# contract, strict liability, or tort (including negligence or otherwise)
# arising in any way out of the use of this software, even if advised of the
# possibility of such damage.
#

#
# qemu
#
# use a qemu command to run the executable in the qemu simulator.
#

%include %{_configdir}/base.cfg
%include %{_configdir}/checks.cfg

#
# console.
#
%define console_stdio
%include %{_configdir}/console.cfg

#
# rtems version
#
%include %{_rtdir}/rtems/version.cfg

#
# qemu common option patterns.
#
%define qemu_opts_base   -no-reboot -monitor none -serial stdio -nographic
#%define qemu_opts_base   -no-reboot -serial null -serial mon:stdio
-nographic
#%define qemu_opts_base  -no-reboot -monitor null -serial stdio -nographic
%define qemu_opts_no_net -net none
#
# qemu executable
#
%ifn %{defined bsp_qemu_opts}
 %define bsp_qemu_opts %{nil}
%endif
%define qemu_cmd  qemu-system-%{bsp_arch}
%define qemu_opts %{bsp_qemu_opts}


#
# 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 for %{bsp}"
%endif
%endif

#
# executable
#

#%execute %{qemu_cmd} %{qemu_opts} -kernel %{test_executable}
%execute %{qemu_cmd} %{qemu_opts_base} %{qemu_opts} -kernel
%{test_executable} %{coverage_arg}


#%define qemu_opts_base -no-reboot -monitor none -serial stdio -nographic
#%define qemu_opts_base -no-reboot -serial null -serial mon:stdio -nographic
#%define qemu_opts_base -no-reboot -monitor null -serial stdio -nographic




>
>>
>>
>>
>>
>>>
>>> On 14 April 2018 at 20:37, Vijay Kumar Banerjee <
>>> vijaykumar9...@gmail.com> wrote:
>>>


 -- vijay

 On 15 April 2018 at 00:50, Vijay Kumar Banerjee <
 vijaykumar9...@gmail.com> wrote:

>
>
>
> On 14 April 2018 at 16:42, Cillian O'Donnell 
> wrote:
>
>>
>>
>> On 14 April 2018 at 07:11, Chris Johns  wrot

Re: error while running rtems-test with coverage

[Cillian O'Donnell]

On 15 April 2018 at 06:46, Vijay Kumar Banerjee 
wrote:

>
>
> On 15 April 2018 at 01:45, Cillian O'Donnell 
> wrote:
>
>> Switch one of these lines out in qemu.cfg.
>>
>> #%define qemu_opts_base -no-reboot -monitor none -serial stdio -nographic
>> #%define qemu_opts_base -no-reboot -serial null -serial mon:stdio
>> -nographic
>> %define qemu_opts_base -no-reboot -monitor null -serial stdio -nographic
>>
>> Just comment out the one that's being used and uncomment one of the
>> others. It should cause a complaint when the tests are run and the qemu cmd
>> should show up in the log so we can take a look at it.
>>
>
>
> error: qemu.cfg:71: execute failed: qemu-system-sparc -no-reboot -monitor
> null -serial stdio -nographic -no-reboot -monitor null -serial stdio
> -nographic -M leon3_generic -kernel /home/lunatic/development/
> rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/
> samples/unlimited/unlimited.exe: exit-code:1
>
> run: qemu-system-sparc -no-reboot -monitor null -serial stdio -nographic
> -no-reboot -monitor null -serial stdio -nographic -M leon3_generic
> -kernel /home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/
> leon3/testsuites/samples/unlimited/unlimited.exe -exec-trace
>  /home/lunatic/development/rtems/kernel/leon3/sparc-
> rtems5/c/leon3/testsuites/samples/unlimited/unlimited.exe.cov
>

Are those line breaks actually there or is it from the copy and paste.
Like  unlimited. If so that's definitely the problem. What does your
last section in qemu.cfg look like now? The execute section.

>
>
>
>
>
>>
>> On 14 April 2018 at 20:37, Vijay Kumar Banerjee > > wrote:
>>
>>>
>>>
>>> -- vijay
>>>
>>> On 15 April 2018 at 00:50, Vijay Kumar Banerjee <
>>> vijaykumar9...@gmail.com> wrote:
>>>



 On 14 April 2018 at 16:42, Cillian O'Donnell 
 wrote:

>
>
> On 14 April 2018 at 07:11, Chris Johns  wrote:
>
>> On 14/4/18 8:02 am, Vijay Kumar Banerjee wrote:
>>
>>> 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 
>>> "/home/lunatic/development/rtems/test/rtems-tools/tester/rt/test.py",
>>> line 353, in run
>>>  tst.reraise()
>>>File 
>>> "/home/lunatic/development/rtems/test/rtems-tools/tester/rt/test.py",
>>> line 160, in reraise
>>>  _test_reraise(*self.result)
>>> NameError: global name '_test_reraise' is not defined
>>>
>>>
>> The reraise logic was moved to the rtemstoolkit last year:
>>
>> https://git.rtems.org/rtems-tools/commit/?id=fa81491764861e6
>> 3785a3faa241c488469087209
>>
>> It had some issues that have been fixed and it is being reused else
>> where in the tester.
>>
>>
>>> -- vijay
>>>
>>> On 13 April 2018 at 23:57, Vijay Kumar Banerjee <
>>> vijaykumar9...@gmail.com > wrote:
>>>
>>>
>>>
>>> On 13 April 2018 at 23:51, Cillian O'Donnell <
>>> cpodonne...@gmail.com
>>> > 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 isn't run and there's no .cov
>>> files in
>>> the end. So that's what you'll have to dig into.
>>>
>>> Okay , I'll set it to global then.
>>>
>>>
>> Changes need to be on the latest version of master before I will
>> review them. The failure above indicate the code you have is not up to 
>> date.
>>
>
> Yes that was the plan. Just to check Vijay your starting point was
> using the ini-update branch from here?
>
> https://github.com/cillianodonnell/rtems-tools/tree/ini-update
>
> That branch is current rtems-tools master that I started to add things
> back in. The only reraise in there is the one improrted from rtemstoolkit.
>

 yes this is the branch I'm using , I checked the reraise error , not
 sure how it showed up buit I called it from the reraise module , and
 it got fixed . now I'm stuck here

 error: config error: qemu.cfg:36: No 'target' defined

>>>
>>> okay , fixed that .
>>> still getting the warnings of the unable to read .cov
>>>

 are we supposed to set the bsp to global as well ?


>> The change you have made is generating an exception in the tester
>> thread. If you want to continue down this path you will need to fix what
>> ever you have added.
>>
>> The test

Re: error while running rtems-test with coverage

[Vijay Kumar Banerjee]

On 15 April 2018 at 01:45, Cillian O'Donnell  wrote:

> Switch one of these lines out in qemu.cfg.
>
> #%define qemu_opts_base -no-reboot -monitor none -serial stdio -nographic
> #%define qemu_opts_base -no-reboot -serial null -serial mon:stdio
> -nographic
> %define qemu_opts_base -no-reboot -monitor null -serial stdio -nographic
>
> Just comment out the one that's being used and uncomment one of the
> others. It should cause a complaint when the tests are run and the qemu cmd
> should show up in the log so we can take a look at it.
>


error: qemu.cfg:71: execute failed: qemu-system-sparc -no-reboot -monitor
null -serial stdio -nographic -no-reboot -monitor null -serial stdio
-nographic -M leon3_generic -kernel
/home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/unlimited/unlimited.exe:
exit-code:1

run: qemu-system-sparc -no-reboot -monitor null -serial stdio -nographic
-no-reboot -monitor null -serial stdio -nographic -M leon3_generic
-kernel /home/lunatic/development/rtem
s/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/unlimited/unlimited.exe
-exec-trace
 
/home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/unlimi
  ted/unlimited.exe.cov





>
> On 14 April 2018 at 20:37, Vijay Kumar Banerjee 
> wrote:
>
>>
>>
>> -- vijay
>>
>> On 15 April 2018 at 00:50, Vijay Kumar Banerjee > > wrote:
>>
>>>
>>>
>>>
>>> On 14 April 2018 at 16:42, Cillian O'Donnell 
>>> wrote:
>>>


 On 14 April 2018 at 07:11, Chris Johns  wrote:

> On 14/4/18 8:02 am, Vijay Kumar Banerjee wrote:
>
>> 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 
>> "/home/lunatic/development/rtems/test/rtems-tools/tester/rt/test.py",
>> line 353, in run
>>  tst.reraise()
>>File 
>> "/home/lunatic/development/rtems/test/rtems-tools/tester/rt/test.py",
>> line 160, in reraise
>>  _test_reraise(*self.result)
>> NameError: global name '_test_reraise' is not defined
>>
>>
> The reraise logic was moved to the rtemstoolkit last year:
>
> https://git.rtems.org/rtems-tools/commit/?id=fa81491764861e6
> 3785a3faa241c488469087209
>
> It had some issues that have been fixed and it is being reused else
> where in the tester.
>
>
>> -- vijay
>>
>> On 13 April 2018 at 23:57, Vijay Kumar Banerjee <
>> vijaykumar9...@gmail.com > wrote:
>>
>>
>>
>> On 13 April 2018 at 23:51, Cillian O'Donnell <
>> cpodonne...@gmail.com
>> > 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 isn't run and there's no .cov files
>> in
>> the end. So that's what you'll have to dig into.
>>
>> Okay , I'll set it to global then.
>>
>>
> Changes need to be on the latest version of master before I will
> review them. The failure above indicate the code you have is not up to 
> date.
>

 Yes that was the plan. Just to check Vijay your starting point was
 using the ini-update branch from here?

 https://github.com/cillianodonnell/rtems-tools/tree/ini-update

 That branch is current rtems-tools master that I started to add things
 back in. The only reraise in there is the one improrted from rtemstoolkit.

>>>
>>> yes this is the branch I'm using , I checked the reraise error , not
>>> sure how it showed up buit I called it from the reraise module , and it
>>> got fixed . now I'm stuck here
>>>
>>> error: config error: qemu.cfg:36: No 'target' defined
>>>
>>
>> okay , fixed that .
>> still getting the warnings of the unable to read .cov
>>
>>>
>>> are we supposed to set the bsp to global as well ?
>>>
>>>
> The change you have made is generating an exception in the tester
> thread. If you want to continue down this path you will need to fix what
> ever you have added.
>
> The tests are run as threads separate from the main thread so the
> exception is caught and re-raised in the main thread letting you know. 
> This
> is broken in the old code base you are using.
>
> Why not investigate the reason as indicated and sort if out what the
> new format configuration file needs?
>
> Chris
>


>>>
>>
>
___
devel mailing list
devel@rtems.org
http://lists.rtem

Re: error while running rtems-test with coverage

[Cillian O'Donnell]

Switch one of these lines out in qemu.cfg.

#%define qemu_opts_base -no-reboot -monitor none -serial stdio -nographic
#%define qemu_opts_base -no-reboot -serial null -serial mon:stdio -nographic
%define qemu_opts_base -no-reboot -monitor null -serial stdio -nographic

Just comment out the one that's being used and uncomment one of the others.
It should cause a complaint when the tests are run and the qemu cmd should
show up in the log so we can take a look at it.

On 14 April 2018 at 20:37, Vijay Kumar Banerjee 
wrote:

>
>
> -- vijay
>
> On 15 April 2018 at 00:50, Vijay Kumar Banerjee 
> wrote:
>
>>
>>
>>
>> On 14 April 2018 at 16:42, Cillian O'Donnell 
>> wrote:
>>
>>>
>>>
>>> On 14 April 2018 at 07:11, Chris Johns  wrote:
>>>
 On 14/4/18 8:02 am, Vijay Kumar Banerjee wrote:

> 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 
> "/home/lunatic/development/rtems/test/rtems-tools/tester/rt/test.py",
> line 353, in run
>  tst.reraise()
>File 
> "/home/lunatic/development/rtems/test/rtems-tools/tester/rt/test.py",
> line 160, in reraise
>  _test_reraise(*self.result)
> NameError: global name '_test_reraise' is not defined
>
>
 The reraise logic was moved to the rtemstoolkit last year:

 https://git.rtems.org/rtems-tools/commit/?id=fa81491764861e6
 3785a3faa241c488469087209

 It had some issues that have been fixed and it is being reused else
 where in the tester.


> -- vijay
>
> On 13 April 2018 at 23:57, Vijay Kumar Banerjee <
> vijaykumar9...@gmail.com > wrote:
>
>
>
> On 13 April 2018 at 23:51, Cillian O'Donnell <
> cpodonne...@gmail.com
> > 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 isn't run and there's no .cov files
> in
> the end. So that's what you'll have to dig into.
>
> Okay , I'll set it to global then.
>
>
 Changes need to be on the latest version of master before I will review
 them. The failure above indicate the code you have is not up to date.

>>>
>>> Yes that was the plan. Just to check Vijay your starting point was using
>>> the ini-update branch from here?
>>>
>>> https://github.com/cillianodonnell/rtems-tools/tree/ini-update
>>>
>>> That branch is current rtems-tools master that I started to add things
>>> back in. The only reraise in there is the one improrted from rtemstoolkit.
>>>
>>
>> yes this is the branch I'm using , I checked the reraise error , not
>> sure how it showed up buit I called it from the reraise module , and it
>> got fixed . now I'm stuck here
>>
>> error: config error: qemu.cfg:36: No 'target' defined
>>
>
> okay , fixed that .
> still getting the warnings of the unable to read .cov
>
>>
>> are we supposed to set the bsp to global as well ?
>>
>>
 The change you have made is generating an exception in the tester
 thread. If you want to continue down this path you will need to fix what
 ever you have added.

 The tests are run as threads separate from the main thread so the
 exception is caught and re-raised in the main thread letting you know. This
 is broken in the old code base you are using.

 Why not investigate the reason as indicated and sort if out what the
 new format configuration file needs?

 Chris

>>>
>>>
>>
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: error while running rtems-test with coverage

[Vijay Kumar Banerjee]

-- vijay

On 15 April 2018 at 00:50, Vijay Kumar Banerjee 
wrote:

>
>
>
> On 14 April 2018 at 16:42, Cillian O'Donnell 
> wrote:
>
>>
>>
>> On 14 April 2018 at 07:11, Chris Johns  wrote:
>>
>>> On 14/4/18 8:02 am, Vijay Kumar Banerjee wrote:
>>>
 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 
 "/home/lunatic/development/rtems/test/rtems-tools/tester/rt/test.py",
 line 353, in run
  tst.reraise()
File 
 "/home/lunatic/development/rtems/test/rtems-tools/tester/rt/test.py",
 line 160, in reraise
  _test_reraise(*self.result)
 NameError: global name '_test_reraise' is not defined


>>> The reraise logic was moved to the rtemstoolkit last year:
>>>
>>> https://git.rtems.org/rtems-tools/commit/?id=fa81491764861e6
>>> 3785a3faa241c488469087209
>>>
>>> It had some issues that have been fixed and it is being reused else
>>> where in the tester.
>>>
>>>
 -- vijay

 On 13 April 2018 at 23:57, Vijay Kumar Banerjee <
 vijaykumar9...@gmail.com > wrote:



 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 isn't run and there's no .cov files in
 the end. So that's what you'll have to dig into.

 Okay , I'll set it to global then.


>>> Changes need to be on the latest version of master before I will review
>>> them. The failure above indicate the code you have is not up to date.
>>>
>>
>> Yes that was the plan. Just to check Vijay your starting point was using
>> the ini-update branch from here?
>>
>> https://github.com/cillianodonnell/rtems-tools/tree/ini-update
>>
>> That branch is current rtems-tools master that I started to add things
>> back in. The only reraise in there is the one improrted from rtemstoolkit.
>>
>
> yes this is the branch I'm using , I checked the reraise error , not sure
> how it showed up buit I called it from the reraise module , and it got
> fixed . now I'm stuck here
>
> error: config error: qemu.cfg:36: No 'target' defined
>

okay , fixed that .
still getting the warnings of the unable to read .cov

>
> are we supposed to set the bsp to global as well ?
>
>
>>> The change you have made is generating an exception in the tester
>>> thread. If you want to continue down this path you will need to fix what
>>> ever you have added.
>>>
>>> The tests are run as threads separate from the main thread so the
>>> exception is caught and re-raised in the main thread letting you know. This
>>> is broken in the old code base you are using.
>>>
>>> Why not investigate the reason as indicated and sort if out what the new
>>> format configuration file needs?
>>>
>>> Chris
>>>
>>
>>
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: error while running rtems-test with coverage

[Vijay Kumar Banerjee]

On 14 April 2018 at 16:42, Cillian O'Donnell  wrote:

>
>
> On 14 April 2018 at 07:11, Chris Johns  wrote:
>
>> On 14/4/18 8:02 am, Vijay Kumar Banerjee wrote:
>>
>>> 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 
>>> "/home/lunatic/development/rtems/test/rtems-tools/tester/rt/test.py",
>>> line 353, in run
>>>  tst.reraise()
>>>File 
>>> "/home/lunatic/development/rtems/test/rtems-tools/tester/rt/test.py",
>>> line 160, in reraise
>>>  _test_reraise(*self.result)
>>> NameError: global name '_test_reraise' is not defined
>>>
>>>
>> The reraise logic was moved to the rtemstoolkit last year:
>>
>> https://git.rtems.org/rtems-tools/commit/?id=fa81491764861e6
>> 3785a3faa241c488469087209
>>
>> It had some issues that have been fixed and it is being reused else where
>> in the tester.
>>
>>
>>> -- vijay
>>>
>>> On 13 April 2018 at 23:57, Vijay Kumar Banerjee <
>>> vijaykumar9...@gmail.com > wrote:
>>>
>>>
>>>
>>> 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 isn't run and there's no .cov files in
>>> the end. So that's what you'll have to dig into.
>>>
>>> Okay , I'll set it to global then.
>>>
>>>
>> Changes need to be on the latest version of master before I will review
>> them. The failure above indicate the code you have is not up to date.
>>
>
> Yes that was the plan. Just to check Vijay your starting point was using
> the ini-update branch from here?
>
> https://github.com/cillianodonnell/rtems-tools/tree/ini-update
>
> That branch is current rtems-tools master that I started to add things
> back in. The only reraise in there is the one improrted from rtemstoolkit.
>

yes this is the branch I'm using , I checked the reraise error , not sure
how it showed up buit I called it from the reraise module , and it got
fixed . now I'm stuck here

error: config error: qemu.cfg:36: No 'target' defined

are we supposed to set the bsp to global as well ?


>> The change you have made is generating an exception in the tester thread.
>> If you want to continue down this path you will need to fix what ever you
>> have added.
>>
>> The tests are run as threads separate from the main thread so the
>> exception is caught and re-raised in the main thread letting you know. This
>> is broken in the old code base you are using.
>>
>> Why not investigate the reason as indicated and sort if out what the new
>> format configuration file needs?
>>
>> Chris
>>
>
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: error while running rtems-test with coverage

[Cillian O'Donnell]

On 14 April 2018 at 07:11, Chris Johns  wrote:

> On 14/4/18 8:02 am, Vijay Kumar Banerjee wrote:
>
>> 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 "/home/lunatic/development/rtems/test/rtems-tools/tester/rt/test.py",
>> line 353, in run
>>  tst.reraise()
>>File "/home/lunatic/development/rtems/test/rtems-tools/tester/rt/test.py",
>> line 160, in reraise
>>  _test_reraise(*self.result)
>> NameError: global name '_test_reraise' is not defined
>>
>>
> The reraise logic was moved to the rtemstoolkit last year:
>
> https://git.rtems.org/rtems-tools/commit/?id=fa81491764861e6
> 3785a3faa241c488469087209
>
> It had some issues that have been fixed and it is being reused else where
> in the tester.
>
>
>> -- vijay
>>
>> On 13 April 2018 at 23:57, Vijay Kumar Banerjee > > wrote:
>>
>>
>>
>> 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 isn't run and there's no .cov files in
>> the end. So that's what you'll have to dig into.
>>
>> Okay , I'll set it to global then.
>>
>>
> Changes need to be on the latest version of master before I will review
> them. The failure above indicate the code you have is not up to date.
>

Yes that was the plan. Just to check Vijay your starting point was using
the ini-update branch from here?

https://github.com/cillianodonnell/rtems-tools/tree/ini-update

That branch is current rtems-tools master that I started to add things back
in. The only reraise in there is the one improrted from rtemstoolkit.

>
> The change you have made is generating an exception in the tester thread.
> If you want to continue down this path you will need to fix what ever you
> have added.
>
> The tests are run as threads separate from the main thread so the
> exception is caught and re-raised in the main thread letting you know. This
> is broken in the old code base you are using.
>
> Why not investigate the reason as indicated and sort if out what the new
> format configuration file needs?
>
> Chris
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: error while running rtems-test with coverage

[Chris Johns]

On 14/4/18 8:02 am, Vijay Kumar Banerjee wrote:

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 
"/home/lunatic/development/rtems/test/rtems-tools/tester/rt/test.py", 
line 353, in run

     tst.reraise()
   File 
"/home/lunatic/development/rtems/test/rtems-tools/tester/rt/test.py", 
line 160, in reraise

     _test_reraise(*self.result)
NameError: global name '_test_reraise' is not defined



The reraise logic was moved to the rtemstoolkit last year:

https://git.rtems.org/rtems-tools/commit/?id=fa81491764861e63785a3faa241c488469087209

It had some issues that have been fixed and it is being reused else 
where in the tester.




-- vijay

On 13 April 2018 at 23:57, Vijay Kumar Banerjee 
mailto:vijaykumar9...@gmail.com>> wrote:




On 13 April 2018 at 23:51, Cillian O'Donnell mailto:cpodonne...@gmail.com>> 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 isn't run and there's no .cov files in
the end. So that's what you'll have to dig into.

Okay , I'll set it to global then.



Changes need to be on the latest version of master before I will review 
them. The failure above indicate the code you have is not up to date.


The change you have made is generating an exception in the tester 
thread. If you want to continue down this path you will need to fix what 
ever you have added.


The tests are run as threads separate from the main thread so the 
exception is caught and re-raised in the main thread letting you know. 
This is broken in the old code base you are using.


Why not investigate the reason as indicated and sort if out what the new 
format configuration file needs?


Chris
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: error while running rtems-test with coverage

[Vijay Kumar Banerjee]

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
"/home/lunatic/development/rtems/test/rtems-tools/tester/rt/test.py", line
353, in run
tst.reraise()
  File
"/home/lunatic/development/rtems/test/rtems-tools/tester/rt/test.py", line
160, in reraise
_test_reraise(*self.result)
NameError: global name '_test_reraise' is not defined


-- vijay

On 13 April 2018 at 23:57, Vijay Kumar Banerjee 
wrote:

>
>
> 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 isn't run
>> and there's no .cov files in the end. So that's what you'll have to dig
>> into.
>>
> Okay , I'll set it to global then.
>
>>
>> On Fri, 13 Apr 2018, 19:16 Vijay Kumar Banerjee, <
>> vijaykumar9...@gmail.com> wrote:
>>
>>> It just shows this.(with only hello)
>>>
>>> Running covoar for score
>>> WARNING: Unable to read coverage file /home/lunatic/development/rtem
>>> s/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
>>>
>>> 
>>> The log file shows this
>>> ..
>>> RTEMS Testing - Tester, 5 (58acb6d61ac7 modified)
>>>   2  Command Line: /home/lunatic/development/rtem
>>> s/test/rtems-tools/tester/rtems-test --rtems-t
>>> ools=/home/lunatic/development/rtems/5 --log=coverage_analysis.log
>>> --rtems-bsp=leon3_qemu --coverage --rtems-builddir=/home/lunatic
>>> /development/rtems/kernel/leon3 sparc-rtems5/c/leon
>>> 3/testsuites/samples/hello
>>>   3  Python: 2.7.14 (default, Feb 27 2018, 20:43:24) [GCC 7.3.1 20180130
>>> (Red Hat 7.3.1-2)]
>>>   4 Host: Linux-4.15.8-300.fc27.x86_64-x86_64-with-fedora-27-Twenty_Seven
>>> (Linux lunatic 4.15.8-300.fc27.x86_64 #1 SMP Fri Mar 9 18:11:36 UTC
>>> 2018 x86_64 x86_64)
>>>   5 Coverage environment prepared
>>>   6 [1/1] p:0 f:0 u:0 e:0 I:0 B:0 t:0 i:0 W:0 | sparc/leon3_qemu:
>>> hello.exe
>>>   7
>>>   8 Passed:1
>>>   9 Failed:0
>>>  10 User Input:0
>>>  11 Expected Fail: 0
>>>  12 Indeterminate: 0
>>>  13 Benchmark: 0
>>>  14 Timeout:   0
>>>  15 Invalid:   0
>>>  16 Wrong Version: 0
>>>  17 Wrong Build:   0
>>>  18 Wrong Tools:   0
>>>  19 
>>>  20 Total: 1
>>>  21
>>>  22 Average test time: 0:00:01.505199
>>>  23 Testing time : 0:00:01.505199
>>>  24 Running covoar for score
>>>  25 shell: covoar -s /home/lunatic/coverage_test/coverage/score.symcfg
>>> -O /home/lunatic/coverage_test/test/score -f QEMU -T sparc-rtems5 -E
>>> /home/lunatic/development/rtems/test/rtems-too
>>> ls/tester/rtems/testing/coverage/Explanations.txt -c .cov -e exe -p
>>> RTEMS-5 /home/lunatic/development/rtems/kernel/leon3/
>>> sparc-rtems5/c/leon3/testsuites/samples/hello/hello.exe
>>>  26 WARNING: Unable to read coverage file 
>>> /home/lunatic/development/rtems/kernel/leon3/sparc-rt
>>>   ems5/c/leon3/testsuites/samples/hello/hello.exe.cov
>>>
>>>  1,1   Top
>>>
>>>
>>> -- vijay
>>>
>>> On 13 April 2018 at 23:40, Cillian O'Donnell 
>>> wrote:
>>>
 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, <
 vijaykumar9...@gmail.com> wrote:

>
> -- 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, <
>> vijaykumar9...@gmail.com> wrote:
>>
>>> can we set it in [coverage] ?
>>>
>>> It runs with the same warnings of unable to read the .cov files
>
>
>> -- 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 variable set in the new 
 leon3-qemu.ini

 Heres the old version from the .MC file

 [global]
 bsp:  none,none, 'leon3'
 coverage_supported:   none,none, '1'


 On Fri, 13 Apr 2018, 18:29 Vijay Kumar Banerjee, <
 vijaykumar9...@gmail.com> wrote:

> It shows the following error
>
> ...
> RTEMS

Re: error while running rtems-test with coverage

[Vijay Kumar Banerjee]

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 isn't run
> and there's no .cov files in the end. So that's what you'll have to dig
> into.
>
Okay , I'll set it to global then.

>
> On Fri, 13 Apr 2018, 19:16 Vijay Kumar Banerjee, 
> wrote:
>
>> 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
>>
>> 
>> The log file shows this
>> ..
>> RTEMS Testing - Tester, 5 (58acb6d61ac7 modified)
>>   2  Command Line: /home/lunatic/development/
>> rtems/test/rtems-tools/tester/rtems-test --rtems-t
>> ools=/home/lunatic/development/rtems/5
>> --log=coverage_analysis.log --rtems-bsp=leon3_qemu --coverage
>> --rtems-builddir=/home/lunatic/development/rtems/kernel/leon3
>> sparc-rtems5/c/leon3/testsuites/samples/hello
>>   3  Python: 2.7.14 (default, Feb 27 2018, 20:43:24) [GCC 7.3.1 20180130
>> (Red Hat 7.3.1-2)]
>>   4 Host: Linux-4.15.8-300.fc27.x86_64-x86_64-with-fedora-27-Twenty_Seven
>> (Linux lunatic 4.15.8-300.fc27.x86_64 #1 SMP Fri Mar 9 18:11:36 UTC
>> 2018 x86_64 x86_64)
>>   5 Coverage environment prepared
>>   6 [1/1] p:0 f:0 u:0 e:0 I:0 B:0 t:0 i:0 W:0 | sparc/leon3_qemu:
>> hello.exe
>>   7
>>   8 Passed:1
>>   9 Failed:0
>>  10 User Input:0
>>  11 Expected Fail: 0
>>  12 Indeterminate: 0
>>  13 Benchmark: 0
>>  14 Timeout:   0
>>  15 Invalid:   0
>>  16 Wrong Version: 0
>>  17 Wrong Build:   0
>>  18 Wrong Tools:   0
>>  19 
>>  20 Total: 1
>>  21
>>  22 Average test time: 0:00:01.505199
>>  23 Testing time : 0:00:01.505199
>>  24 Running covoar for score
>>  25 shell: covoar -s /home/lunatic/coverage_test/coverage/score.symcfg
>> -O /home/lunatic/coverage_test/test/score -f QEMU -T sparc-rtems5 -E
>> /home/lunatic/development/rtems/test/rtems-too
>> ls/tester/rtems/testing/coverage/Explanations.txt -c .cov -e exe -p
>> RTEMS-5 /home/lunatic/development/rtems/kernel/leon3/
>> sparc-rtems5/c/leon3/testsuites/samples/hello/hello.exe
>>  26 WARNING: Unable to read coverage file 
>> /home/lunatic/development/rtems/kernel/leon3/sparc-rt
>>   ems5/c/leon3/testsuites/samples/hello/hello.exe.cov
>>
>>1,1   Top
>>
>>
>> -- vijay
>>
>> On 13 April 2018 at 23:40, Cillian O'Donnell 
>> wrote:
>>
>>> 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, <
>>> vijaykumar9...@gmail.com> wrote:
>>>

 -- 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, <
> vijaykumar9...@gmail.com> wrote:
>
>> can we set it in [coverage] ?
>>
>> It runs with the same warnings of unable to read the .cov files


> -- 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 variable set in the new 
>>> leon3-qemu.ini
>>>
>>> Heres the old version from the .MC file
>>>
>>> [global]
>>> bsp:  none,none, 'leon3'
>>> coverage_supported:   none,none, '1'
>>>
>>>
>>> On Fri, 13 Apr 2018, 18:29 Vijay Kumar Banerjee, <
>>> vijaykumar9...@gmail.com> wrote:
>>>
 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  f:0  u:0  e:0  I:0  B:0  t:0  i:0  W:0  |
 sparc/leon3_qemu: capture.exe
 [ 4/13] p:0  f:0  u:0  e:0  I:0  B:0  t:0  i:0  W:0  |
 sparc/leon3_qemu: fileio.exe
 error: qemu.cfg:77: macro '%{coverage_supported}' not found
 warning: switched to dry run due to errors
 error: qemu.cfg:77: invalid if bool value:  %if
 %{coverage_supported}
 error: qemu.cfg:77: macro '%{coverage_supported}' not found
 warning: switched to dry run due

Re: error while running rtems-test with coverage

[Cillian O'Donnell]

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
into.

On Fri, 13 Apr 2018, 19:16 Vijay Kumar Banerjee, 
wrote:

> 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
>
> 
> The log file shows this
> ..
> RTEMS Testing - Tester, 5 (58acb6d61ac7 modified)
>   2  Command Line:
> /home/lunatic/development/rtems/test/rtems-tools/tester/rtems-test
> --rtems-tools=/home/lunatic/development/rtems/5
> --log=coverage_analysis.log --rtems-bsp=leon3_qemu --coverage
> --rtems-builddir=/home/lunatic/development/rtems/kernel/leon3
> sparc-rtems5/c/leon3/testsuites/samples/hello
>   3  Python: 2.7.14 (default, Feb 27 2018, 20:43:24) [GCC 7.3.1 20180130
> (Red Hat 7.3.1-2)]
>   4 Host: Linux-4.15.8-300.fc27.x86_64-x86_64-with-fedora-27-Twenty_Seven
> (Linux lunatic 4.15.8-300.fc27.x86_64 #1 SMP Fri Mar 9 18:11:36 UTC
> 2018 x86_64 x86_64)
>   5 Coverage environment prepared
>   6 [1/1] p:0 f:0 u:0 e:0 I:0 B:0 t:0 i:0 W:0 | sparc/leon3_qemu: hello.exe
>   7
>   8 Passed:1
>   9 Failed:0
>  10 User Input:0
>  11 Expected Fail: 0
>  12 Indeterminate: 0
>  13 Benchmark: 0
>  14 Timeout:   0
>  15 Invalid:   0
>  16 Wrong Version: 0
>  17 Wrong Build:   0
>  18 Wrong Tools:   0
>  19 
>  20 Total: 1
>  21
>  22 Average test time: 0:00:01.505199
>  23 Testing time : 0:00:01.505199
>  24 Running covoar for score
>  25 shell: covoar -s /home/lunatic/coverage_test/coverage/score.symcfg -O
> /home/lunatic/coverage_test/test/score -f QEMU -T sparc-rtems5 -E
> /home/lunatic/development/rtems/test/rtems-too
> ls/tester/rtems/testing/coverage/Explanations.txt -c .cov -e exe -p RTEMS-5
> /home/lunatic/d
> evelopment/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/hello/hello.exe
>  26 WARNING: Unable to read coverage file
> /home/lunatic/development/rtems/kernel/leon3/sparc-rt
> ems5/c/leon3/testsuites/samples/hello/hello.exe.cov
>
>1,1   Top
>
>
> -- vijay
>
> On 13 April 2018 at 23:40, Cillian O'Donnell 
> wrote:
>
>> 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, <
>> vijaykumar9...@gmail.com> wrote:
>>
>>>
>>> -- 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, <
 vijaykumar9...@gmail.com> wrote:

> can we set it in [coverage] ?
>
> It runs with the same warnings of unable to read the .cov files
>>>
>>>
 -- 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 variable set in the new leon3-qemu.ini
>>
>> Heres the old version from the .MC file
>>
>> [global]
>> bsp:  none,none, 'leon3'
>> coverage_supported:   none,none, '1'
>>
>>
>> On Fri, 13 Apr 2018, 18:29 Vijay Kumar Banerjee, <
>> vijaykumar9...@gmail.com> wrote:
>>
>>> 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  f:0  u:0  e:0  I:0  B:0  t:0  i:0  W:0  |
>>> sparc/leon3_qemu: capture.exe
>>> [ 4/13] p:0  f:0  u:0  e:0  I:0  B:0  t:0  i:0  W:0  |
>>> sparc/leon3_qemu: fileio.exe
>>> error: qemu.cfg:77: macro '%{coverage_supported}' not found
>>> warning: switched to dry run due to errors
>>> error: qemu.cfg:77: invalid if bool value:  %if %{coverage_supported}
>>> error: qemu.cfg:77: macro '%{coverage_supported}' not found
>>> warning: switched to dry run due to errors
>>> error: qemu.cfg:77: invalid if bool value:  %if %{coverage_supported}
>>> Traceback (most recent call last):
>>>   File
>>> "/home/lunatic/development/rtems/test/rtems-tools/tester/rtems-test", 
>>> line
>>> 40, in 
>>> rt.tes

Re: error while running rtems-test with coverage

[Vijay Kumar Banerjee]

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


The log file shows this
..
RTEMS Testing - Tester, 5 (58acb6d61ac7 modified)
  2  Command Line:
/home/lunatic/development/rtems/test/rtems-tools/tester/rtems-test
--rtems-tools=/home/lunatic/development/rtems/5
--log=coverage_analysis.log --rtems-bsp=leon3_qemu --coverage
--rtems-builddir=/home/lunatic/development/rtems/kernel/leon3
sparc-rtems5/c/leon3/testsuites/samples/hello
  3  Python: 2.7.14 (default, Feb 27 2018, 20:43:24) [GCC 7.3.1 20180130
(Red Hat 7.3.1-2)]
  4 Host: Linux-4.15.8-300.fc27.x86_64-x86_64-with-fedora-27-Twenty_Seven
(Linux lunatic 4.15.8-300.fc27.x86_64 #1 SMP Fri Mar 9 18:11:36 UTC
2018 x86_64 x86_64)
  5 Coverage environment prepared
  6 [1/1] p:0 f:0 u:0 e:0 I:0 B:0 t:0 i:0 W:0 | sparc/leon3_qemu: hello.exe
  7
  8 Passed:1
  9 Failed:0
 10 User Input:0
 11 Expected Fail: 0
 12 Indeterminate: 0
 13 Benchmark: 0
 14 Timeout:   0
 15 Invalid:   0
 16 Wrong Version: 0
 17 Wrong Build:   0
 18 Wrong Tools:   0
 19 
 20 Total: 1
 21
 22 Average test time: 0:00:01.505199
 23 Testing time : 0:00:01.505199
 24 Running covoar for score
 25 shell: covoar -s /home/lunatic/coverage_test/coverage/score.symcfg -O
/home/lunatic/coverage_test/test/score -f QEMU -T sparc-rtems5 -E
/home/lunatic/development/rtems/test/rtems-too
ls/tester/rtems/testing/coverage/Explanations.txt -c .cov -e exe -p RTEMS-5
/home/lunatic/d
evelopment/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/hello/hello.exe
 26 WARNING: Unable to read coverage file
/home/lunatic/development/rtems/kernel/leon3/sparc-rt
ems5/c/leon3/testsuites/samples/hello/hello.exe.cov

 1,1   Top


-- vijay

On 13 April 2018 at 23:40, Cillian O'Donnell  wrote:

> 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 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, <
>>> vijaykumar9...@gmail.com> wrote:
>>>
 can we set it in [coverage] ?

 It runs with the same warnings of unable to read the .cov files
>>
>>
>>> -- 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 variable set in the new leon3-qemu.ini
>
> Heres the old version from the .MC file
>
> [global]
> bsp:  none,none, 'leon3'
> coverage_supported:   none,none, '1'
>
>
> On Fri, 13 Apr 2018, 18:29 Vijay Kumar Banerjee, <
> vijaykumar9...@gmail.com> wrote:
>
>> 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  f:0  u:0  e:0  I:0  B:0  t:0  i:0  W:0  |
>> sparc/leon3_qemu: capture.exe
>> [ 4/13] p:0  f:0  u:0  e:0  I:0  B:0  t:0  i:0  W:0  |
>> sparc/leon3_qemu: fileio.exe
>> error: qemu.cfg:77: macro '%{coverage_supported}' not found
>> warning: switched to dry run due to errors
>> error: qemu.cfg:77: invalid if bool value:  %if %{coverage_supported}
>> error: qemu.cfg:77: macro '%{coverage_supported}' not found
>> warning: switched to dry run due to errors
>> error: qemu.cfg:77: invalid if bool value:  %if %{coverage_supported}
>> Traceback (most recent call last):
>>   File 
>> "/home/lunatic/development/rtems/test/rtems-tools/tester/rtems-test",
>> line 40, in 
>> rt.test.run()
>>   File 
>> "/home/lunatic/development/rtems/test/rtems-tools/tester/rt/test.py",
>> line 353, in run
>> tst.reraise()
>>   File 
>> "/home/lunatic/development/rtems/test/rtems-tools/tester/rt/test.py",
>> line 160, in reraise
>> _test_reraise(*self.result)
>> NameError: global name '_test_reraise' is not defined
>> error: qemu.cfg:77: macro '%{coverage_supported}' not found
>> warning: switched to dry run due to errors
>> error: qemu.cfg:77: invalid if bool value:  %if %{coverage_supported}
>> error: qem

Re: error while running rtems-test with coverage

[Cillian O'Donnell]

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 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, <
>> vijaykumar9...@gmail.com> wrote:
>>
>>> can we set it in [coverage] ?
>>>
>>> It runs with the same warnings of unable to read the .cov files
>
>
>> -- 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 variable set in the new leon3-qemu.ini

 Heres the old version from the .MC file

 [global]
 bsp:  none,none, 'leon3'
 coverage_supported:   none,none, '1'


 On Fri, 13 Apr 2018, 18:29 Vijay Kumar Banerjee, <
 vijaykumar9...@gmail.com> wrote:

> 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  f:0  u:0  e:0  I:0  B:0  t:0  i:0  W:0  |
> sparc/leon3_qemu: capture.exe
> [ 4/13] p:0  f:0  u:0  e:0  I:0  B:0  t:0  i:0  W:0  |
> sparc/leon3_qemu: fileio.exe
> error: qemu.cfg:77: macro '%{coverage_supported}' not found
> warning: switched to dry run due to errors
> error: qemu.cfg:77: invalid if bool value:  %if %{coverage_supported}
> error: qemu.cfg:77: macro '%{coverage_supported}' not found
> warning: switched to dry run due to errors
> error: qemu.cfg:77: invalid if bool value:  %if %{coverage_supported}
> Traceback (most recent call last):
>   File
> "/home/lunatic/development/rtems/test/rtems-tools/tester/rtems-test", line
> 40, in 
> rt.test.run()
>   File
> "/home/lunatic/development/rtems/test/rtems-tools/tester/rt/test.py", line
> 353, in run
> tst.reraise()
>   File
> "/home/lunatic/development/rtems/test/rtems-tools/tester/rt/test.py", line
> 160, in reraise
> _test_reraise(*self.result)
> NameError: global name '_test_reraise' is not defined
> error: qemu.cfg:77: macro '%{coverage_supported}' not found
> warning: switched to dry run due to errors
> error: qemu.cfg:77: invalid if bool value:  %if %{coverage_supported}
> error: qemu.cfg:77: macro '%{coverage_supported}' not found
> warning: switched to dry run due to errors
> error: qemu.cfg:77: invalid if bool value:  %if %{coverage_supported}
>
>
>
> -- vijay
>
> On 13 April 2018 at 22:54, Cillian O'Donnell 
> wrote:
>
>> 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 for %{bsp}"
>> %endif
>> %endif
>>
>> #
>> # Executable
>> #
>> %execute %{qemu_cmd} %{qemu_opts_base} %{qemu_opts} -kernel 
>> %{test_executable} %{coverage_arg}
>>
>>
>> On Fri, 13 Apr 2018, 18:18 Vijay Kumar Banerjee, <
>> vijaykumar9...@gmail.com> wrote:
>>
>>> 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 permitted provided that the following conditions
>>> are met:
>>> #
>>> # 1. Redistributions of source code must retain the above copyright
>>> notice,
>>> # this list of conditions and the following disclaimer.
>>> #
>>> # 2. Redistributions in binary form must reproduce the above
>>> copyright notice,
>>> # this list of conditions and the following disclaimer in the
>>> documentation
>>> # and/or other materials provided with the distribution.
>>> #
>>> # THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND
>>> CONTRIBUTORS "AS IS"
>>> # AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
>>> TO, THE
>>> # IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
>>> PURPOSE
>>> # ARE DISCLAI

Re: error while running rtems-test with coverage

[Vijay Kumar Banerjee]

-- 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, 
> wrote:
>
>> can we set it in [coverage] ?
>>
>> It runs with the same warnings of unable to read the .cov files


> -- 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 variable set in the new leon3-qemu.ini
>>>
>>> Heres the old version from the .MC file
>>>
>>> [global]
>>> bsp:  none,none, 'leon3'
>>> coverage_supported:   none,none, '1'
>>>
>>>
>>> On Fri, 13 Apr 2018, 18:29 Vijay Kumar Banerjee, <
>>> vijaykumar9...@gmail.com> wrote:
>>>
 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  f:0  u:0  e:0  I:0  B:0  t:0  i:0  W:0  |
 sparc/leon3_qemu: capture.exe
 [ 4/13] p:0  f:0  u:0  e:0  I:0  B:0  t:0  i:0  W:0  |
 sparc/leon3_qemu: fileio.exe
 error: qemu.cfg:77: macro '%{coverage_supported}' not found
 warning: switched to dry run due to errors
 error: qemu.cfg:77: invalid if bool value:  %if %{coverage_supported}
 error: qemu.cfg:77: macro '%{coverage_supported}' not found
 warning: switched to dry run due to errors
 error: qemu.cfg:77: invalid if bool value:  %if %{coverage_supported}
 Traceback (most recent call last):
   File 
 "/home/lunatic/development/rtems/test/rtems-tools/tester/rtems-test",
 line 40, in 
 rt.test.run()
   File 
 "/home/lunatic/development/rtems/test/rtems-tools/tester/rt/test.py",
 line 353, in run
 tst.reraise()
   File 
 "/home/lunatic/development/rtems/test/rtems-tools/tester/rt/test.py",
 line 160, in reraise
 _test_reraise(*self.result)
 NameError: global name '_test_reraise' is not defined
 error: qemu.cfg:77: macro '%{coverage_supported}' not found
 warning: switched to dry run due to errors
 error: qemu.cfg:77: invalid if bool value:  %if %{coverage_supported}
 error: qemu.cfg:77: macro '%{coverage_supported}' not found
 warning: switched to dry run due to errors
 error: qemu.cfg:77: invalid if bool value:  %if %{coverage_supported}



 -- vijay

 On 13 April 2018 at 22:54, Cillian O'Donnell 
 wrote:

> 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 for %{bsp}"
> %endif
> %endif
>
> #
> # Executable
> #
> %execute %{qemu_cmd} %{qemu_opts_base} %{qemu_opts} -kernel 
> %{test_executable} %{coverage_arg}
>
>
> On Fri, 13 Apr 2018, 18:18 Vijay Kumar Banerjee, <
> vijaykumar9...@gmail.com> wrote:
>
>> 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 permitted provided that the following conditions
>> are met:
>> #
>> # 1. Redistributions of source code must retain the above copyright
>> notice,
>> # this list of conditions and the following disclaimer.
>> #
>> # 2. Redistributions in binary form must reproduce the above
>> copyright notice,
>> # this list of conditions and the following disclaimer in the
>> documentation
>> # and/or other materials provided with the distribution.
>> #
>> # THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
>> "AS IS"
>> # AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
>> TO, THE
>> # IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
>> PURPOSE
>> # ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR
>> CONTRIBUTORS BE
>> # LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
>> # CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
>> # SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
>> BUSIN

Re: error while running rtems-test with coverage

[Cillian O'Donnell]

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 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 variable set in the new leon3-qemu.ini
>>
>> Heres the old version from the .MC file
>>
>> [global]
>> bsp:  none,none, 'leon3'
>> coverage_supported:   none,none, '1'
>>
>>
>> On Fri, 13 Apr 2018, 18:29 Vijay Kumar Banerjee, <
>> vijaykumar9...@gmail.com> wrote:
>>
>>> 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  f:0  u:0  e:0  I:0  B:0  t:0  i:0  W:0  | sparc/leon3_qemu:
>>> capture.exe
>>> [ 4/13] p:0  f:0  u:0  e:0  I:0  B:0  t:0  i:0  W:0  | sparc/leon3_qemu:
>>> fileio.exe
>>> error: qemu.cfg:77: macro '%{coverage_supported}' not found
>>> warning: switched to dry run due to errors
>>> error: qemu.cfg:77: invalid if bool value:  %if %{coverage_supported}
>>> error: qemu.cfg:77: macro '%{coverage_supported}' not found
>>> warning: switched to dry run due to errors
>>> error: qemu.cfg:77: invalid if bool value:  %if %{coverage_supported}
>>> Traceback (most recent call last):
>>>   File
>>> "/home/lunatic/development/rtems/test/rtems-tools/tester/rtems-test", line
>>> 40, in 
>>> rt.test.run()
>>>   File
>>> "/home/lunatic/development/rtems/test/rtems-tools/tester/rt/test.py", line
>>> 353, in run
>>> tst.reraise()
>>>   File
>>> "/home/lunatic/development/rtems/test/rtems-tools/tester/rt/test.py", line
>>> 160, in reraise
>>> _test_reraise(*self.result)
>>> NameError: global name '_test_reraise' is not defined
>>> error: qemu.cfg:77: macro '%{coverage_supported}' not found
>>> warning: switched to dry run due to errors
>>> error: qemu.cfg:77: invalid if bool value:  %if %{coverage_supported}
>>> error: qemu.cfg:77: macro '%{coverage_supported}' not found
>>> warning: switched to dry run due to errors
>>> error: qemu.cfg:77: invalid if bool value:  %if %{coverage_supported}
>>>
>>>
>>>
>>> -- vijay
>>>
>>> On 13 April 2018 at 22:54, Cillian O'Donnell 
>>> wrote:
>>>
 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 for %{bsp}"
 %endif
 %endif

 #
 # Executable
 #
 %execute %{qemu_cmd} %{qemu_opts_base} %{qemu_opts} -kernel 
 %{test_executable} %{coverage_arg}


 On Fri, 13 Apr 2018, 18:18 Vijay Kumar Banerjee, <
 vijaykumar9...@gmail.com> wrote:

> 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 permitted provided that the following conditions
> are met:
> #
> # 1. Redistributions of source code must retain the above copyright
> notice,
> # this list of conditions and the following disclaimer.
> #
> # 2. Redistributions in binary form must reproduce the above copyright
> notice,
> # this list of conditions and the following disclaimer in the
> documentation
> # and/or other materials provided with the distribution.
> #
> # THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
> "AS IS"
> # AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
> TO, THE
> # IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
> PURPOSE
> # ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR
> CONTRIBUTORS BE
> # LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
> # CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
> # SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
> BUSINESS
> # INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER
> IN
> # CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
> OTHERWISE)
> # ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
> OF THE
> # P

Re: error while running rtems-test with coverage

[Vijay Kumar Banerjee]

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 variable set in the new leon3-qemu.ini
>
> Heres the old version from the .MC file
>
> [global]
> bsp:  none,none, 'leon3'
> coverage_supported:   none,none, '1'
>
>
> On Fri, 13 Apr 2018, 18:29 Vijay Kumar Banerjee, 
> wrote:
>
>> 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  f:0  u:0  e:0  I:0  B:0  t:0  i:0  W:0  | sparc/leon3_qemu:
>> capture.exe
>> [ 4/13] p:0  f:0  u:0  e:0  I:0  B:0  t:0  i:0  W:0  | sparc/leon3_qemu:
>> fileio.exe
>> error: qemu.cfg:77: macro '%{coverage_supported}' not found
>> warning: switched to dry run due to errors
>> error: qemu.cfg:77: invalid if bool value:  %if %{coverage_supported}
>> error: qemu.cfg:77: macro '%{coverage_supported}' not found
>> warning: switched to dry run due to errors
>> error: qemu.cfg:77: invalid if bool value:  %if %{coverage_supported}
>> Traceback (most recent call last):
>>   File "/home/lunatic/development/rtems/test/rtems-tools/tester/rtems-test",
>> line 40, in 
>> rt.test.run()
>>   File "/home/lunatic/development/rtems/test/rtems-tools/tester/rt/test.py",
>> line 353, in run
>> tst.reraise()
>>   File "/home/lunatic/development/rtems/test/rtems-tools/tester/rt/test.py",
>> line 160, in reraise
>> _test_reraise(*self.result)
>> NameError: global name '_test_reraise' is not defined
>> error: qemu.cfg:77: macro '%{coverage_supported}' not found
>> warning: switched to dry run due to errors
>> error: qemu.cfg:77: invalid if bool value:  %if %{coverage_supported}
>> error: qemu.cfg:77: macro '%{coverage_supported}' not found
>> warning: switched to dry run due to errors
>> error: qemu.cfg:77: invalid if bool value:  %if %{coverage_supported}
>>
>>
>>
>> -- vijay
>>
>> On 13 April 2018 at 22:54, Cillian O'Donnell 
>> wrote:
>>
>>> 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 for %{bsp}"
>>> %endif
>>> %endif
>>>
>>> #
>>> # Executable
>>> #
>>> %execute %{qemu_cmd} %{qemu_opts_base} %{qemu_opts} -kernel 
>>> %{test_executable} %{coverage_arg}
>>>
>>>
>>> On Fri, 13 Apr 2018, 18:18 Vijay Kumar Banerjee, <
>>> vijaykumar9...@gmail.com> wrote:
>>>
 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 permitted provided that the following conditions
 are met:
 #
 # 1. Redistributions of source code must retain the above copyright
 notice,
 # this list of conditions and the following disclaimer.
 #
 # 2. Redistributions in binary form must reproduce the above copyright
 notice,
 # this list of conditions and the following disclaimer in the
 documentation
 # and/or other materials provided with the distribution.
 #
 # THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
 "AS IS"
 # AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,
 THE
 # IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
 PURPOSE
 # ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR
 CONTRIBUTORS BE
 # LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
 # CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
 # SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
 BUSINESS
 # INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER
 IN
 # CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
 OTHERWISE)
 # ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
 OF THE
 # POSSIBILITY OF SUCH DAMAGE.
 #

 #
 # QEMU
 #
 # Use a qemu command to run the executable in the qemu simulator.
 #

 %include %{_configdir}/base.cfg
 %include %{_configdir}/checks.cfg

 #
 # Console.
 #
 %define console_stdio
 %include %{_configdir}/console.cfg

 #
 # RTEMS version
 #
 %include %{_

Re: error while running rtems-test with coverage

[Cillian O'Donnell]

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,none, 'leon3'
coverage_supported:   none,none, '1'


On Fri, 13 Apr 2018, 18:29 Vijay Kumar Banerjee, 
wrote:

> 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  f:0  u:0  e:0  I:0  B:0  t:0  i:0  W:0  | sparc/leon3_qemu:
> capture.exe
> [ 4/13] p:0  f:0  u:0  e:0  I:0  B:0  t:0  i:0  W:0  | sparc/leon3_qemu:
> fileio.exe
> error: qemu.cfg:77: macro '%{coverage_supported}' not found
> warning: switched to dry run due to errors
> error: qemu.cfg:77: invalid if bool value:  %if %{coverage_supported}
> error: qemu.cfg:77: macro '%{coverage_supported}' not found
> warning: switched to dry run due to errors
> error: qemu.cfg:77: invalid if bool value:  %if %{coverage_supported}
> Traceback (most recent call last):
>   File
> "/home/lunatic/development/rtems/test/rtems-tools/tester/rtems-test", line
> 40, in 
> rt.test.run()
>   File
> "/home/lunatic/development/rtems/test/rtems-tools/tester/rt/test.py", line
> 353, in run
> tst.reraise()
>   File
> "/home/lunatic/development/rtems/test/rtems-tools/tester/rt/test.py", line
> 160, in reraise
> _test_reraise(*self.result)
> NameError: global name '_test_reraise' is not defined
> error: qemu.cfg:77: macro '%{coverage_supported}' not found
> warning: switched to dry run due to errors
> error: qemu.cfg:77: invalid if bool value:  %if %{coverage_supported}
> error: qemu.cfg:77: macro '%{coverage_supported}' not found
> warning: switched to dry run due to errors
> error: qemu.cfg:77: invalid if bool value:  %if %{coverage_supported}
>
>
>
> -- vijay
>
> On 13 April 2018 at 22:54, Cillian O'Donnell 
> wrote:
>
>> 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 for %{bsp}"
>> %endif
>> %endif
>>
>> #
>> # Executable
>> #
>> %execute %{qemu_cmd} %{qemu_opts_base} %{qemu_opts} -kernel 
>> %{test_executable} %{coverage_arg}
>>
>>
>> On Fri, 13 Apr 2018, 18:18 Vijay Kumar Banerjee, <
>> vijaykumar9...@gmail.com> wrote:
>>
>>> 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 permitted provided that the following conditions are
>>> met:
>>> #
>>> # 1. Redistributions of source code must retain the above copyright
>>> notice,
>>> # this list of conditions and the following disclaimer.
>>> #
>>> # 2. Redistributions in binary form must reproduce the above copyright
>>> notice,
>>> # this list of conditions and the following disclaimer in the
>>> documentation
>>> # and/or other materials provided with the distribution.
>>> #
>>> # THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
>>> "AS IS"
>>> # AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,
>>> THE
>>> # IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
>>> PURPOSE
>>> # ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS
>>> BE
>>> # LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
>>> # CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
>>> # SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
>>> BUSINESS
>>> # INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
>>> # CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
>>> # ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
>>> THE
>>> # POSSIBILITY OF SUCH DAMAGE.
>>> #
>>>
>>> #
>>> # QEMU
>>> #
>>> # Use a qemu command to run the executable in the qemu simulator.
>>> #
>>>
>>> %include %{_configdir}/base.cfg
>>> %include %{_configdir}/checks.cfg
>>>
>>> #
>>> # Console.
>>> #
>>> %define console_stdio
>>> %include %{_configdir}/console.cfg
>>>
>>> #
>>> # RTEMS version
>>> #
>>> %include %{_rtdir}/rtems/version.cfg
>>>
>>> #
>>> # Qemu common option patterns.
>>> #
>>> #%define qemu_opts_base   -no-reboot -monitor none -serial stdio
>>> -nographic
>>> #%define qemu_opts_base   -no-reboot -serial null -serial mon:stdio
>>> -nographic
>>> %d

Re: error while running rtems-test with coverage

[Vijay Kumar Banerjee]

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  f:0  u:0  e:0  I:0  B:0  t:0  i:0  W:0  | sparc/leon3_qemu:
capture.exe
[ 4/13] p:0  f:0  u:0  e:0  I:0  B:0  t:0  i:0  W:0  | sparc/leon3_qemu:
fileio.exe
error: qemu.cfg:77: macro '%{coverage_supported}' not found
warning: switched to dry run due to errors
error: qemu.cfg:77: invalid if bool value:  %if %{coverage_supported}
error: qemu.cfg:77: macro '%{coverage_supported}' not found
warning: switched to dry run due to errors
error: qemu.cfg:77: invalid if bool value:  %if %{coverage_supported}
Traceback (most recent call last):
  File
"/home/lunatic/development/rtems/test/rtems-tools/tester/rtems-test", line
40, in 
rt.test.run()
  File
"/home/lunatic/development/rtems/test/rtems-tools/tester/rt/test.py", line
353, in run
tst.reraise()
  File
"/home/lunatic/development/rtems/test/rtems-tools/tester/rt/test.py", line
160, in reraise
_test_reraise(*self.result)
NameError: global name '_test_reraise' is not defined
error: qemu.cfg:77: macro '%{coverage_supported}' not found
warning: switched to dry run due to errors
error: qemu.cfg:77: invalid if bool value:  %if %{coverage_supported}
error: qemu.cfg:77: macro '%{coverage_supported}' not found
warning: switched to dry run due to errors
error: qemu.cfg:77: invalid if bool value:  %if %{coverage_supported}



-- vijay

On 13 April 2018 at 22:54, Cillian O'Donnell  wrote:

> 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 for %{bsp}"
> %endif
> %endif
>
> #
> # Executable
> #
> %execute %{qemu_cmd} %{qemu_opts_base} %{qemu_opts} -kernel 
> %{test_executable} %{coverage_arg}
>
>
> On Fri, 13 Apr 2018, 18:18 Vijay Kumar Banerjee, 
> wrote:
>
>> 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 permitted provided that the following conditions are
>> met:
>> #
>> # 1. Redistributions of source code must retain the above copyright
>> notice,
>> # this list of conditions and the following disclaimer.
>> #
>> # 2. Redistributions in binary form must reproduce the above copyright
>> notice,
>> # this list of conditions and the following disclaimer in the
>> documentation
>> # and/or other materials provided with the distribution.
>> #
>> # THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS
>> IS"
>> # AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,
>> THE
>> # IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
>> PURPOSE
>> # ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS
>> BE
>> # LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
>> # CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
>> # SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
>> # INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
>> # CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
>> # ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
>> THE
>> # POSSIBILITY OF SUCH DAMAGE.
>> #
>>
>> #
>> # QEMU
>> #
>> # Use a qemu command to run the executable in the qemu simulator.
>> #
>>
>> %include %{_configdir}/base.cfg
>> %include %{_configdir}/checks.cfg
>>
>> #
>> # Console.
>> #
>> %define console_stdio
>> %include %{_configdir}/console.cfg
>>
>> #
>> # RTEMS version
>> #
>> %include %{_rtdir}/rtems/version.cfg
>>
>> #
>> # Qemu common option patterns.
>> #
>> #%define qemu_opts_base   -no-reboot -monitor none -serial stdio
>> -nographic
>> #%define qemu_opts_base   -no-reboot -serial null -serial mon:stdio
>> -nographic
>> %define qemu_opts_base  -no-reboot -monitor null -serial stdio -nographic
>> %define qemu_opts_no_net -net none
>> #
>> # Qemu executable
>> #
>> %ifn %{defined bsp_qemu_opts}
>>  %define bsp_qemu_opts %{nil}
>> %endif
>> %define qemu_cmd  qemu-system-%{bsp_arch}
>> %define qemu_opts %{bsp_qemu_opts}
>>
>> #
>> # Executable
>> #
>> %execute %{qemu_cmd} %{qemu_opts} -kernel %{test_executable}
>>
>> -- vijay
>>
>> On 13 April 2018 at 22:19, Cillian O'Donnell 
>> wrote:
>>
>>> 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 Fr

Re: error while running rtems-test with coverage

[Cillian O'Donnell]

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 for %{bsp}"
%endif
%endif

#
# Executable
#
%execute %{qemu_cmd} %{qemu_opts_base} %{qemu_opts} -kernel
%{test_executable} %{coverage_arg}


On Fri, 13 Apr 2018, 18:18 Vijay Kumar Banerjee, 
wrote:

> 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 permitted provided that the following conditions are
> met:
> #
> # 1. Redistributions of source code must retain the above copyright notice,
> # this list of conditions and the following disclaimer.
> #
> # 2. Redistributions in binary form must reproduce the above copyright
> notice,
> # this list of conditions and the following disclaimer in the documentation
> # and/or other materials provided with the distribution.
> #
> # THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS
> IS"
> # AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
> # IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
> PURPOSE
> # ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE
> # LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
> # CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
> # SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
> # INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
> # CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
> # ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
> THE
> # POSSIBILITY OF SUCH DAMAGE.
> #
>
> #
> # QEMU
> #
> # Use a qemu command to run the executable in the qemu simulator.
> #
>
> %include %{_configdir}/base.cfg
> %include %{_configdir}/checks.cfg
>
> #
> # Console.
> #
> %define console_stdio
> %include %{_configdir}/console.cfg
>
> #
> # RTEMS version
> #
> %include %{_rtdir}/rtems/version.cfg
>
> #
> # Qemu common option patterns.
> #
> #%define qemu_opts_base   -no-reboot -monitor none -serial stdio -nographic
> #%define qemu_opts_base   -no-reboot -serial null -serial mon:stdio
> -nographic
> %define qemu_opts_base  -no-reboot -monitor null -serial stdio -nographic
> %define qemu_opts_no_net -net none
> #
> # Qemu executable
> #
> %ifn %{defined bsp_qemu_opts}
>  %define bsp_qemu_opts %{nil}
> %endif
> %define qemu_cmd  qemu-system-%{bsp_arch}
> %define qemu_opts %{bsp_qemu_opts}
>
> #
> # Executable
> #
> %execute %{qemu_cmd} %{qemu_opts} -kernel %{test_executable}
>
> -- vijay
>
> On 13 April 2018 at 22:19, Cillian O'Donnell 
> wrote:
>
>> 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, <
>> vijaykumar9...@gmail.com> wrote:
>>
>>> 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
 rtems-tools/tester/rtems/testing

 On Fri, 13 Apr 2018, 06:39 Vijay Kumar Banerjee, <
 vijaykumar9...@gmail.com> wrote:

> I manually built qemu from here
>
> https://github.com/AdaCore/qemu
>
> I guess this is regular qemu , please send a link for couverture
> qemu for manual build.
>
> -- vijay
>
> On 12 April 2018 at 22:23, Cillian O'Donnell 
> wrote:
>
>> Ah that's good progress, those .cov files are supposed to be
>> generated by couverture-qemu as the test are run. They contain the trace
>> data. Are you definitely running couverture-qemu and not regular qemu?
>>
>> On Thu, 12 Apr 2018, 17:41 Vijay Kumar Banerjee, <
>> vijaykumar9...@gmail.com> wrote:
>>
>>> I got the parsing of the coverage from the ini file running , now
>>> I'm getting the following error and warnings .
>>>
>>>
>>> 
>>>
>>> Running covoar for score
>>> WARNING: Unable to read coverage file
>>> /home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/base_sp/base_sp.exe.cov
>>> WARNING: Unable to read coverage file
>>> /home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/capture/capture.exe.cov
>>> WARNING: Unable to read coverage file
>>> /home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/cdtest/cdtest.

Re: error while running rtems-test with coverage

[Vijay Kumar Banerjee]

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 permitted provided that the following conditions are
met:
#
# 1. Redistributions of source code must retain the above copyright notice,
# this list of conditions and the following disclaimer.
#
# 2. Redistributions in binary form must reproduce the above copyright
notice,
# this list of conditions and the following disclaimer in the documentation
# and/or other materials provided with the distribution.
#
# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS
IS"
# AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
# IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
# ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE
# LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
# CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
# SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
# INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
# CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
# ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
# POSSIBILITY OF SUCH DAMAGE.
#

#
# QEMU
#
# Use a qemu command to run the executable in the qemu simulator.
#

%include %{_configdir}/base.cfg
%include %{_configdir}/checks.cfg

#
# Console.
#
%define console_stdio
%include %{_configdir}/console.cfg

#
# RTEMS version
#
%include %{_rtdir}/rtems/version.cfg

#
# Qemu common option patterns.
#
#%define qemu_opts_base   -no-reboot -monitor none -serial stdio -nographic
#%define qemu_opts_base   -no-reboot -serial null -serial mon:stdio
-nographic
%define qemu_opts_base  -no-reboot -monitor null -serial stdio -nographic
%define qemu_opts_no_net -net none
#
# Qemu executable
#
%ifn %{defined bsp_qemu_opts}
 %define bsp_qemu_opts %{nil}
%endif
%define qemu_cmd  qemu-system-%{bsp_arch}
%define qemu_opts %{bsp_qemu_opts}

#
# Executable
#
%execute %{qemu_cmd} %{qemu_opts} -kernel %{test_executable}

-- vijay

On 13 April 2018 at 22:19, Cillian O'Donnell  wrote:

> 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 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
>>> rtems-tools/tester/rtems/testing
>>>
>>> On Fri, 13 Apr 2018, 06:39 Vijay Kumar Banerjee, <
>>> vijaykumar9...@gmail.com> wrote:
>>>
 I manually built qemu from here

 https://github.com/AdaCore/qemu

 I guess this is regular qemu , please send a link for couverture
 qemu for manual build.

 -- vijay

 On 12 April 2018 at 22:23, Cillian O'Donnell 
 wrote:

> Ah that's good progress, those .cov files are supposed to be generated
> by couverture-qemu as the test are run. They contain the trace data. Are
> you definitely running couverture-qemu and not regular qemu?
>
> On Thu, 12 Apr 2018, 17:41 Vijay Kumar Banerjee, <
> vijaykumar9...@gmail.com> wrote:
>
>> I got the parsing of the coverage from the ini file running , now I'm
>> getting the following error and warnings .
>>
>>
>> 
>>
>> Running covoar for score
>> WARNING: Unable to read coverage file /home/lunatic/development/
>> rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/
>> samples/base_sp/base_sp.exe.cov
>> WARNING: Unable to read coverage file /home/lunatic/development/
>> rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/
>> samples/capture/capture.exe.cov
>> WARNING: Unable to read coverage file /home/lunatic/development/
>> rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/
>> samples/cdtest/cdtest.exe.cov
>> WARNING: Unable to read coverage file /home/lunatic/development/
>> rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/
>> samples/fileio/fileio.exe.cov
>> WARNING: Unable to read coverage file /home/lunatic/development/
>> rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/
>> samples/hello/hello.exe.cov
>> WARNING: Unable to read coverage file /home/lunatic/development/
>> rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/
>> samples/iostream/cxx_iostream.exe.cov
>> WARNING: Unable to read coverage file /home/lunatic/development/
>> rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/
>> samples/loopback/loopback.exe.cov
>> WARNING: Unable t

Re: error while running rtems-test with coverage

[Cillian O'Donnell]

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 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
>> rtems-tools/tester/rtems/testing
>>
>> On Fri, 13 Apr 2018, 06:39 Vijay Kumar Banerjee, <
>> vijaykumar9...@gmail.com> wrote:
>>
>>> I manually built qemu from here
>>>
>>> https://github.com/AdaCore/qemu
>>>
>>> I guess this is regular qemu , please send a link for couverture
>>> qemu for manual build.
>>>
>>> -- vijay
>>>
>>> On 12 April 2018 at 22:23, Cillian O'Donnell 
>>> wrote:
>>>
 Ah that's good progress, those .cov files are supposed to be generated
 by couverture-qemu as the test are run. They contain the trace data. Are
 you definitely running couverture-qemu and not regular qemu?

 On Thu, 12 Apr 2018, 17:41 Vijay Kumar Banerjee, <
 vijaykumar9...@gmail.com> wrote:

> I got the parsing of the coverage from the ini file running , now I'm
> getting the following error and warnings .
>
>
> 
>
> Running covoar for score
> WARNING: Unable to read coverage file
> /home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/base_sp/base_sp.exe.cov
> WARNING: Unable to read coverage file
> /home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/capture/capture.exe.cov
> WARNING: Unable to read coverage file
> /home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/cdtest/cdtest.exe.cov
> WARNING: Unable to read coverage file
> /home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/fileio/fileio.exe.cov
> WARNING: Unable to read coverage file
> /home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/hello/hello.exe.cov
> WARNING: Unable to read coverage file
> /home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/iostream/cxx_iostream.exe.cov
> WARNING: Unable to read coverage file
> /home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/loopback/loopback.exe.cov
> WARNING: Unable to read coverage file
> /home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/minimum/minimum.exe.cov
> WARNING: Unable to read coverage file
> /home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/nsecs/nsecs.exe.cov
> WARNING: Unable to read coverage file
> /home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/paranoia/paranoia.exe.cov
> WARNING: Unable to read coverage file
> /home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/pppd/pppd.exe.cov
> WARNING: Unable to read coverage file
> /home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/ticker/ticker.exe.cov
> WARNING: Unable to read coverage file
> /home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/unlimited/unlimited.exe.cov
> ERROR: No information to analyze
> ***Cleaning tempfiles***
> error: covoar failure exit code: 1
>
>
>
>
> -- vijay
>
> On 10 April 2018 at 18:10, Vijay Kumar Banerjee <
> vijaykumar9...@gmail.com> wrote:
>
>> I managed to get the tests running with the following two patches .
>> Please review them .
>>
>> -- vijay
>>
>> On 9 April 2018 at 15:28, Vijay Kumar Banerjee <
>> vijaykumar9...@gmail.com> wrote:
>>
>>>
>>>
>>> On Fri, 6 Apr 2018, 02:24 Vijay Kumar Banerjee, <
>>> vijaykumar9...@gmail.com> wrote:
>>>
 I tried to solve the empty get in the way shown in the patch , but
 it doesn't seems to work, I'm getting the following error now

 RTEMS Testing - Tester, 5 (1ed6e2e64090)
 Traceback (most recent call last):
   File
 "/home/lunatic/development/rtems/rtems-tools/tester/rtems-test", line 
 40,
 in 
 rt.test.run()
   File
 "/home/lunatic/development/rtems/rtems-tools/tester/rt/test.py", line 
 303,
 in run
 bsp = config.load(bsp[1], opts)
   File
 "/home/lunatic/development/rtems/rtems-tools/tester/rt/config.py", line
 461, in load
 return opts.defaults['bsp']
   File
 "/home/lunatic/development/rtems/rtems-tools/rtemstoolkit/macros.py", 
 line
 190, in __getitem__
 raise IndexError('key: %s' % (key))
 IndexError: key: bsp

>

Re: error while running rtems-test with coverage

[Vijay Kumar Banerjee]

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
> rtems-tools/tester/rtems/testing
>
> On Fri, 13 Apr 2018, 06:39 Vijay Kumar Banerjee, 
> wrote:
>
>> I manually built qemu from here
>>
>> https://github.com/AdaCore/qemu
>>
>> I guess this is regular qemu , please send a link for couverture qemu for
>> manual build.
>>
>> -- vijay
>>
>> On 12 April 2018 at 22:23, Cillian O'Donnell 
>> wrote:
>>
>>> Ah that's good progress, those .cov files are supposed to be generated
>>> by couverture-qemu as the test are run. They contain the trace data. Are
>>> you definitely running couverture-qemu and not regular qemu?
>>>
>>> On Thu, 12 Apr 2018, 17:41 Vijay Kumar Banerjee, <
>>> vijaykumar9...@gmail.com> wrote:
>>>
 I got the parsing of the coverage from the ini file running , now I'm
 getting the following error and warnings .


 

 Running covoar for score
 WARNING: Unable to read coverage file /home/lunatic/development/
 rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/
 samples/base_sp/base_sp.exe.cov
 WARNING: Unable to read coverage file /home/lunatic/development/
 rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/
 samples/capture/capture.exe.cov
 WARNING: Unable to read coverage file /home/lunatic/development/
 rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/
 samples/cdtest/cdtest.exe.cov
 WARNING: Unable to read coverage file /home/lunatic/development/
 rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/
 samples/fileio/fileio.exe.cov
 WARNING: Unable to read coverage file /home/lunatic/development/
 rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/
 samples/hello/hello.exe.cov
 WARNING: Unable to read coverage file /home/lunatic/development/
 rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/
 samples/iostream/cxx_iostream.exe.cov
 WARNING: Unable to read coverage file /home/lunatic/development/
 rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/
 samples/loopback/loopback.exe.cov
 WARNING: Unable to read coverage file /home/lunatic/development/
 rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/
 samples/minimum/minimum.exe.cov
 WARNING: Unable to read coverage file /home/lunatic/development/
 rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/
 samples/nsecs/nsecs.exe.cov
 WARNING: Unable to read coverage file /home/lunatic/development/
 rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/
 samples/paranoia/paranoia.exe.cov
 WARNING: Unable to read coverage file /home/lunatic/development/
 rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/
 samples/pppd/pppd.exe.cov
 WARNING: Unable to read coverage file /home/lunatic/development/
 rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/
 samples/ticker/ticker.exe.cov
 WARNING: Unable to read coverage file /home/lunatic/development/
 rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/
 samples/unlimited/unlimited.exe.cov
 ERROR: No information to analyze
 ***Cleaning tempfiles***
 error: covoar failure exit code: 1




 -- vijay

 On 10 April 2018 at 18:10, Vijay Kumar Banerjee <
 vijaykumar9...@gmail.com> wrote:

> I managed to get the tests running with the following two patches .
> Please review them .
>
> -- vijay
>
> On 9 April 2018 at 15:28, Vijay Kumar Banerjee <
> vijaykumar9...@gmail.com> wrote:
>
>>
>>
>> On Fri, 6 Apr 2018, 02:24 Vijay Kumar Banerjee, <
>> vijaykumar9...@gmail.com> wrote:
>>
>>> I tried to solve the empty get in the way shown in the patch , but
>>> it doesn't seems to work, I'm getting the following error now
>>>
>>> RTEMS Testing - Tester, 5 (1ed6e2e64090)
>>> Traceback (most recent call last):
>>>   File "/home/lunatic/development/rtems/rtems-tools/tester/rtems-test",
>>> line 40, in 
>>> rt.test.run()
>>>   File "/home/lunatic/development/rtems/rtems-tools/tester/rt/test.py",
>>> line 303, in run
>>> bsp = config.load(bsp[1], opts)
>>>   File 
>>> "/home/lunatic/development/rtems/rtems-tools/tester/rt/config.py",
>>> line 461, in load
>>> return opts.defaults['bsp']
>>>   File 
>>> "/home/lunatic/development/rtems/rtems-tools/rtemstoolkit/macros.py",
>>> line 190, in __getitem__
>>> raise IndexError('key: %s' % (key))
>>> IndexError: key: bsp
>>>
>>> I still Couldn't figure out why it's happening, when I use
>> RawConfigParse , it seems to run nicely though .
>>
>> Any Ideas on solving it without using RawConfigParser ?
>>
>>
>>> -- vijay
>>>
>>> On 5 April 2018 at 11:51, Cillian O'Donnell 
>>> wrote:

Re: error while running rtems-test with coverage

[Cillian O'Donnell]

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
>
> https://github.com/AdaCore/qemu
>
> I guess this is regular qemu , please send a link for couverture qemu for
> manual build.
>
> -- vijay
>
> On 12 April 2018 at 22:23, Cillian O'Donnell 
> wrote:
>
>> Ah that's good progress, those .cov files are supposed to be generated by
>> couverture-qemu as the test are run. They contain the trace data. Are you
>> definitely running couverture-qemu and not regular qemu?
>>
>> On Thu, 12 Apr 2018, 17:41 Vijay Kumar Banerjee, <
>> vijaykumar9...@gmail.com> wrote:
>>
>>> I got the parsing of the coverage from the ini file running , now I'm
>>> getting the following error and warnings .
>>>
>>>
>>> 
>>>
>>> Running covoar for score
>>> WARNING: Unable to read coverage file
>>> /home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/base_sp/base_sp.exe.cov
>>> WARNING: Unable to read coverage file
>>> /home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/capture/capture.exe.cov
>>> WARNING: Unable to read coverage file
>>> /home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/cdtest/cdtest.exe.cov
>>> WARNING: Unable to read coverage file
>>> /home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/fileio/fileio.exe.cov
>>> WARNING: Unable to read coverage file
>>> /home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/hello/hello.exe.cov
>>> WARNING: Unable to read coverage file
>>> /home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/iostream/cxx_iostream.exe.cov
>>> WARNING: Unable to read coverage file
>>> /home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/loopback/loopback.exe.cov
>>> WARNING: Unable to read coverage file
>>> /home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/minimum/minimum.exe.cov
>>> WARNING: Unable to read coverage file
>>> /home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/nsecs/nsecs.exe.cov
>>> WARNING: Unable to read coverage file
>>> /home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/paranoia/paranoia.exe.cov
>>> WARNING: Unable to read coverage file
>>> /home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/pppd/pppd.exe.cov
>>> WARNING: Unable to read coverage file
>>> /home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/ticker/ticker.exe.cov
>>> WARNING: Unable to read coverage file
>>> /home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/unlimited/unlimited.exe.cov
>>> ERROR: No information to analyze
>>> ***Cleaning tempfiles***
>>> error: covoar failure exit code: 1
>>>
>>>
>>>
>>>
>>> -- vijay
>>>
>>> On 10 April 2018 at 18:10, Vijay Kumar Banerjee <
>>> vijaykumar9...@gmail.com> wrote:
>>>
 I managed to get the tests running with the following two patches .
 Please review them .

 -- vijay

 On 9 April 2018 at 15:28, Vijay Kumar Banerjee <
 vijaykumar9...@gmail.com> wrote:

>
>
> On Fri, 6 Apr 2018, 02:24 Vijay Kumar Banerjee, <
> vijaykumar9...@gmail.com> wrote:
>
>> I tried to solve the empty get in the way shown in the patch , but it
>> doesn't seems to work, I'm getting the following error now
>>
>> RTEMS Testing - Tester, 5 (1ed6e2e64090)
>> Traceback (most recent call last):
>>   File
>> "/home/lunatic/development/rtems/rtems-tools/tester/rtems-test", line 40,
>> in 
>> rt.test.run()
>>   File
>> "/home/lunatic/development/rtems/rtems-tools/tester/rt/test.py", line 
>> 303,
>> in run
>> bsp = config.load(bsp[1], opts)
>>   File
>> "/home/lunatic/development/rtems/rtems-tools/tester/rt/config.py", line
>> 461, in load
>> return opts.defaults['bsp']
>>   File
>> "/home/lunatic/development/rtems/rtems-tools/rtemstoolkit/macros.py", 
>> line
>> 190, in __getitem__
>> raise IndexError('key: %s' % (key))
>> IndexError: key: bsp
>>
>> I still Couldn't figure out why it's happening, when I use
> RawConfigParse , it seems to run nicely though .
>
> Any Ideas on solving it without using RawConfigParser ?
>
>
>> -- vijay
>>
>> On 5 April 2018 at 11:51, Cillian O'Donnell 
>> wrote:
>>
>>>
>>>
>>> On Wed, 4 Apr 2018, 11:18 Vijay Kumar Banerjee, <
>>> vijaykumar9...@gmail.com> wrote:
>>>
 I got the rtems-test running

 I found that get_item_names(section, err) in configuration.py  was
 returning an empty list to the

Re: error while running rtems-test with coverage

[Vijay Kumar Banerjee]

I manually built qemu from here

https://github.com/AdaCore/qemu

I guess this is regular qemu , please send a link for couverture qemu for
manual build.

-- vijay

On 12 April 2018 at 22:23, Cillian O'Donnell  wrote:

> Ah that's good progress, those .cov files are supposed to be generated by
> couverture-qemu as the test are run. They contain the trace data. Are you
> definitely running couverture-qemu and not regular qemu?
>
> On Thu, 12 Apr 2018, 17:41 Vijay Kumar Banerjee, 
> wrote:
>
>> I got the parsing of the coverage from the ini file running , now I'm
>> getting the following error and warnings .
>>
>>
>> 
>>
>> Running covoar for score
>> WARNING: Unable to read coverage file /home/lunatic/development/
>> rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/
>> samples/base_sp/base_sp.exe.cov
>> WARNING: Unable to read coverage file /home/lunatic/development/
>> rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/
>> samples/capture/capture.exe.cov
>> WARNING: Unable to read coverage file /home/lunatic/development/
>> rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/
>> samples/cdtest/cdtest.exe.cov
>> WARNING: Unable to read coverage file /home/lunatic/development/
>> rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/
>> samples/fileio/fileio.exe.cov
>> WARNING: Unable to read coverage file /home/lunatic/development/
>> rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/
>> samples/hello/hello.exe.cov
>> WARNING: Unable to read coverage file /home/lunatic/development/
>> rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/
>> samples/iostream/cxx_iostream.exe.cov
>> WARNING: Unable to read coverage file /home/lunatic/development/
>> rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/
>> samples/loopback/loopback.exe.cov
>> WARNING: Unable to read coverage file /home/lunatic/development/
>> rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/
>> samples/minimum/minimum.exe.cov
>> WARNING: Unable to read coverage file /home/lunatic/development/
>> rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/
>> samples/nsecs/nsecs.exe.cov
>> WARNING: Unable to read coverage file /home/lunatic/development/
>> rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/
>> samples/paranoia/paranoia.exe.cov
>> WARNING: Unable to read coverage file /home/lunatic/development/
>> rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/
>> samples/pppd/pppd.exe.cov
>> WARNING: Unable to read coverage file /home/lunatic/development/
>> rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/
>> samples/ticker/ticker.exe.cov
>> WARNING: Unable to read coverage file /home/lunatic/development/
>> rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/
>> samples/unlimited/unlimited.exe.cov
>> ERROR: No information to analyze
>> ***Cleaning tempfiles***
>> error: covoar failure exit code: 1
>>
>>
>>
>>
>> -- vijay
>>
>> On 10 April 2018 at 18:10, Vijay Kumar Banerjee > > wrote:
>>
>>> I managed to get the tests running with the following two patches .
>>> Please review them .
>>>
>>> -- vijay
>>>
>>> On 9 April 2018 at 15:28, Vijay Kumar Banerjee >> > wrote:
>>>


 On Fri, 6 Apr 2018, 02:24 Vijay Kumar Banerjee, <
 vijaykumar9...@gmail.com> wrote:

> I tried to solve the empty get in the way shown in the patch , but it
> doesn't seems to work, I'm getting the following error now
>
> RTEMS Testing - Tester, 5 (1ed6e2e64090)
> Traceback (most recent call last):
>   File "/home/lunatic/development/rtems/rtems-tools/tester/rtems-test",
> line 40, in 
> rt.test.run()
>   File "/home/lunatic/development/rtems/rtems-tools/tester/rt/test.py",
> line 303, in run
> bsp = config.load(bsp[1], opts)
>   File "/home/lunatic/development/rtems/rtems-tools/tester/rt/config.py",
> line 461, in load
> return opts.defaults['bsp']
>   File 
> "/home/lunatic/development/rtems/rtems-tools/rtemstoolkit/macros.py",
> line 190, in __getitem__
> raise IndexError('key: %s' % (key))
> IndexError: key: bsp
>
> I still Couldn't figure out why it's happening, when I use
 RawConfigParse , it seems to run nicely though .

 Any Ideas on solving it without using RawConfigParser ?


> -- vijay
>
> On 5 April 2018 at 11:51, Cillian O'Donnell 
> wrote:
>
>>
>>
>> On Wed, 4 Apr 2018, 11:18 Vijay Kumar Banerjee, <
>> vijaykumar9...@gmail.com> wrote:
>>
>>> I got the rtems-test running
>>>
>>> I found that get_item_names(section, err) in configuration.py  was
>>> returning an empty list to the
>>> item_names in load(bsp,opts) for config.py this was giving out the
>>> error mandatory item not found .
>>>
>>> I have attached the patch file .
>>>
>>> current status :
>>> rtems-test is running without coverage
>>>
>>> running coverage gives the following error :
>>>
>>> RTEMS Testing - Tester, 5 (092c569e81ae)
>>> Traceback (most recent call la

Re: error while running rtems-test with coverage

[Cillian O'Donnell]

Ah that's good progress, those .cov files are supposed to be generated by
couverture-qemu as the test are run. They contain the trace data. Are you
definitely running couverture-qemu and not regular qemu?

On Thu, 12 Apr 2018, 17:41 Vijay Kumar Banerjee, 
wrote:

> I got the parsing of the coverage from the ini file running , now I'm
> getting the following error and warnings .
>
>
> 
>
> Running covoar for score
> WARNING: Unable to read coverage file
> /home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/base_sp/base_sp.exe.cov
> WARNING: Unable to read coverage file
> /home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/capture/capture.exe.cov
> WARNING: Unable to read coverage file
> /home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/cdtest/cdtest.exe.cov
> WARNING: Unable to read coverage file
> /home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/fileio/fileio.exe.cov
> WARNING: Unable to read coverage file
> /home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/hello/hello.exe.cov
> WARNING: Unable to read coverage file
> /home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/iostream/cxx_iostream.exe.cov
> WARNING: Unable to read coverage file
> /home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/loopback/loopback.exe.cov
> WARNING: Unable to read coverage file
> /home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/minimum/minimum.exe.cov
> WARNING: Unable to read coverage file
> /home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/nsecs/nsecs.exe.cov
> WARNING: Unable to read coverage file
> /home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/paranoia/paranoia.exe.cov
> WARNING: Unable to read coverage file
> /home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/pppd/pppd.exe.cov
> WARNING: Unable to read coverage file
> /home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/ticker/ticker.exe.cov
> WARNING: Unable to read coverage file
> /home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/unlimited/unlimited.exe.cov
> ERROR: No information to analyze
> ***Cleaning tempfiles***
> error: covoar failure exit code: 1
>
>
>
>
> -- vijay
>
> On 10 April 2018 at 18:10, Vijay Kumar Banerjee 
> wrote:
>
>> I managed to get the tests running with the following two patches .
>> Please review them .
>>
>> -- vijay
>>
>> On 9 April 2018 at 15:28, Vijay Kumar Banerjee 
>> wrote:
>>
>>>
>>>
>>> On Fri, 6 Apr 2018, 02:24 Vijay Kumar Banerjee, <
>>> vijaykumar9...@gmail.com> wrote:
>>>
 I tried to solve the empty get in the way shown in the patch , but it
 doesn't seems to work, I'm getting the following error now

 RTEMS Testing - Tester, 5 (1ed6e2e64090)
 Traceback (most recent call last):
   File "/home/lunatic/development/rtems/rtems-tools/tester/rtems-test",
 line 40, in 
 rt.test.run()
   File "/home/lunatic/development/rtems/rtems-tools/tester/rt/test.py",
 line 303, in run
 bsp = config.load(bsp[1], opts)
   File
 "/home/lunatic/development/rtems/rtems-tools/tester/rt/config.py", line
 461, in load
 return opts.defaults['bsp']
   File
 "/home/lunatic/development/rtems/rtems-tools/rtemstoolkit/macros.py", line
 190, in __getitem__
 raise IndexError('key: %s' % (key))
 IndexError: key: bsp

 I still Couldn't figure out why it's happening, when I use
>>> RawConfigParse , it seems to run nicely though .
>>>
>>> Any Ideas on solving it without using RawConfigParser ?
>>>
>>>
 -- vijay

 On 5 April 2018 at 11:51, Cillian O'Donnell 
 wrote:

>
>
> On Wed, 4 Apr 2018, 11:18 Vijay Kumar Banerjee, <
> vijaykumar9...@gmail.com> wrote:
>
>> I got the rtems-test running
>>
>> I found that get_item_names(section, err) in configuration.py  was
>> returning an empty list to the
>> item_names in load(bsp,opts) for config.py this was giving out the
>> error mandatory item not found .
>>
>> I have attached the patch file .
>>
>> current status :
>> rtems-test is running without coverage
>>
>> running coverage gives the following error :
>>
>> RTEMS Testing - Tester, 5 (092c569e81ae)
>> Traceback (most recent call last):
>>   File
>> "/home/lunatic/development/rtems/rtems-tools/tester/rtems-test", line 40,
>> in 
>> rt.test.run()
>>   File
>> "/home/lunatic/development/rtems/rtems-tools/tester/rt/test.py", line 
>> 310,
>> in run
>> coverage = coverage_get_obj(opts, path_to_builddir[1])
>>   File
>> "/home/lunatic/development/rtems/rtems-tools/tester/rt/test.p

Re: error while running rtems-test with coverage

[Vijay Kumar Banerjee]

I got the parsing of the coverage from the ini file running , now I'm
getting the following error and warnings .




Running covoar for score
WARNING: Unable to read coverage file
/home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/base_sp/base_sp.exe.cov
WARNING: Unable to read coverage file
/home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/capture/capture.exe.cov
WARNING: Unable to read coverage file
/home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/cdtest/cdtest.exe.cov
WARNING: Unable to read coverage file
/home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/fileio/fileio.exe.cov
WARNING: Unable to read coverage file
/home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/hello/hello.exe.cov
WARNING: Unable to read coverage file
/home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/iostream/cxx_iostream.exe.cov
WARNING: Unable to read coverage file
/home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/loopback/loopback.exe.cov
WARNING: Unable to read coverage file
/home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/minimum/minimum.exe.cov
WARNING: Unable to read coverage file
/home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/nsecs/nsecs.exe.cov
WARNING: Unable to read coverage file
/home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/paranoia/paranoia.exe.cov
WARNING: Unable to read coverage file
/home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/pppd/pppd.exe.cov
WARNING: Unable to read coverage file
/home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/ticker/ticker.exe.cov
WARNING: Unable to read coverage file
/home/lunatic/development/rtems/kernel/leon3/sparc-rtems5/c/leon3/testsuites/samples/unlimited/unlimited.exe.cov
ERROR: No information to analyze
***Cleaning tempfiles***
error: covoar failure exit code: 1




-- vijay

On 10 April 2018 at 18:10, Vijay Kumar Banerjee 
wrote:

> I managed to get the tests running with the following two patches .
> Please review them .
>
> -- vijay
>
> On 9 April 2018 at 15:28, Vijay Kumar Banerjee 
> wrote:
>
>>
>>
>> On Fri, 6 Apr 2018, 02:24 Vijay Kumar Banerjee, 
>> wrote:
>>
>>> I tried to solve the empty get in the way shown in the patch , but it
>>> doesn't seems to work, I'm getting the following error now
>>>
>>> RTEMS Testing - Tester, 5 (1ed6e2e64090)
>>> Traceback (most recent call last):
>>>   File "/home/lunatic/development/rtems/rtems-tools/tester/rtems-test",
>>> line 40, in 
>>> rt.test.run()
>>>   File "/home/lunatic/development/rtems/rtems-tools/tester/rt/test.py",
>>> line 303, in run
>>> bsp = config.load(bsp[1], opts)
>>>   File "/home/lunatic/development/rtems/rtems-tools/tester/rt/config.py",
>>> line 461, in load
>>> return opts.defaults['bsp']
>>>   File "/home/lunatic/development/rtems/rtems-tools/rtemstoolkit/macros.py",
>>> line 190, in __getitem__
>>> raise IndexError('key: %s' % (key))
>>> IndexError: key: bsp
>>>
>>> I still Couldn't figure out why it's happening, when I use
>> RawConfigParse , it seems to run nicely though .
>>
>> Any Ideas on solving it without using RawConfigParser ?
>>
>>
>>> -- vijay
>>>
>>> On 5 April 2018 at 11:51, Cillian O'Donnell 
>>> wrote:
>>>


 On Wed, 4 Apr 2018, 11:18 Vijay Kumar Banerjee, <
 vijaykumar9...@gmail.com> wrote:

> I got the rtems-test running
>
> I found that get_item_names(section, err) in configuration.py  was
> returning an empty list to the
> item_names in load(bsp,opts) for config.py this was giving out the
> error mandatory item not found .
>
> I have attached the patch file .
>
> current status :
> rtems-test is running without coverage
>
> running coverage gives the following error :
>
> RTEMS Testing - Tester, 5 (092c569e81ae)
> Traceback (most recent call last):
>   File "/home/lunatic/development/rtems/rtems-tools/tester/rtems-test",
> line 40, in 
> rt.test.run()
>   File "/home/lunatic/development/rtems/rtems-tools/tester/rt/test.py",
> line 310, in run
> coverage = coverage_get_obj(opts, path_to_builddir[1])
>   File "/home/lunatic/development/rtems/rtems-tools/tester/rt/test.py",
> line 230, in coverage_get_obj
> coverage_obj = coverage.coverage_run(opts.defaults,
> path_to_builddir)
>   File 
> "/home/lunatic/development/rtems/rtems-tools/tester/rt/coverage.py",
> line 335, in __init__
> self.report_format = self.config_map['report_format'][2]
>

 This is back to the difference in cfg formats. It's looking for the
 last line here

 https://github.com/cillianodonnell/rtems-tools/blob/
 

Re: error while running rtems-test with coverage

[Aditya Upadhyay]

You can use this command to send a patch to devel:

git send-email LOCATION_OF_PATCH_FILE --to devel@rtems.org --cc=_EMAIL_ID

It makes easier to review the patch.

On Tue, Apr 10, 2018 at 6:10 PM, Vijay Kumar Banerjee
 wrote:
> I managed to get the tests running with the following two patches .
> Please review them .
>
> -- vijay
>
> On 9 April 2018 at 15:28, Vijay Kumar Banerjee 
> wrote:
>>
>>
>>
>> On Fri, 6 Apr 2018, 02:24 Vijay Kumar Banerjee, 
>> wrote:
>>>
>>> I tried to solve the empty get in the way shown in the patch , but it
>>> doesn't seems to work, I'm getting the following error now
>>>
>>> RTEMS Testing - Tester, 5 (1ed6e2e64090)
>>> Traceback (most recent call last):
>>>   File "/home/lunatic/development/rtems/rtems-tools/tester/rtems-test",
>>> line 40, in 
>>> rt.test.run()
>>>   File "/home/lunatic/development/rtems/rtems-tools/tester/rt/test.py",
>>> line 303, in run
>>> bsp = config.load(bsp[1], opts)
>>>   File "/home/lunatic/development/rtems/rtems-tools/tester/rt/config.py",
>>> line 461, in load
>>> return opts.defaults['bsp']
>>>   File
>>> "/home/lunatic/development/rtems/rtems-tools/rtemstoolkit/macros.py", line
>>> 190, in __getitem__
>>> raise IndexError('key: %s' % (key))
>>> IndexError: key: bsp
>>>
>> I still Couldn't figure out why it's happening, when I use RawConfigParse
>> , it seems to run nicely though .
>>
>> Any Ideas on solving it without using RawConfigParser ?
>>
>>>
>>> -- vijay
>>>
>>> On 5 April 2018 at 11:51, Cillian O'Donnell 
>>> wrote:



 On Wed, 4 Apr 2018, 11:18 Vijay Kumar Banerjee,
  wrote:
>
> I got the rtems-test running
>
> I found that get_item_names(section, err) in configuration.py  was
> returning an empty list to the
> item_names in load(bsp,opts) for config.py this was giving out the
> error mandatory item not found .
>
> I have attached the patch file .
>
> current status :
> rtems-test is running without coverage
>
> running coverage gives the following error :
>
> RTEMS Testing - Tester, 5 (092c569e81ae)
> Traceback (most recent call last):
>   File "/home/lunatic/development/rtems/rtems-tools/tester/rtems-test",
> line 40, in 
> rt.test.run()
>   File "/home/lunatic/development/rtems/rtems-tools/tester/rt/test.py",
> line 310, in run
> coverage = coverage_get_obj(opts, path_to_builddir[1])
>   File "/home/lunatic/development/rtems/rtems-tools/tester/rt/test.py",
> line 230, in coverage_get_obj
> coverage_obj = coverage.coverage_run(opts.defaults,
> path_to_builddir)
>   File
> "/home/lunatic/development/rtems/rtems-tools/tester/rt/coverage.py", line
> 335, in __init__
> self.report_format = self.config_map['report_format'][2]


 This is back to the difference in cfg formats. It's looking for the last
 line here


 https://github.com/cillianodonnell/rtems-tools/blob/coverage/tester/rtems/testing/bsps/leon3-qemu.mc

 Which is now


 https://github.com/cillianodonnell/rtems-tools/blob/ini-update/tester/rtems/testing/bsps/leon3_qemu.ini

 It's trying to grab the 'html' text so it can trigger the right section
 of code in coverage.py

 It's something just to tell which format we want the report to output
>>>
>>>
>>> Understood , I'll come to that after I manage to get the test running
>>> first .


> TypeError: 'NoneType' object has no attribute '__getitem__'
>
>
> Thanks
>
> -- vijay
>
> On 4 April 2018 at 11:16, Chris Johns  wrote:
>>
>> On 04/04/2018 06:36, Vijay Kumar Banerjee wrote:
>> > after pulling the ini-update branch from
>> > https://github.com/cillianodonnell/rtems-tools/tree/ini-update
>> >
>>
>> Any local changes?
>>
>> > I tried running the rtems-test with the following command
>> >
>> > $HOME/development/rtems/rtems-tools/tester/rtems-test
>> > --rtems-tools=$HOME/development/rtems/5 --log=coverage_analysis.log
>> > --rtems-bsp=leon3_qemu
>> > --rtems-builddir=$HOME/development/rtems/kernel/leon3
>> > sparc-rtems5/c/leon3/testsuites/samples
>> >
>> > was getting the KeyError for 'coverage'
>> >
>>
>> Please paste the command and output as it appears in the terminal?
>>
>> > current status :
>> > the same command gives the error :
>> > "mandatory item not found in bsp section : bsp,"
>> > to make sure I didn't break something , I also tried running from a
>> > freshly
>> > downloaded directory as well, it gives the same error.
>>
>> Did you try running the following command from the top of the source
>> tree:
>>
>>  $ grep -r "mandatory item not found" *
>>
>> ?
>>
>> Chris
>
>
>>>
>
>
> ___
> devel mailing list
> devel@rtems.org
> http://lists.rtems.org/

Re: error while running rtems-test with coverage

[Vijay Kumar Banerjee]

I managed to get the tests running with the following two patches .
Please review them .

-- vijay

On 9 April 2018 at 15:28, Vijay Kumar Banerjee 
wrote:

>
>
> On Fri, 6 Apr 2018, 02:24 Vijay Kumar Banerjee, 
> wrote:
>
>> I tried to solve the empty get in the way shown in the patch , but it
>> doesn't seems to work, I'm getting the following error now
>>
>> RTEMS Testing - Tester, 5 (1ed6e2e64090)
>> Traceback (most recent call last):
>>   File "/home/lunatic/development/rtems/rtems-tools/tester/rtems-test",
>> line 40, in 
>> rt.test.run()
>>   File "/home/lunatic/development/rtems/rtems-tools/tester/rt/test.py",
>> line 303, in run
>> bsp = config.load(bsp[1], opts)
>>   File "/home/lunatic/development/rtems/rtems-tools/tester/rt/config.py",
>> line 461, in load
>> return opts.defaults['bsp']
>>   File "/home/lunatic/development/rtems/rtems-tools/rtemstoolkit/macros.py",
>> line 190, in __getitem__
>> raise IndexError('key: %s' % (key))
>> IndexError: key: bsp
>>
>> I still Couldn't figure out why it's happening, when I use RawConfigParse
> , it seems to run nicely though .
>
> Any Ideas on solving it without using RawConfigParser ?
>
>
>> -- vijay
>>
>> On 5 April 2018 at 11:51, Cillian O'Donnell 
>> wrote:
>>
>>>
>>>
>>> On Wed, 4 Apr 2018, 11:18 Vijay Kumar Banerjee, <
>>> vijaykumar9...@gmail.com> wrote:
>>>
 I got the rtems-test running

 I found that get_item_names(section, err) in configuration.py  was
 returning an empty list to the
 item_names in load(bsp,opts) for config.py this was giving out the
 error mandatory item not found .

 I have attached the patch file .

 current status :
 rtems-test is running without coverage

 running coverage gives the following error :

 RTEMS Testing - Tester, 5 (092c569e81ae)
 Traceback (most recent call last):
   File "/home/lunatic/development/rtems/rtems-tools/tester/rtems-test",
 line 40, in 
 rt.test.run()
   File "/home/lunatic/development/rtems/rtems-tools/tester/rt/test.py",
 line 310, in run
 coverage = coverage_get_obj(opts, path_to_builddir[1])
   File "/home/lunatic/development/rtems/rtems-tools/tester/rt/test.py",
 line 230, in coverage_get_obj
 coverage_obj = coverage.coverage_run(opts.defaults,
 path_to_builddir)
   File "/home/lunatic/development/rtems/rtems-tools/tester/rt/coverage.py",
 line 335, in __init__
 self.report_format = self.config_map['report_format'][2]

>>>
>>> This is back to the difference in cfg formats. It's looking for the last
>>> line here
>>>
>>> https://github.com/cillianodonnell/rtems-tools/
>>> blob/coverage/tester/rtems/testing/bsps/leon3-qemu.mc
>>>
>>> Which is now
>>>
>>> https://github.com/cillianodonnell/rtems-tools/
>>> blob/ini-update/tester/rtems/testing/bsps/leon3_qemu.ini
>>>
>>> It's trying to grab the 'html' text so it can trigger the right section
>>> of code in coverage.py
>>>
>>> It's something just to tell which format we want the report to output
>>>
>>
>> Understood , I'll come to that after I manage to get the test running
>> first .
>>
>>>
>>> TypeError: 'NoneType' object has no attribute '__getitem__'


 Thanks

 -- vijay

 On 4 April 2018 at 11:16, Chris Johns  wrote:

> On 04/04/2018 06:36, Vijay Kumar Banerjee wrote:
> > after pulling the ini-update branch from
> > https://github.com/cillianodonnell/rtems-tools/tree/ini-update
> >
>
> Any local changes?
>
> > I tried running the rtems-test with the following command
> >
> > $HOME/development/rtems/rtems-tools/tester/rtems-test
> > --rtems-tools=$HOME/development/rtems/5 --log=coverage_analysis.log
> > --rtems-bsp=leon3_qemu --rtems-builddir=$HOME/
> development/rtems/kernel/leon3
> > sparc-rtems5/c/leon3/testsuites/samples
> >
> > was getting the KeyError for 'coverage'
> >
>
> Please paste the command and output as it appears in the terminal?
>
> > current status :
> > the same command gives the error :
> > "mandatory item not found in bsp section : bsp,"
> > to make sure I didn't break something , I also tried running from a
> freshly
> > downloaded directory as well, it gives the same error.
>
> Did you try running the following command from the top of the source
> tree:
>
>  $ grep -r "mandatory item not found" *
>
> ?
>
> Chris
>


>>
From 84eefb79fcd5c9abcbfce08995ed410d21e3babe Mon Sep 17 00:00:00 2001
From: thelunatic 
Date: Tue, 10 Apr 2018 16:19:04 +0530
Subject: [PATCH] initial

---
 tester/rt/tftpy/TftpServer.py | 4 ++--
 tester/rt/tftpy/TftpStates.py | 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/tester/rt/tftpy/TftpServer.py b/tester/rt/tftpy/TftpServer.py
index 07c2107..b6d0ada 100644
--- a/tester/rt/tftpy/TftpServer.py
+++ b/tester/rt/tftpy/TftpServer.py
@@ -53,8 +53,8 @@

Re: error while running rtems-test with coverage

[Vijay Kumar Banerjee]

On Fri, 6 Apr 2018, 02:24 Vijay Kumar Banerjee, 
wrote:

> I tried to solve the empty get in the way shown in the patch , but it
> doesn't seems to work, I'm getting the following error now
>
> RTEMS Testing - Tester, 5 (1ed6e2e64090)
> Traceback (most recent call last):
>   File "/home/lunatic/development/rtems/rtems-tools/tester/rtems-test",
> line 40, in 
> rt.test.run()
>   File "/home/lunatic/development/rtems/rtems-tools/tester/rt/test.py",
> line 303, in run
> bsp = config.load(bsp[1], opts)
>   File "/home/lunatic/development/rtems/rtems-tools/tester/rt/config.py",
> line 461, in load
> return opts.defaults['bsp']
>   File
> "/home/lunatic/development/rtems/rtems-tools/rtemstoolkit/macros.py", line
> 190, in __getitem__
> raise IndexError('key: %s' % (key))
> IndexError: key: bsp
>
> I still Couldn't figure out why it's happening, when I use RawConfigParse
, it seems to run nicely though .

Any Ideas on solving it without using RawConfigParser ?


> -- vijay
>
> On 5 April 2018 at 11:51, Cillian O'Donnell  wrote:
>
>>
>>
>> On Wed, 4 Apr 2018, 11:18 Vijay Kumar Banerjee, 
>> wrote:
>>
>>> I got the rtems-test running
>>>
>>> I found that get_item_names(section, err) in configuration.py  was
>>> returning an empty list to the
>>> item_names in load(bsp,opts) for config.py this was giving out the error
>>> mandatory item not found .
>>>
>>> I have attached the patch file .
>>>
>>> current status :
>>> rtems-test is running without coverage
>>>
>>> running coverage gives the following error :
>>>
>>> RTEMS Testing - Tester, 5 (092c569e81ae)
>>> Traceback (most recent call last):
>>>   File "/home/lunatic/development/rtems/rtems-tools/tester/rtems-test",
>>> line 40, in 
>>> rt.test.run()
>>>   File "/home/lunatic/development/rtems/rtems-tools/tester/rt/test.py",
>>> line 310, in run
>>> coverage = coverage_get_obj(opts, path_to_builddir[1])
>>>   File "/home/lunatic/development/rtems/rtems-tools/tester/rt/test.py",
>>> line 230, in coverage_get_obj
>>> coverage_obj = coverage.coverage_run(opts.defaults, path_to_builddir)
>>>   File
>>> "/home/lunatic/development/rtems/rtems-tools/tester/rt/coverage.py", line
>>> 335, in __init__
>>> self.report_format = self.config_map['report_format'][2]
>>>
>>
>> This is back to the difference in cfg formats. It's looking for the last
>> line here
>>
>>
>> https://github.com/cillianodonnell/rtems-tools/blob/coverage/tester/rtems/testing/bsps/leon3-qemu.mc
>>
>> Which is now
>>
>>
>> https://github.com/cillianodonnell/rtems-tools/blob/ini-update/tester/rtems/testing/bsps/leon3_qemu.ini
>>
>> It's trying to grab the 'html' text so it can trigger the right section
>> of code in coverage.py
>>
>> It's something just to tell which format we want the report to output
>>
>
> Understood , I'll come to that after I manage to get the test running
> first .
>
>>
>> TypeError: 'NoneType' object has no attribute '__getitem__'
>>>
>>>
>>> Thanks
>>>
>>> -- vijay
>>>
>>> On 4 April 2018 at 11:16, Chris Johns  wrote:
>>>
 On 04/04/2018 06:36, Vijay Kumar Banerjee wrote:
 > after pulling the ini-update branch from
 > https://github.com/cillianodonnell/rtems-tools/tree/ini-update
 >

 Any local changes?

 > I tried running the rtems-test with the following command
 >
 > $HOME/development/rtems/rtems-tools/tester/rtems-test
 > --rtems-tools=$HOME/development/rtems/5 --log=coverage_analysis.log
 > --rtems-bsp=leon3_qemu
 --rtems-builddir=$HOME/development/rtems/kernel/leon3
 > sparc-rtems5/c/leon3/testsuites/samples
 >
 > was getting the KeyError for 'coverage'
 >

 Please paste the command and output as it appears in the terminal?

 > current status :
 > the same command gives the error :
 > "mandatory item not found in bsp section : bsp,"
 > to make sure I didn't break something , I also tried running from a
 freshly
 > downloaded directory as well, it gives the same error.

 Did you try running the following command from the top of the source
 tree:

  $ grep -r "mandatory item not found" *

 ?

 Chris

>>>
>>>
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: error while running rtems-test with coverage

[Vijay Kumar Banerjee]

I tried to solve the empty get in the way shown in the patch , but it
doesn't seems to work, I'm getting the following error now

RTEMS Testing - Tester, 5 (1ed6e2e64090)
Traceback (most recent call last):
  File "/home/lunatic/development/rtems/rtems-tools/tester/rtems-test",
line 40, in 
rt.test.run()
  File "/home/lunatic/development/rtems/rtems-tools/tester/rt/test.py",
line 303, in run
bsp = config.load(bsp[1], opts)
  File "/home/lunatic/development/rtems/rtems-tools/tester/rt/config.py",
line 461, in load
return opts.defaults['bsp']
  File
"/home/lunatic/development/rtems/rtems-tools/rtemstoolkit/macros.py", line
190, in __getitem__
raise IndexError('key: %s' % (key))
IndexError: key: bsp


-- vijay

On 5 April 2018 at 11:51, Cillian O'Donnell  wrote:

>
>
> On Wed, 4 Apr 2018, 11:18 Vijay Kumar Banerjee, 
> wrote:
>
>> I got the rtems-test running
>>
>> I found that get_item_names(section, err) in configuration.py  was
>> returning an empty list to the
>> item_names in load(bsp,opts) for config.py this was giving out the error
>> mandatory item not found .
>>
>> I have attached the patch file .
>>
>> current status :
>> rtems-test is running without coverage
>>
>> running coverage gives the following error :
>>
>> RTEMS Testing - Tester, 5 (092c569e81ae)
>> Traceback (most recent call last):
>>   File "/home/lunatic/development/rtems/rtems-tools/tester/rtems-test",
>> line 40, in 
>> rt.test.run()
>>   File "/home/lunatic/development/rtems/rtems-tools/tester/rt/test.py",
>> line 310, in run
>> coverage = coverage_get_obj(opts, path_to_builddir[1])
>>   File "/home/lunatic/development/rtems/rtems-tools/tester/rt/test.py",
>> line 230, in coverage_get_obj
>> coverage_obj = coverage.coverage_run(opts.defaults, path_to_builddir)
>>   File "/home/lunatic/development/rtems/rtems-tools/tester/rt/coverage.py",
>> line 335, in __init__
>> self.report_format = self.config_map['report_format'][2]
>>
>
> This is back to the difference in cfg formats. It's looking for the last
> line here
>
> https://github.com/cillianodonnell/rtems-tools/blob/coverage/tester/rtems/
> testing/bsps/leon3-qemu.mc
>
> Which is now
>
> https://github.com/cillianodonnell/rtems-tools/
> blob/ini-update/tester/rtems/testing/bsps/leon3_qemu.ini
>
> It's trying to grab the 'html' text so it can trigger the right section of
> code in coverage.py
>
> It's something just to tell which format we want the report to output
>

Understood , I'll come to that after I manage to get the test running first
.

>
> TypeError: 'NoneType' object has no attribute '__getitem__'
>>
>>
>> Thanks
>>
>> -- vijay
>>
>> On 4 April 2018 at 11:16, Chris Johns  wrote:
>>
>>> On 04/04/2018 06:36, Vijay Kumar Banerjee wrote:
>>> > after pulling the ini-update branch from
>>> > https://github.com/cillianodonnell/rtems-tools/tree/ini-update
>>> >
>>>
>>> Any local changes?
>>>
>>> > I tried running the rtems-test with the following command
>>> >
>>> > $HOME/development/rtems/rtems-tools/tester/rtems-test
>>> > --rtems-tools=$HOME/development/rtems/5 --log=coverage_analysis.log
>>> > --rtems-bsp=leon3_qemu --rtems-builddir=$HOME/
>>> development/rtems/kernel/leon3
>>> > sparc-rtems5/c/leon3/testsuites/samples
>>> >
>>> > was getting the KeyError for 'coverage'
>>> >
>>>
>>> Please paste the command and output as it appears in the terminal?
>>>
>>> > current status :
>>> > the same command gives the error :
>>> > "mandatory item not found in bsp section : bsp,"
>>> > to make sure I didn't break something , I also tried running from a
>>> freshly
>>> > downloaded directory as well, it gives the same error.
>>>
>>> Did you try running the following command from the top of the source
>>> tree:
>>>
>>>  $ grep -r "mandatory item not found" *
>>>
>>> ?
>>>
>>> Chris
>>>
>>
>>
From 1ed6e2e6409041bd9288dab1923ad5a816299086 Mon Sep 17 00:00:00 2001
From: thelunatic 
Date: Fri, 6 Apr 2018 02:11:04 +0530
Subject: [PATCH] setting raw=True in get_item_names

---
 rtemstoolkit/configuration.py | 2 +-
 tester/rt/config.py   | 4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/rtemstoolkit/configuration.py b/rtemstoolkit/configuration.py
index 6917a81..b742227 100644
--- a/rtemstoolkit/configuration.py
+++ b/rtemstoolkit/configuration.py
@@ -121,7 +121,7 @@ class configuration:
 
 try:
 
-return [item[0] for item in self.config.items(section)]
+return [item[0] for item in self.config.items(section,raw=True)]
 except:
 if err:
 raise error.general('config: section "%s" not found' % (section))
diff --git a/tester/rt/config.py b/tester/rt/config.py
index 8c4b5b8..6cfd2f6 100644
--- a/tester/rt/config.py
+++ b/tester/rt/config.py
@@ -427,7 +427,7 @@ def load(bsp, opts):
 if m not in item_names:
 raise error.general('mandatory item not found in bsp section: %s ' % (m))
 opts.defaults.set_write_map(bsp, add = True)
-

Re: error while running rtems-test with coverage

[Cillian O'Donnell]

On Wed, 4 Apr 2018, 11:18 Vijay Kumar Banerjee, 
wrote:

> I got the rtems-test running
>
> I found that get_item_names(section, err) in configuration.py  was
> returning an empty list to the
> item_names in load(bsp,opts) for config.py this was giving out the error
> mandatory item not found .
>
> I have attached the patch file .
>
> current status :
> rtems-test is running without coverage
>
> running coverage gives the following error :
>
> RTEMS Testing - Tester, 5 (092c569e81ae)
> Traceback (most recent call last):
>   File "/home/lunatic/development/rtems/rtems-tools/tester/rtems-test",
> line 40, in 
> rt.test.run()
>   File "/home/lunatic/development/rtems/rtems-tools/tester/rt/test.py",
> line 310, in run
> coverage = coverage_get_obj(opts, path_to_builddir[1])
>   File "/home/lunatic/development/rtems/rtems-tools/tester/rt/test.py",
> line 230, in coverage_get_obj
> coverage_obj = coverage.coverage_run(opts.defaults, path_to_builddir)
>   File
> "/home/lunatic/development/rtems/rtems-tools/tester/rt/coverage.py", line
> 335, in __init__
> self.report_format = self.config_map['report_format'][2]
>

This is back to the difference in cfg formats. It's looking for the last
line here

https://github.com/cillianodonnell/rtems-tools/blob/coverage/tester/rtems/testing/bsps/leon3-qemu.mc

Which is now

https://github.com/cillianodonnell/rtems-tools/blob/ini-update/tester/rtems/testing/bsps/leon3_qemu.ini

It's trying to grab the 'html' text so it can trigger the right section of
code in coverage.py

It's something just to tell which format we want the report to output

TypeError: 'NoneType' object has no attribute '__getitem__'
>
>
> Thanks
>
> -- vijay
>
> On 4 April 2018 at 11:16, Chris Johns  wrote:
>
>> On 04/04/2018 06:36, Vijay Kumar Banerjee wrote:
>> > after pulling the ini-update branch from
>> > https://github.com/cillianodonnell/rtems-tools/tree/ini-update
>> >
>>
>> Any local changes?
>>
>> > I tried running the rtems-test with the following command
>> >
>> > $HOME/development/rtems/rtems-tools/tester/rtems-test
>> > --rtems-tools=$HOME/development/rtems/5 --log=coverage_analysis.log
>> > --rtems-bsp=leon3_qemu
>> --rtems-builddir=$HOME/development/rtems/kernel/leon3
>> > sparc-rtems5/c/leon3/testsuites/samples
>> >
>> > was getting the KeyError for 'coverage'
>> >
>>
>> Please paste the command and output as it appears in the terminal?
>>
>> > current status :
>> > the same command gives the error :
>> > "mandatory item not found in bsp section : bsp,"
>> > to make sure I didn't break something , I also tried running from a
>> freshly
>> > downloaded directory as well, it gives the same error.
>>
>> Did you try running the following command from the top of the source tree:
>>
>>  $ grep -r "mandatory item not found" *
>>
>> ?
>>
>> Chris
>>
>
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: error while running rtems-test with coverage

[Chris Johns]

On 4/4/18 8:18 pm, Vijay Kumar Banerjee wrote:
> I got the rtems-test running 
> 
> I found that get_item_names(section, err) in configuration.py  was returning 
> an
> empty list to the 
> item_names in load(bsp,opts) for config.py this was giving out the error
> mandatory item not found .
> 
> I have attached the patch file .
> 

The patch changes the functionality from interpolated to not interpolated and
that may break other dependent code. Interpolated is desirable for this tool kit
module. Please review:

https://git.rtems.org/rtems-tools/tree/rtemstoolkit/configuration.py#n79

This builds on the basic interpolation in python 3 for 2.7 so the module is
consistent.

Can you handle an empty list where the call is made?

Chris
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: error while running rtems-test with coverage

[Vijay Kumar Banerjee]

I got the rtems-test running

I found that get_item_names(section, err) in configuration.py  was
returning an empty list to the
item_names in load(bsp,opts) for config.py this was giving out the error
mandatory item not found .

I have attached the patch file .

current status :
rtems-test is running without coverage

running coverage gives the following error :

RTEMS Testing - Tester, 5 (092c569e81ae)
Traceback (most recent call last):
  File "/home/lunatic/development/rtems/rtems-tools/tester/rtems-test",
line 40, in 
rt.test.run()
  File "/home/lunatic/development/rtems/rtems-tools/tester/rt/test.py",
line 310, in run
coverage = coverage_get_obj(opts, path_to_builddir[1])
  File "/home/lunatic/development/rtems/rtems-tools/tester/rt/test.py",
line 230, in coverage_get_obj
coverage_obj = coverage.coverage_run(opts.defaults, path_to_builddir)
  File "/home/lunatic/development/rtems/rtems-tools/tester/rt/coverage.py",
line 335, in __init__
self.report_format = self.config_map['report_format'][2]
TypeError: 'NoneType' object has no attribute '__getitem__'


Thanks

-- vijay

On 4 April 2018 at 11:16, Chris Johns  wrote:

> On 04/04/2018 06:36, Vijay Kumar Banerjee wrote:
> > after pulling the ini-update branch from
> > https://github.com/cillianodonnell/rtems-tools/tree/ini-update
> >
>
> Any local changes?
>
> > I tried running the rtems-test with the following command
> >
> > $HOME/development/rtems/rtems-tools/tester/rtems-test
> > --rtems-tools=$HOME/development/rtems/5 --log=coverage_analysis.log
> > --rtems-bsp=leon3_qemu --rtems-builddir=$HOME/
> development/rtems/kernel/leon3
> > sparc-rtems5/c/leon3/testsuites/samples
> >
> > was getting the KeyError for 'coverage'
> >
>
> Please paste the command and output as it appears in the terminal?
>
> > current status :
> > the same command gives the error :
> > "mandatory item not found in bsp section : bsp,"
> > to make sure I didn't break something , I also tried running from a
> freshly
> > downloaded directory as well, it gives the same error.
>
> Did you try running the following command from the top of the source tree:
>
>  $ grep -r "mandatory item not found" *
>
> ?
>
> Chris
>
From 092c569e81ae9362828e6a9a464fbf6a72d49981 Mon Sep 17 00:00:00 2001
From: thelunatic 
Date: Wed, 4 Apr 2018 14:45:38 +0530
Subject: [PATCH] configuration RawConfigParser

---
 rtemstoolkit/configuration.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/rtemstoolkit/configuration.py b/rtemstoolkit/configuration.py
index e3f8b79..2047ba1 100644
--- a/rtemstoolkit/configuration.py
+++ b/rtemstoolkit/configuration.py
@@ -48,7 +48,7 @@ from rtemstoolkit import path
 class configuration:
 
 def __init__(self):
-self.config = configparser.ConfigParser()
+self.config = configparser.RawConfigParser()
 self.ini = None
 self.macro_filter = re.compile('\$\{.+\}')
 
-- 
2.14.3

___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: error while running rtems-test with coverage

[Chris Johns]

On 04/04/2018 06:36, Vijay Kumar Banerjee wrote:
> after pulling the ini-update branch from 
> https://github.com/cillianodonnell/rtems-tools/tree/ini-update
> 

Any local changes?

> I tried running the rtems-test with the following command
> 
> $HOME/development/rtems/rtems-tools/tester/rtems-test
> --rtems-tools=$HOME/development/rtems/5 --log=coverage_analysis.log
> --rtems-bsp=leon3_qemu --rtems-builddir=$HOME/development/rtems/kernel/leon3
> sparc-rtems5/c/leon3/testsuites/samples
> 
> was getting the KeyError for 'coverage'
>

Please paste the command and output as it appears in the terminal?

> current status : 
> the same command gives the error : 
> "mandatory item not found in bsp section : bsp," 
> to make sure I didn't break something , I also tried running from a freshly
> downloaded directory as well, it gives the same error.

Did you try running the following command from the top of the source tree:

 $ grep -r "mandatory item not found" *

?

Chris
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

error while running rtems-test with coverage

[Vijay Kumar Banerjee]

after pulling the ini-update branch from
https://github.com/cillianodonnell/rtems-tools/tree/ini-update

I tried running the rtems-test with the following command

$HOME/development/rtems/rtems-tools/tester/rtems-test
--rtems-tools=$HOME/development/rtems/5 --log=coverage_analysis.log
--rtems-bsp=leon3_qemu
--rtems-builddir=$HOME/development/rtems/kernel/leon3
sparc-rtems5/c/leon3/testsuites/samples

was getting the KeyError for 'coverage'

current status :
the same command gives the error :
"mandatory item not found in bsp section : bsp,"
to make sure I didn't break something , I also tried running from a freshly
downloaded directory as well, it gives the same error.

-- vijay
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel