Hello,
I have added the following changes in the bsps/sparc/leon3/config/leon3.cfg
--
CFLAGS_OPTIMIZE_V = -Os -g
CFLAGS_OPTIMIZE_V += -ftest-coverage
---
While trying to build with these flags, I got a bunch of
the following errors:
==
{standard input}: Assembler messages:
On 6 June 2018 at 17:48, Joel Sherrill wrote:
>
>
> On Wed, Jun 6, 2018, 1:16 AM Cillian O'Donnell
> wrote:
>
>>
>>
>> On Wed, 6 Jun 2018, 01:52 Joel Sherrill, wrote:
>>
>>>
>>>
>>> On Tue, Jun 5, 2018, 7:22 PM Vijay Kumar Baner
On Wed, 6 Jun 2018, 08:31 Joel Sherrill, wrote:
>
>
> On Tue, Jun 5, 2018, 9:54 PM Chris Johns wrote:
>
>>
>> On 31/5/18 6:44 am, Vijay Kumar Banerjee wrote:
>> > On 31 May 2018 at 02:02, Joel Sherrill > j...@rtems.org>>
>> > wrote:
>> &g
On Wed, 6 Jun 2018, 06:22 Joel Sherrill, wrote:
>
>
> On Tue, Jun 5, 2018, 7:22 PM Vijay Kumar Banerjee <
> vijaykumar9...@gmail.com> wrote:
>
>> On 6 June 2018 at 03:57, Joel Sherrill wrote:
>>
>>> I think everything is pushed. Is there a
On 6 June 2018 at 03:57, Joel Sherrill wrote:
> I think everything is pushed. Is there any patch outstanding?
>
> Thank you.
No outstanding patch, everything on my side is squashed into it. :)
> On Mon, Jun 4, 2018 at 3:44 PM, Vijay Kumar Banerjee <
> vijaykumar9...@gmail.co
Add support in tester to run covoar and generate an html report to display
the summary of the coverage reports generated from covoar.
Co-authored-by : Cillian O'Donnell
---
.gitignore| 1 +
tester/rt/coverage.py | 385
On 5 June 2018 at 01:28, Cillian O'Donnell wrote:
>
>
> On 4 June 2018 at 20:29, Vijay Kumar Banerjee
> wrote:
>
>> On 5 June 2018 at 00:51, Joel Sherrill wrote:
>>
>>>
>>>
>>> On Mon, Jun 4, 2018 at 2:12 PM, Vijay Kumar Banerjee <
>
On 5 June 2018 at 00:51, Joel Sherrill wrote:
>
>
> On Mon, Jun 4, 2018 at 2:12 PM, Vijay Kumar Banerjee <
> vijaykumar9...@gmail.com> wrote:
>
>> On 5 June 2018 at 00:31, Joel Sherrill wrote:
>>
>>> I will add that covoar was originally design
needed. If we're headed in that way
then I think making separate report.html like leon3-report.html would be
simpler
to achieve, and then create a master index.html for listing all the report
htmls.
>
> On Mon, Jun 4, 2018 at 1:43 PM, Cillian O'Donnell
> wrote:
>
>>
>>
>
On 2 June 2018 at 01:00, Vijay Kumar Banerjee
wrote:
> On 2 June 2018 at 00:48, Joel Sherrill wrote:
>
>>
>>
>> On Fri, Jun 1, 2018, 11:21 AM Vijay Kumar Banerjee <
>> vijaykumar9...@gmail.com> wrote:
>>
>>> On 1 June 2018 at 20:30, Gedare Blo
On 2 June 2018 at 00:48, Joel Sherrill wrote:
>
>
> On Fri, Jun 1, 2018, 11:21 AM Vijay Kumar Banerjee <
> vijaykumar9...@gmail.com> wrote:
>
>> On 1 June 2018 at 20:30, Gedare Bloom wrote:
>>
>>> On Fri, Jun 1, 2018 at 10:28 AM, Vijay Kumar Banerjee
On 1 June 2018 at 20:30, Gedare Bloom wrote:
> On Fri, Jun 1, 2018 at 10:28 AM, Vijay Kumar Banerjee
> wrote:
> > On 1 June 2018 at 19:24, Joel Sherrill wrote:
> >>
> >>
> >>
> >> On Fri, Jun 1, 2018 at 2:46 AM, Vijay Kumar Banerjee
&
On 1 June 2018 at 19:24, Joel Sherrill wrote:
>
>
> On Fri, Jun 1, 2018 at 2:46 AM, Vijay Kumar Banerjee <
> vijaykumar9...@gmail.com> wrote:
>
>> Here's the list of Ideas for improvements:
>>
>> 1. Include the section coverage in the bsp config f
rt of your GSoC.
>
> --joel
>
> On Thu, May 31, 2018 at 5:18 PM, Vijay Kumar Banerjee <
> vijaykumar9...@gmail.com> wrote:
>
>>
>>
>> On Fri, 1 Jun 2018, 03:40 Joel Sherrill, wrote:
>>
>>>
>>>
>>> On Thu, May 31, 2018 at 4:57
On Fri, 1 Jun 2018, 03:40 Joel Sherrill, wrote:
>
>
> On Thu, May 31, 2018 at 4:57 PM, Vijay Kumar Banerjee <
> vijaykumar9...@gmail.com> wrote:
>
>> On 1 June 2018 at 02:50, Joel Sherrill wrote:
>>
>>>
>>>
>>> On Thu, May 31, 20
On 1 June 2018 at 02:50, Joel Sherrill wrote:
>
>
> On Thu, May 31, 2018 at 4:15 PM, Cillian O'Donnell
> wrote:
>
>>
>>
>> On Thu, 31 May 2018, 22:03 Vijay Kumar Banerjee, <
>> vijaykumar9...@gmail.com> wrote:
>>
>>> On 1 June 2018 a
> sets, probably renamed to --coverage-sets=... Or require sets to be
> chosen
> > --coverage-sets=all or specific sets --coverage-sets=score,sapi,core
> >
> Yes, and it should work for more than 1 or 2.
>
> It can work for any number of sets.
> > On Thu, 31 May 2018,
Thu, 31 May 2018, 21:29 Vijay Kumar Banerjee,
> wrote:
>
>> On 1 June 2018 at 01:57, Cillian O'Donnell wrote:
>>
>>> So is it checking whether it's --coverage or --coverage=set1,set2? Are
>>> those the 2 possibilities your checking?
>>>
>>
On 1 June 2018 at 01:19, Gedare Bloom wrote:
> On Thu, May 31, 2018 at 3:47 PM, Vijay Kumar Banerjee
> wrote:
> > On 1 June 2018 at 01:07, Cillian O'Donnell
> wrote:
> >>
> >>
> >>
> >> On 31 May 2018 at 19:07, Vijay Kumar Banerjee >
>
On 1 June 2018 at 01:07, Cillian O'Donnell wrote:
>
>
> On 31 May 2018 at 19:07, Vijay Kumar Banerjee
> wrote:
>
>> Add support in tester to run covoar and generate an html report to display
>> the summary of the coverage reports generated from covoar.
>>
>
Add support in tester to run covoar and generate an html report to display
the summary of the coverage reports generated from covoar.
Co-authored-by : Cillian O'Donnell
---
tester/rt/coverage.py | 379 ++
tester/rt/test.py
Hello,
The covoar currently is capable of processing multisets
from the symbol-sets ini file, however, it currently keeps
all the reports in the same directory (../coverage/score).
Before the recent updates to covoar it could only read
one set/subsystem from an ini file, and the script used
to
On 31 May 2018 at 02:02, Joel Sherrill wrote:
>
>
> On Wed, May 30, 2018 at 3:29 PM, Vijay Kumar Banerjee <
> vijaykumar9...@gmail.com> wrote:
>
>> On 31 May 2018 at 00:28, Joel Sherrill wrote:
>>
>>>
>>>
>>> I may not understand c
On 31 May 2018 at 00:28, Joel Sherrill wrote:
>
>
> I may not understand correctly but there is test_run and coverage_run.
> Someone
> suggested making coverage_running an option to test_run. If that's what's
> being
> asked for, then I think doing it in a follow up patch is OK.
>
> If that's
On 30 May 2018 at 23:29, Joel Sherrill wrote:
>
>
> On Wed, May 30, 2018 at 12:54 PM, Vijay Kumar Banerjee <
> vijaykumar9...@gmail.com> wrote:
>
>> On 30 May 2018 at 22:51, Gedare Bloom wrote:
>>
>>> Please provide your name in your commits (git
On 30 May 2018 at 22:51, Gedare Bloom wrote:
> > +def coverage_run(opts, coverage, executables):
> > +coverage.executables = executables
> > +coverage.run()
> > +
> > def run(command_path = None):
> > import sys
> > tests = []
> > @@ -221,15 +228,16 @@ def run(command_path =
On 30 May 2018 at 22:51, Gedare Bloom wrote:
> Please provide your name in your commits (git config --user.name "My
> Name") that you submit.
>
> OK Noted :)
> The first line of this commit, and therefore the email subject, is
> overly vague. Provide a slightly more specific description.
>
On
On 30 May 2018 at 22:55, Cillian O'Donnell wrote:
>
>
> On Wed, 30 May 2018, 18:15 Vijay Kumar Banerjee,
> wrote:
>
>>
>>
>> On Wed, 30 May 2018, 22:42 Cillian O'Donnell,
>> wrote:
>>
>>>
>>>
>>> On Wed, 30 May 2018, 16:5
On Wed, 30 May 2018, 22:42 Cillian O'Donnell, wrote:
>
>
> On Wed, 30 May 2018, 16:58 Gedare Bloom, wrote:
>
>> On Wed, May 30, 2018 at 11:32 AM, Vijay Kumar Banerjee
>> wrote:
>> > On 30 May 2018 at 20:18, Gedare Bloom wrote:
>> >>
>> >&
d, May 30, 2018 at 10:29 AM, Vijay Kumar Banerjee
> wrote:
> > On 30 May 2018 at 00:54, Joel Sherrill wrote:
> >>
> >>
> >>
> >> On Tue, May 29, 2018 at 11:27 AM, Vijay Kumar Banerjee
> >> wrote:
> >>>
> >>>
> >
On 30 May 2018 at 00:54, Joel Sherrill wrote:
>
>
> On Tue, May 29, 2018 at 11:27 AM, Vijay Kumar Banerjee <
> vijaykumar9...@gmail.com> wrote:
>
>>
>>
>> On Tue, 29 May 2018, 20:10 Joel Sherrill, wrote:
>>
>>>
>>>
>>> On
On 28 May 2018 at 00:49, Joel Sherrill wrote:
> It sounds like great progress is being made but this thread is very long
> and I am losing track of what needs committing.
>
> We can start a new thread. :)
> Plus there is Chris' work to merge as well.
>
> How close is everything
On Mon, 28 May 2018, 00:32 Cillian O'Donnell, <cpodonne...@gmail.com> wrote:
>
>
> On Sun, 27 May 2018, 19:59 Vijay Kumar Banerjee, <vijaykumar9...@gmail.com>
> wrote:
>
>> Hello,
>>
>> The support for letting users input specific symbols
>>
Hello,
The support for letting users input specific symbols
for coverage analysis is now working in my
cov-tester-support branch
https://github.com/thelunatic/rtems-tools/tree/cov-tester-support
Please have a look into the code and test it.
The user can input specific symbols with the
On Fri, 25 May 2018, 09:26 Vijay Kumar Banerjee, <vijaykumar9...@gmail.com>
wrote:
>
>
> On Fri, 25 May 2018, 02:52 Chris Johns, <ch...@contemporary.net.au> wrote:
>
>> On 25/5/18 7:11 am, Vijay Kumar Banerjee wrote:
>> > On Fri, 25 May 2018, 00:35 Joel S
On Fri, 25 May 2018, 02:52 Chris Johns, <ch...@contemporary.net.au> wrote:
> On 25/5/18 7:11 am, Vijay Kumar Banerjee wrote:
> > On Fri, 25 May 2018, 00:35 Joel Sherrill, <j...@rtems.org
> > <mailto:j...@rtems.org>> wrote:
> > On Thu, May
On Fri, 25 May 2018, 00:35 Joel Sherrill, <j...@rtems.org> wrote:
>
>
> On Thu, May 24, 2018, 10:43 AM Vijay Kumar Banerjee <
> vijaykumar9...@gmail.com> wrote:
>
>> On 24 May 2018 at 18:58, Vijay Kumar Banerjee <vijaykumar9...@gmail.com>
>> wrote:
On 24 May 2018 at 18:58, Vijay Kumar Banerjee <vijaykumar9...@gmail.com>
wrote:
> On 24 May 2018 at 18:21, Gedare Bloom <ged...@rtems.org> wrote:
>
>> Vijay,
>>
>> Please test Chris' modifications.
>>
>> On Thu, May 24, 2018 at 2:23 AM, Chris John
On 22 May 2018 at 00:33, Joel Sherrill <j...@rtems.org> wrote:
>
>
> On Mon, May 21, 2018, 1:54 PM Vijay Kumar Banerjee <
> vijaykumar9...@gmail.com> wrote:
>
>> On 21 May 2018 at 23:07, Joel Sherrill <j...@rtems.org> wrote:
>>
>>>
>&
On 21 May 2018 at 23:07, Joel Sherrill <j...@rtems.org> wrote:
>
>
> On Mon, May 21, 2018, 12:01 PM Vijay Kumar Banerjee <
> vijaykumar9...@gmail.com> wrote:
>
>> On 21 May 2018 at 21:42, Joel Sherrill <j...@rtems.org> wrote:
>>
>>>
>>
On 21 May 2018 at 21:42, Joel Sherrill <j...@rtems.org> wrote:
>
>
> On Mon, May 21, 2018 at 10:13 AM, Vijay Kumar Banerjee <
> vijaykumar9...@gmail.com> wrote:
>
>> On 21 May 2018 at 20:37, Joel Sherrill <j...@rtems.org> wrote:
>>
>>>
>>
On 21 May 2018 at 20:37, Joel Sherrill <j...@rtems.org> wrote:
>
>
> On Mon, May 21, 2018 at 9:52 AM, Vijay Kumar Banerjee <
> vijaykumar9...@gmail.com> wrote:
>
>> On 21 May 2018 at 17:39, Joel Sherrill <j...@rtems.org> wrote:
>>
>>>
gt; On Mon, May 21, 2018, 6:35 AM Cillian O'Donnell <cpodonne...@gmail.com>
> wrote:
>
>>
>>
>> On Mon, 21 May 2018, 12:18 Vijay Kumar Banerjee, <
>> vijaykumar9...@gmail.com> wrote:
>>
>>> On 21 May 2018 at 16:39, Cillian O'Donnell &
On 21 May 2018 at 16:39, Cillian O'Donnell <cpodonne...@gmail.com> wrote:
>
>
> On Mon, 21 May 2018, 12:08 Cillian O'Donnell, <cpodonne...@gmail.com>
> wrote:
>
>>
>>
>> On Mon, 21 May 2018, 11:49 Vijay Kumar Banerjee, <
>> vijaykumar9...@gma
On 21 May 2018 at 11:56, Cillian O'Donnell <cpodonne...@gmail.com> wrote:
>
>
> On Sun, 20 May 2018, 22:33 Vijay Kumar Banerjee, <vijaykumar9...@gmail.com>
> wrote:
>
>> On 21 May 2018 at 02:29, Cillian O'Donnell <cpodonne...@gmail.com> wrote:
>>
>&
On 21 May 2018 at 02:29, Cillian O'Donnell <cpodonne...@gmail.com> wrote:
>
>
> On Sun, 20 May 2018, 15:35 Vijay Kumar Banerjee, <vijaykumar9...@gmail.com>
> wrote:
>
>> On 20 May 2018 at 00:53, Vijay Kumar Banerjee <vijaykumar9...@gmail.com>
>> wro
On 20 May 2018 at 00:53, Vijay Kumar Banerjee <vijaykumar9...@gmail.com>
wrote:
>
>
> On Sun, 20 May 2018, 00:45 Cillian O'Donnell, <cpodonne...@gmail.com>
> wrote:
>
>> It works.. Sorry I was using the right covoar but the wrong rtems-test.
>> Ahh its n
On Sun, 20 May 2018, 01:56 Cillian O'Donnell, <cpodonne...@gmail.com> wrote:
>
>
> On Sat, 19 May 2018, 20:59 Vijay Kumar Banerjee, <vijaykumar9...@gmail.com>
> wrote:
>
>> Hello,
>>
>> My end sem exams are starting next week from 22nd May and w
Hello,
My end sem exams are starting next week from 22nd May and will go till 31st
May. During this period I will be less efficient.
I understand that the project is in a crucial state and 10 days of
inactivity is unacceptable so I will try my best to be as active as
possible during the gaps
On Sun, 20 May 2018, 00:45 Cillian O'Donnell, wrote:
> It works.. Sorry I was using the right covoar but the wrong rtems-test.
> Ahh its nice to see the data back in the reports again. Did you manage to
> track down 2 exes with the mismatch in symbol size?
>
Great! so next
On 19 May 2018 at 18:28, Cillian O'Donnell <cpodonne...@gmail.com> wrote:
>
>
> On Sat, 19 May 2018, 13:28 Vijay Kumar Banerjee, <vijaykumar9...@gmail.com>
> wrote:
>
>> On 19 May 2018 at 17:56, Vijay Kumar Banerjee <vijaykumar9...@gmail.com>
>> wrote
On 19 May 2018 at 17:56, Vijay Kumar Banerjee <vijaykumar9...@gmail.com>
wrote:
> On 19 May 2018 at 17:50, Vijay Kumar Banerjee <vijaykumar9...@gmail.com>
> wrote:
>
>> On 19 May 2018 at 17:44, Cillian O'Donnell <cpodonne...@gmail.com> wrote:
>>
>>>
On 19 May 2018 at 17:50, Vijay Kumar Banerjee <vijaykumar9...@gmail.com>
wrote:
> On 19 May 2018 at 17:44, Cillian O'Donnell <cpodonne...@gmail.com> wrote:
>
>>
>>
>> On Sat, 19 May 2018, 12:28 Vijay Kumar Banerjee, <
>> vijaykumar9...@gmail.com>
On 19 May 2018 at 16:47, Cillian O'Donnell wrote:
>
> God these messages again... at least I'm an expert in fixing these :)
> Vijay I'm only seeing the headings in the report on my end using your
> branch. How are you running it and from where? Is there any changes you
>
On 19 May 2018 at 04:26, Joel Sherrill wrote:
> If you run nm on some of the executables, do you see the
> Is symbol? We need to.know its type.
>
I did this on the testsuites
find -iname '*.exe' -exec nm -A '{}' \; | grep '\'
which returned nothing .
am I using the right
On 19 May 2018 at 03:29, Joel Sherrill <j...@rtems.org> wrote:
>
>
> On Fri, May 18, 2018 at 4:53 PM, Vijay Kumar Banerjee <
> vijaykumar9...@gmail.com> wrote:
>
>>
>>
>> On Sat, 19 May 2018, 03:06 Joel Sherrill, <j...@rtems.org> wrote:
>>
On Sat, 19 May 2018, 03:06 Joel Sherrill, <j...@rtems.org> wrote:
>
>
> On Fri, May 18, 2018 at 4:01 PM, Vijay Kumar Banerjee <
> vijaykumar9...@gmail.com> wrote:
>
>> On 19 May 2018 at 02:29, Vijay Kumar Banerjee <vijaykumar9...@gmail.com>
>> w
On 19 May 2018 at 02:29, Vijay Kumar Banerjee <vijaykumar9...@gmail.com>
wrote:
> On 19 May 2018 at 01:30, Cillian O'Donnell <cpodonne...@gmail.com> wrote:
>
>>
>>
>> On Fri, 18 May 2018, 14:55 Vijay Kumar Banerjee, <
>> vijaykumar9...@gmail.com&g
On 19 May 2018 at 01:30, Cillian O'Donnell <cpodonne...@gmail.com> wrote:
>
>
> On Fri, 18 May 2018, 14:55 Vijay Kumar Banerjee, <vijaykumar9...@gmail.com>
> wrote:
>
>>
>>
>> On 18 May 2018 at 19:09, Cillian O'Donnell <cpodonne...@gmail.com> wro
On 18 May 2018 at 19:09, Cillian O'Donnell <cpodonne...@gmail.com> wrote:
>
>
> On Fri, 18 May 2018, 12:36 Vijay Kumar Banerjee, <vijaykumar9...@gmail.com>
> wrote:
>
>>
>> On 18 May 2018 at 12:30, Cillian O'Donnell <cpodonne...@gmail.com> wrote:
&
On 18 May 2018 at 12:30, Cillian O'Donnell wrote:
> Cool, you should run it for the full testsuite and take a look at that
> report (takes a while.. around 575 tests)
>
>>
>>> When I try to run the full testsuites it gives the following error .
What could be causing this
On Fri, 18 May 2018, 11:52 Cillian O'Donnell, <cpodonne...@gmail.com> wrote:
>
>
> On Thu, 17 May 2018, 21:32 Vijay Kumar Banerjee, <vijaykumar9...@gmail.com>
> wrote:
>
>> hello,
>>
>> I have attached the html report !
>>
>
> Report looks
hello,
I have attached the html report !
Well it looks good but I hardcoded the paths, at least that gave the proper
idea of what exactly needs to be done. Now I understand why
--rtems-builddir stayed there for a long time , it makes the job simple .
Here's a point that needs discussion :
1.
Current status: The gcno files are needed to pass it as an argument to
covoar to generate the gcov reports.
the generation of the gcno file needs changing the gcc flags .
reference link :
https://gcc.gnu.org/onlinedocs/gcc/Gcov-Data-Files.html#Gcov-Data-Files
-- vijay
On 14 May 2018 at 23:37, Joel Sherrill <j...@rtems.org> wrote:
>
>
> On Mon, May 14, 2018 at 12:43 PM, Vijay Kumar Banerjee <
> vijaykumar9...@gmail.com> wrote:
>
>> On 14 May 2018 at 21:21, Joel Sherrill <j...@rtems.org> wrote:
>>
>>>
On Mon, 14 May 2018, 23:24 Cillian O'Donnell, <cpodonne...@gmail.com> wrote:
>
>
> On Mon, 14 May 2018, 09:50 Vijay Kumar Banerjee, <vijaykumar9...@gmail.com>
> wrote:
>
>> On 14 May 2018 at 12:10, Cillian O'Donnell <cpodonne...@gmail.com> wrote:
>>
On 14 May 2018 at 21:21, Joel Sherrill <j...@rtems.org> wrote:
>
>
> On Mon, May 14, 2018 at 10:19 AM, Vijay Kumar Banerjee <
> vijaykumar9...@gmail.com> wrote:
>
>> Hello,
>>
>> The coverage report is showing some data now (txt only). There is still
Hello,
The coverage report is showing some data now (txt only). There is still
some work needed to be done for it to get merged with the main repo. As it
depends on the ongoing work on the covoar.cc and coverage.py, meanwhile I
want to get started with the gcov support in covoar as I already have
On 14 May 2018 at 12:10, Cillian O'Donnell <cpodonne...@gmail.com> wrote:
>
>
> On Sun, 13 May 2018, 22:15 Vijay Kumar Banerjee, <vijaykumar9...@gmail.com>
> wrote:
>
>> On 14 May 2018 at 02:15, Cillian O'Donnell <cpodonne...@gmail.com> wrote:
>&
On 14 May 2018 at 02:15, Cillian O'Donnell wrote:
> ---
> tester/covoar/covoar.cc | 10 +++---
> 1 file changed, 3 insertions(+), 7 deletions(-)
>
> diff --git a/tester/covoar/covoar.cc b/tester/covoar/covoar.cc
> index 5c87402..c6b0589 100644
> ---
On 13 May 2018 at 21:05, Gedare Bloom wrote:
> Probably this is because rtems-sparc5 does not have a . in it like
> rtems-sparc4.11
>
>
> Does that really make the difference ?
it is parsed by covoar/DesiredSymbols.cc , it just simply replaces the
@BUILD-TARGET@ with the
On 13 May 2018 at 19:00, Cillian O'Donnell wrote:
> Is there supposed to be a message there?
>
> Anyway just to clear this up, try this for me.
>
> 1. Grab a new branch of
>
> https://github.com/cillianodonnell/rtems-tools/tree/tester-support
>
> which is the current
On Sun, 13 May 2018, 18:24 Cillian O'Donnell, <cpodonne...@gmail.com> wrote:
>
>
> On 13 May 2018 at 13:47, Vijay Kumar Banerjee <vijaykumar9...@gmail.com>
> wrote:
>
>>
>> On Sun, 13 May 2018, 18:14 Cillian O'Donnell, <cpodonne...@gmail.com>
>
On Sun, 13 May 2018, 18:24 Cillian O'Donnell, <cpodonne...@gmail.com> wrote:
>
>
> On 13 May 2018 at 13:47, Vijay Kumar Banerjee <vijaykumar9...@gmail.com>
> wrote:
>
>>
>> On Sun, 13 May 2018, 18:14 Cillian O'Donnell, <cpodonne...@gmail.com>
>
not
> quite right but that's just collaborative development, you'll have to get
> used to it :)...
>
That's alright. :)
>
> On 13 May 2018 at 12:39, Vijay Kumar Banerjee <vijaykumar9...@gmail.com>
> wrote:
>
>>
>>
>> On Sun, 13 May 2018, 17:02 Cillian O'Donnell,
find results in
> /home/cpod/development/rtems/leon3
> ***Cleaning tempfiles***
>
> So there does seem to be some knock on effect of just tacking on .cov
> there. Can't see all the consequences immediately but I'm having a look
> now. I'll let you know if I find anything.
>
>
>
On 13 May 2018 at 16:16, Vijay Kumar Banerjee <vijaykumar9...@gmail.com>
wrote:
>
>
> On Sun, 13 May 2018, 16:15 Vijay Kumar Banerjee, <vijaykumar9...@gmail.com>
> wrote:
>
>>
>>
>> On Sun, 13 May 2018, 16:09 Cillian O'Donnell, <cpodonne...@gmail
On Sun, 13 May 2018, 16:15 Vijay Kumar Banerjee, <vijaykumar9...@gmail.com>
wrote:
>
>
> On Sun, 13 May 2018, 16:09 Cillian O'Donnell, <cpodonne...@gmail.com>
> wrote:
>
>> It does seem to be having some knock on effect. Covoar made it past these
>> checks b
On 13 May 2018 at 10:50, Chris Johns <chr...@rtems.org> wrote:
> On 13/5/18 4:44 pm, Vijay Kumar Banerjee wrote:
> > On Sun, 13 May 2018, 10:09 Chris Johns, <chr...@rtems.org
> > <mailto:chr...@rtems.org>> wrote:
> > >
> > >
On 11 May 2018 at 11:50, Cillian O'Donnell wrote:
> At the moment when the tester runs covoar the error messages generated are
> a clear indicator of what is wrong, so task list is dictated by what
> they're saying at the moment. Fixing the mismatch between exe.cov and
y 11, 2018 at 1:37 PM, Vijay Kumar Banerjee <
> vijaykumar9...@gmail.com> wrote:
>
>>
>>
>> On Fri, 11 May 2018, 23:59 Danxue Huang, <danxue.hu...@gmail.com> wrote:
>>
>>> Hey Vijay,
>>>
>>> Thank you so much for answering my ques
to run hello world ?
>
> Best,
> Dannie
>
> On Fri, May 11, 2018 at 12:57 PM, Vijay Kumar Banerjee <
> vijaykumar9...@gmail.com> wrote:
>
>>
>> Hello Dannie,
>>
>> I guess you're looking for the testsuites direcotry under the build
>> d
Hello Dannie,
I guess you're looking for the testsuites direcotry under the build
directory.
It can be found somewhere like this
$HOME/development/rtems/kernel/erc32/sparc-rtems5/c/erc32/testsuites
If you're looking for the c code then you can find it under the RTEMS_ROOT
directory.
In my set
On Fri, 11 May 2018, 02:19 Cillian O'Donnell, <cpodonne...@gmail.com> wrote:
>
>
> On 10 May 2018 at 20:15, Vijay Kumar Banerjee <vijaykumar9...@gmail.com>
> wrote:
>
>> Frankly, I'm totally confused at the moment. I'm not able to come up with
>> a
On Fri, 11 May 2018, 01:09 Joel Sherrill, <j...@rtems.org> wrote:
>
>
> On Thu, May 10, 2018 at 2:15 PM, Vijay Kumar Banerjee <
> vijaykumar9...@gmail.com> wrote:
>
>> Frankly, I'm totally confused at the moment. I'm not able to come up with
>> a proper task
On 11 May 2018 at 00:09, Chris Johns wrote:
> On 11/5/18 5:37 am, Cillian O'Donnell wrote:
> > On Thu, 10 May 2018, 11:48 Chris Johns, >
> > It is not a exception in an exception or in a stack unwind path, it
> is an
> > exception being thrown with
Frankly, I'm totally confused at the moment. I'm not able to come up with a
proper task list to serially go through.
according to my understanding (and proposal), the major goals are:
1. Get the coverage analysis running again and get it merged with the
current master repo.
2. Generating line
On 8 May 2018 at 00:33, Cillian O'Donnell wrote:
> Here's the branch with work in progress for the tester. Have a look when
> you can Vijay.
>
> https://github.com/cillianodonnell/rtems-tools/tree/tester-support
>
>
> I am going through this now.
according to your last
imple. We just need to hear from Chris.
>
> --joel
>
This will hopefully fix it, unfortunately I can't test it now, as I'm on
mobile. Hopefully Cillian can try building with the diff applied.
>
>
> On Mon, May 7, 2018 at 12:42 PM, Joel Sherrill <j...@rtems.org> wrote:
>
>
8 at 15:40, Joel Sherrill <j...@rtems.org> wrote:
>
>>
>>
>> On Mon, May 7, 2018 at 6:01 AM, Vijay Kumar Banerjee <
>> vijaykumar9...@gmail.com> wrote:
>>
>>> I have added the path to libdwarf here
>>>
>>
On Mon, 7 May 2018, 20:10 Joel Sherrill, <j...@rtems.org> wrote:
>
>
> On Mon, May 7, 2018 at 6:01 AM, Vijay Kumar Banerjee <
> vijaykumar9...@gmail.com> wrote:
>
>> I have added the path to libdwarf here
>>
>
> That worked for me to build but not
2018 at 13:30, Vijay Kumar Banerjee <vijaykumar9...@gmail.com>
wrote:
>
> On 6 May 2018 at 13:29, Chris Johns <chr...@rtems.org> wrote:
>
>> On 6/5/18 5:28 pm, Vijay Kumar Banerjee wrote:
>>
>>> On 6 May 2018 at 08:54, Chris Johns <chr...@rtems.org >&
On 6 May 2018 at 13:29, Chris Johns <chr...@rtems.org> wrote:
> On 6/5/18 5:28 pm, Vijay Kumar Banerjee wrote:
>
>> On 6 May 2018 at 08:54, Chris Johns <chr...@rtems.org > chr...@rtems.org>> wrote:
>>
>> Would you please try `waf clean build`
On 6 May 2018 at 08:54, Chris Johns <chr...@rtems.org> wrote:
> On 6/5/18 9:49 am, Chris Johns wrote:
>
>> On 6/5/18 7:54 am, Vijay Kumar Banerjee wrote:
>>
>>> On 6 May 2018 at 03:05, Chris Johns <chr...@rtems.org >> chr...@rtems.org>>
>>
On 6 May 2018 at 03:05, Chris Johns <chr...@rtems.org> wrote:
>
> On 6 May 2018, at 7:04 am, Vijay Kumar Banerjee <vijaykumar9...@gmail.com>
> wrote:
>
>
> On 6 May 2018 at 02:25, Cillian O'Donnell <cpodonne...@gmail.com> wrote:
>
>>
>>
>&
On 6 May 2018 at 02:25, Cillian O'Donnell wrote:
>
>
> On 5 May 2018 at 21:12, Chris Johns wrote:
>
>>
>>
>> > On 6 May 2018, at 2:44 am, Joel Sherrill wrote:
>> >
>> > Looks similar to Cillian's failure. Chris will have to show me where
rtems-tools/build/tester/covoar/CoverageReaderQEMU.cc.1.o']
On 5 May 2018 at 21:47, Joel Sherrill <j...@rtems.org> wrote:
>
>
> On Sat, May 5, 2018, 10:57 AM Vijay Kumar Banerjee <
> vijaykumar9...@gmail.com> wrote:
>
>> Hello,
>>
>> I'm getting t
Hello,
I'm getting this build failure after applying this patch
---
Build failed
-> task in 'ccovoar' failed with exit status 1:
{task 140086064254560: cxx app_common.cc -> app_common.cc.1.o}
['/usr/bin/g++', '-std=c++11', '-O2', '-g', '-Itester/covoar',
'-I../tester/covoar', '-Irtemstoolkit',
On Fri, 4 May 2018, 12:17 Cillian O'Donnell, <cpodonne...@gmail.com> wrote:
>
>
> On Fri, 4 May 2018, 00:04 Joel Sherrill, <j...@rtems.org> wrote:
>
>>
>>
>> On Thu, May 3, 2018 at 1:45 PM, Vijay Kumar Banerjee <
>> vijaykumar9...@gmail.com
On 4 May 2018 at 04:34, Joel Sherrill <j...@rtems.org> wrote:
>
>
> On Thu, May 3, 2018 at 1:45 PM, Vijay Kumar Banerjee <
> vijaykumar9...@gmail.com> wrote:
>
>>
>> On 3 May 2018 at 22:58, Cillian O'Donnell <cpodonne...@gmail.com> wrote:
>>
801 - 900 of 971 matches
Mail list logo