Re: [PATCH] Generate coverage analysis Report

On Wed, 6 Jun 2018, 05:07 Vijay Kumar Banerjee, wrote: > 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>> >>> >

Re: [PATCH] Generate coverage analysis Report

On Tue, Jun 5, 2018, 11:07 PM Vijay Kumar Banerjee wrote: > 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>> >>>

Re: [PATCH] Generate coverage analysis Report

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: >> > On Wed, May 30, 2018 at 3:29 PM, Vijay Kumar Banerjee

Re: [PATCH] Generate coverage analysis Report

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: > > On Wed, May 30, 2018 at 3:29 PM, Vijay Kumar Banerjee > > mailto:vijaykumar9...@gmail.com>> wrote: > > > >

Re: [PATCH] Generate coverage analysis Report

On 31/5/18 6:44 am, Vijay Kumar Banerjee wrote: > On 31 May 2018 at 02:02, Joel Sherrill > > wrote: > On Wed, May 30, 2018 at 3:29 PM, Vijay Kumar Banerjee > mailto:vijaykumar9...@gmail.com>> wrote: > > On 31 May 2018 at 00:28, Joel Sherrill

Re: [PATCH] Generate coverage analysis Report

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 correctly but there is test_run and coverage_run. >>> Someone >>>

Re: [PATCH] Generate coverage analysis Report

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 correctly but there is test_run and coverage_run. >> Someone >> suggested making coverage_running an option to test_run. If

Re: [PATCH] Generate coverage analysis Report

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

Re: [PATCH] Generate coverage analysis Report

On Wed, May 30, 2018 at 1:34 PM, Vijay Kumar Banerjee < vijaykumar9...@gmail.com> wrote: > 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:

Re: [PATCH] Generate coverage analysis Report

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 config --user.name "My >>> Name") that you

Re: [PATCH] Generate coverage analysis Report

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 =

Re: [PATCH] Generate coverage analysis Report

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 config --user.name "My >> Name") that you submit. >> >> OK Noted :) > >> The first line of this commit, and

Re: [PATCH] Generate coverage analysis Report

On Wed, 30 May 2018, 18:54 Vijay Kumar Banerjee, wrote: > 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

Re: [PATCH] Generate coverage analysis Report

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

Re: [PATCH] Generate coverage analysis Report

On Wed, 30 May 2018, 18:21 Gedare Bloom, wrote: > Please provide your name in your commits (git config --user.name "My > Name") that you submit. > > The first line of this commit, and therefore the email subject, is > overly vague. Provide a slightly more specific description. > > On Wed, May

Re: [PATCH] Generate coverage analysis Report

Please provide your name in your commits (git config --user.name "My Name") that you submit. The first line of this commit, and therefore the email subject, is overly vague. Provide a slightly more specific description. On Wed, May 30, 2018 at 1:00 PM, thelunatic wrote: > + Add script to run

[PATCH] Generate coverage analysis Report

+ Add script to run covoar and generate an html report from the output generated from covoar + Add symbol-sets ini file for library addresses of the symbol-sets + tester/rt/test : Add options for running coverage Co-author : Cillian O'Donnel --- tester/rt/coverage.py |