On Sun, 13 May 2018, 22:15 Vijay Kumar Banerjee,
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 5c874
Hello,
this is 16:00 in UTC+2, which means I am always in a local train during
that time. So, I cannot attend.
--
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail : sebastian.hu...@embe
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
> --- a/tester/covoar/covoar.cc
> +++ b/tester/c
---
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
--- a/tester/covoar/covoar.cc
+++ b/tester/covoar/covoar.cc
@@ -75,7 +75,7 @@ static void createBuildPath(Execu
On Sun, May 13, 2018, 11:33 AM Cillian O'Donnell
wrote:
>
>
> On 13 May 2018 at 16:32, Vijay Kumar Banerjee
> wrote:
>
>> 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 ne
On 13 May 2018 at 16:32, Vijay Kumar Banerjee
wrote:
> 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/test
On Sun, May 13, 2018, 10:20 AM Gedare Bloom wrote:
> On Wed, May 9, 2018 at 4:23 PM, Joel Sherrill wrote:
> > Updates #3425.
> > ---
> > bsps/sparc64/include/arch/arch.h | 4
> > bsps/sparc64/include/arch/mm/frame.h | 4
> > bsps/sparc64/include/arch/mm/mmu.h
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 buildTarget
_
On 13 May 2018 at 21:02, Vijay Kumar Banerjee
wrote:
> 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/test
On Sun, May 13, 2018 at 11:32 AM, Vijay Kumar Banerjee
wrote:
> 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/
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 master plus one patch with th
On Wed, May 9, 2018 at 4:23 PM, Joel Sherrill wrote:
> Updates #3425.
> ---
> bsps/sparc64/include/arch/arch.h | 4
> bsps/sparc64/include/arch/mm/frame.h | 4
> bsps/sparc64/include/arch/mm/mmu.h| 4
> bsps/sparc64/include/arch/mm/tlb.h
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 master plus one patch with the tester support in
progress.
2. Apply your patch to that and mak
On Sun, 13 May 2018, 18:24 Cillian O'Donnell, wrote:
>
>
> On 13 May 2018 at 13:47, Vijay Kumar Banerjee
> wrote:
>
>>
>> On Sun, 13 May 2018, 18:14 Cillian O'Donnell,
>> wrote:
>>
>>>
>>>
>>> On 13 May 2018 at 13:35, Vijay Kumar Banerjee
>>> wrote:
>>>
On Sun, 13 May 2018, 17:32 Cil
On Sun, 13 May 2018, 18:24 Cillian O'Donnell, wrote:
>
>
> On 13 May 2018 at 13:47, Vijay Kumar Banerjee
> wrote:
>
>>
>> On Sun, 13 May 2018, 18:14 Cillian O'Donnell,
>> wrote:
>>
>>>
>>>
>>> On 13 May 2018 at 13:35, Vijay Kumar Banerjee
>>> wrote:
>>>
On Sun, 13 May 2018, 17:32 Cil
On 13 May 2018 at 13:47, Vijay Kumar Banerjee
wrote:
>
> On Sun, 13 May 2018, 18:14 Cillian O'Donnell,
> wrote:
>
>>
>>
>> On 13 May 2018 at 13:35, Vijay Kumar Banerjee
>> wrote:
>>
>>>
>>> On Sun, 13 May 2018, 17:32 Cillian O'Donnell,
>>> wrote:
>>>
I understand but that's a separate iss
On Sun, 13 May 2018, 18:14 Cillian O'Donnell, wrote:
>
>
> On 13 May 2018 at 13:35, Vijay Kumar Banerjee
> wrote:
>
>>
>> On Sun, 13 May 2018, 17:32 Cillian O'Donnell,
>> wrote:
>>
>>> I understand but that's a separate issue. I can do a full coverage run
>>> from the top of the build tree by c
On 13 May 2018 at 13:35, Vijay Kumar Banerjee
wrote:
>
> On Sun, 13 May 2018, 17:32 Cillian O'Donnell,
> wrote:
>
>> I understand but that's a separate issue. I can do a full coverage run
>> from the top of the build tree by changing hello.exe.cov to hello.cov
>> manually using current master. T
On Sun, 13 May 2018, 17:32 Cillian O'Donnell, wrote:
> I understand but that's a separate issue. I can do a full coverage run
> from the top of the build tree by changing hello.exe.cov to hello.cov
> manually using current master. Then I add your patch which is supposed to
> fix the problem of ha
I understand but that's a separate issue. I can do a full coverage run from
the top of the build tree by changing hello.exe.cov to hello.cov manually
using current master. Then I add your patch which is supposed to fix the
problem of having to change those manually so it looks for hello.exe.cov
ins
On Sun, 13 May 2018, 17:02 Cillian O'Donnell, wrote:
> But you see the thing is that if you remove the changes you made and run
> the tester from the top of the build tree it makes it past those checks and
> does full coverage analysis runs for all trace files that end in only .cov.
> So only hel
But you see the thing is that if you remove the changes you made and run
the tester from the top of the build tree it makes it past those checks and
does full coverage analysis runs for all trace files that end in only .cov.
So only hello.cov here because I've changed it manually.
warning: Unable
On 13 May 2018 at 16:16, Vijay Kumar Banerjee
wrote:
>
>
> On Sun, 13 May 2018, 16:15 Vijay Kumar Banerjee,
> wrote:
>
>>
>>
>> On Sun, 13 May 2018, 16:09 Cillian O'Donnell,
>> wrote:
>>
>>> It does seem to be having some knock on effect. Covoar made it past
>>> these checks before.
>>>
>>> ---
On Sun, 13 May 2018, 16:15 Vijay Kumar Banerjee,
wrote:
>
>
> On Sun, 13 May 2018, 16:09 Cillian O'Donnell,
> wrote:
>
>> It does seem to be having some knock on effect. Covoar made it past these
>> checks before.
>>
>> -
>> Total: 13
>> Average test time: 0:00:03.178923
On Sun, 13 May 2018, 16:09 Cillian O'Donnell, wrote:
> It does seem to be having some knock on effect. Covoar made it past these
> checks before.
>
> -
> Total: 13
> Average test time: 0:00:03.178923
> Testing time : 0:00:41.326000
> Running covoar for score
> covoar r
It does seem to be having some knock on effect. Covoar made it past these
checks before.
-
Total: 13
Average test time: 0:00:03.178923
Testing time : 0:00:41.326000
Running covoar for score
covoar results directory:
/home/cpod/development/rtems/leon3/coverage/score
ERRO
26 matches
Mail list logo
