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
nne...@gmail.com> 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:
-- vijay
On 13 April 2018 at 23:29, Cillian O'Donnell <cpodonne...@gmail.com> 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 Vi
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 Ba
%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
>>
il.com> 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 mad
ls/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 couver
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 pa
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:
On 11 April 2018 at 10:45, Chris Johns <chr...@rtems.org> wrote:
> On 11/04/2018 15:04, Vijay Kumar Banerjee wrote:
> > I was using Python 3, I just checked that it works fine with Python2.7
> without
> > the changes mentioned in the patch.
>
> I suggest you stay
I was using Python 3, I just checked that it works fine with Python2.7
without the changes mentioned in the patch.
On 11 April 2018 at 06:20, Chris Johns wrote:
> On 11/04/2018 07:04, vijaykumar9...@gmail.com wrote:
> > From: thelunatic
> >
> > ---
>
yes I'm using python 3
On Wed, 11 Apr 2018, 04:49 Chris Johns, wrote:
> Hi,
>
> Are you using Python 3?
>
> This is an upstream package ...
>
> https://github.com/msoulier/tftpy/blob/master/tftpy/TftpServer.py
>
> and it looks to me like this has been fixed upstream so we
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>
> wrot
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 (
uot;/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 <cpodonne...@gmail.com> wrote:
>
>
> On Wed, 4 Apr 2018, 11:18 V
..@rtems.org> 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 t
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
On 3 April 2018 at 03:58, Chris Johns wrote:
> On 03/04/2018 02:10, Cillian O'Donnell wrote:
> > Sure if you want to crack at it.
> >
> > If you pull the ini-update branch again, I've included the other files
> you'll need.
> >
> > Now if you try and run rtems-test with
Hello ,
I'm currently going through the coverage code , Can you please help me
understand what are the specific changes that are needed for the coverage
to be running again?
thanks
-- vijay
On 26 March 2018 at 09:30, Vijay Kumar Banerjee <vijaykumar9...@gmail.com>
wrote:
> 1. Yes
gcov as bonus work. It isn't discussed as work during the
> summer.It would be nice to get gcov correctness done earlier
> because that might be the best way to nice reports. For
> example, running lcov on the .gcov files produced by covoar
> might be an option.
>
> --joel
>
s someone answers soon, just upload it.
>
> --joel
>
> On Mar 25, 2018 2:37 PM, "Vijay Kumar Banerjee" <vijaykumar9...@gmail.com>
> wrote:
>
>> It's the last day before the deadline!
>> Please provide a final review of the proposal before submitting.
>>
It's the last day before the deadline!
Please provide a final review of the proposal before submitting.
Thanks
-- vijay
On 24 March 2018 at 21:37, Vijay Kumar Banerjee <vijaykumar9...@gmail.com>
wrote:
> hello mentors and other developers of the community , there are only thr
, Vijay Kumar Banerjee <vijaykumar9...@gmail.com>
wrote:
> Thanks Cillian :)
>
> It's great to see it running , I'll do some background reading about RSB,
> and RTEMS-Tools along with the covoar code . And also work on my python
> skills.
>
> to try rtems-test on a
I have tried
perl-5.24.3
perl-5.22.4
perl-5.20.3
still getting the same error, it be coming from something else
-- vijay
On 18 March 2018 at 16:15, Vijay Kumar Banerjee <vijaykumar9...@gmail.com>
wrote:
>
>
> -- vijay
>
> On 18 March 2018 at 16:13, Gedare Bloom <
-- vijay
On 18 March 2018 at 16:13, Gedare Bloom <ged...@rtems.org> wrote:
> On Sun, Mar 18, 2018 at 6:41 AM, Gedare Bloom <ged...@rtems.org> wrote:
> > Vijay,
> >
> > On Sun, Mar 18, 2018 at 6:36 AM, Vijay Kumar Banerjee
> > <vijaykumar9...@gmail.com&
t have --help which help2man can't parse.
> >
>
> I don't think this is the solution, because the failure happens while
> trying to build the autotools.
>
> > On Mar 17, 2018 11:34 AM, "Vijay Kumar Banerjee" <
> vijaykumar9...@gmail.com>
> > wrote
verture has been updated to a recent enough version of the upstream
> qemu, then it is likely to fail the same way.
>
> --joel
>
> On Mar 17, 2018 9:46 AM, "Vijay Kumar Banerjee" <vijaykumar9...@gmail.com>
> wrote:
>
>> I built it manually
>>
>>
It worked !
It's great to see it running ! I have attached the result .
-- vijay
On 18 March 2018 at 02:31, Cillian O'Donnell <cpodonne...@gmail.com> wrote:
>
>
> On 17 March 2018 at 20:08, Vijay Kumar Banerjee <vijaykumar9...@gmail.com>
> wrote:
>
>> yes it
hello ,
As suggested by Gedare , I have started this thread on the build error that
I'm getting .
I'm getting automake-1.12.6-x86_64-linux-gnu-1 building error while trying
to build autotools from rsb
I'm using fedora 27 64bit .
P.S: the error report is attached
-- vijay
RTEMS Tools Project -
; then add the prefix to $PATH in .bashrc as well like before.
>
> export PATH=$HOME/qemu/install/bin:$PATH
>
> Then run rtem-test and see what happens
>
>
> On 16 March 2018 at 19:13, Vijay Kumar Banerjee <vijaykumar9...@gmail.com>
> wrote:
>
>>
the same error comes when I try to build qemu from the
RTEMS/rtems-source-builder as well
is the issue coming from my system ? I'm using fedora 27 64bit
On 17 Mar 2018 12:39 a.m., "Vijay Kumar Banerjee" <vijaykumar9...@gmail.com>
wrote:
> yes , the same thing happens
>
velopment/5 devel/qemu
>
>
> On 16 March 2018 at 16:48, Vijay Kumar Banerjee <vijaykumar9...@gmail.com>
> wrote:
>
>> still the same error
>>
>> -- vijay
>>
>> On 16 March 2018 at 21:39, Cillian O'Donnell <cpodonne...@gmail.com>
>> wr
on my end. Pull that change into couverture-build
> branch and try it again. I'm not seeing any automake stuff here, so just
> check that and let me know.
>
> On 16 March 2018 at 14:59, Vijay Kumar Banerjee <vijaykumar9...@gmail.com>
> wrote:
>
>> building couvert
nne...@gmail.com> wrote:
>
>
> On 15 March 2018 at 12:26, Vijay Kumar Banerjee <vijaykumar9...@gmail.com>
> wrote:
>
>> It runs with a bunch of errors . I have attached the log file
>>
>
> Ok, I'm guessing you didn't set up Couverture-Qemu (special version of
&g
gt; $HOME/development/rtems-tools/tester/rtems-test --rtems-bsp=leon3-qemu
> --log=log-leon3.log --rtems-tools=$HOME/development/rtems/5
> --rtems-builddir=$HOME/development/rtems/kernel/leon3
> sparc-rtems5/c/leon3/testsuites/samples
>
> Do the tests run?
>
> On 15 March 2018 a
I have attached the output of the ls of that directory
-- vijay
On 15 March 2018 at 15:52, Cillian O'Donnell <cpodonne...@gmail.com> wrote:
>
>
> On 15 March 2018 at 03:58, Vijay Kumar Banerjee <vijaykumar9...@gmail.com>
> wrote:
>
>>
>> hello ,
>&g
hello ,
as told by Joel , I started this thread to further discuss the coverage
analysis toolset .
Current status is , I'm trying to builld and run rtems-test from the
coverage-merge branch of the previous GSoC student Cillian .
https://github.com/cillianodonnell/rtems-tools/tree/coverage-merge
wrote:
>>
>>>
>>>
>>> On Wed, Mar 14, 2018 at 4:13 PM, Cillian O'Donnell <
>>> cpodonne...@gmail.com> wrote:
>>>
>>>>
>>>>
>>>> On 14 March 2018 at 19:51, Cillian O'Donnell <cpodonne...@gmail.com>
>>>> w
On 15 March 2018 at 02:43, Cillian O'Donnell <cpodonne...@gmail.com> wrote:
>
>
> On 14 March 2018 at 19:51, Cillian O'Donnell <cpodonne...@gmail.com>
> wrote:
>
>>
>>
>> On 14 March 2018 at 18:26, Vijay Kumar Banerjee <vijaykumar9...@gmail.com
On 9 Mar 2018 10:15 p.m., "Vijay Kumar Banerjee" <vijaykumar9...@gmail.com>
wrote:
On 9 Mar 2018 3:34 a.m., "Joel Sherrill" <joel.sherr...@gmail.com> wrote:
On Sun, Mar 4, 2018 at 4:52 AM, Cillian O'Donnell <cpodonne...@gmail.com>
wrote:
>
>
>
ch 2018 at 22:18, Vijay Kumar Banerjee <vijaykumar9...@gmail.com>
wrote:
> Hello sir,
>
> I need some guidance to proceed to apply for #2920 as my GSoC project.
>
> I wanted to know the following points :
>
> 1. What are the prerequisites (do I have to produce somethi
Cillian ,
Thank you for the links, I will try to reproduce it , and in case of any
problem, I'll surely ask .
Vijay k.
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
help me find the right one.
Also, please guide me with reading references and some small tickets
related to the project .
Thank you ,
Vijay k.
On 26 February 2018 at 21:54, Vijay Kumar Banerjee <vijaykumar9...@gmail.com
> wrote:
> Thank you for giving me a detailed introduction to th
8 at 15:36, Joel Sherrill <j...@rtems.org> wrote:
>
>
> On Feb 26, 2018 2:22 AM, "Christian Mauderer" <
> christian.maude...@embedded-brains.de> wrote:
>
> Am 24.02.2018 um 16:21 schrieb Vijay Kumar Banerjee:
> > Hello,
> >
> > As t
Hello,
As told by Joel, I sent the screenshots of my working hello world to his
personal email and have also included my name in the GSoC tracking page .
+ Make Eclipse Target Interaction work with RTEMS (
https://www.eclipse.org/tcf/)
+ Improvements to our coverage reporting. GCOV validation
suites/samples/hello/hello.scn
@@ -1,3 +1,5 @@
-*** HELLO WORLD TEST ***
+***Vijay's HELLO WORLD TEST ***
Hello World
-*** END OF HELLO WORLD TEST ***
+This is Vijay Kumar Banerjee
+
+*** END OF Vijay's HELLO WORLD TEST ***
diff --git a/testsuites/samples/hello/init.c b/testsuites/samples/hello/
901 - 946 of 946 matches
Mail list logo