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 ha
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
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 s
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 co
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
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, C
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, V
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:4
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
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 -s
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 -moni
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'
-- 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
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)
>
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)
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/r
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
"/
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
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.
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
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 unle
-- 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 i
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'Donnel
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 leon
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
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
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 f
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
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
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 20
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 gu
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
> co
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
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
WARNIN
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 .
>
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
>> d
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/dev
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.t
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 .
>
>
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
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 runni
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-tes
42 matches
Mail list logo
