<div dir="auto"><div><br><br><div class="gmail_quote"><div dir="ltr">On Wed, 6 Jun 2018, 05:07 Vijay Kumar Banerjee, <<a href="mailto:vijaykumar9597@gmail.com">vijaykumar9597@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><div><div class="gmail_quote"><div dir="ltr">On Wed, 6 Jun 2018, 08:31 Joel Sherrill, <<a href="mailto:joel@rtems.org" target="_blank" rel="noreferrer">joel@rtems.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><div><br><br><div class="gmail_quote"><div dir="ltr">On Tue, Jun 5, 2018, 9:54 PM Chris Johns <<a href="mailto:chrisj@rtems.org" rel="noreferrer noreferrer" target="_blank">chrisj@rtems.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
On 31/5/18 6:44 am, Vijay Kumar Banerjee wrote:<br>
> On 31 May 2018 at 02:02, Joel Sherrill <<a href="mailto:joel@rtems.org" rel="noreferrer noreferrer noreferrer" target="_blank">joel@rtems.org</a> <mailto:<a href="mailto:joel@rtems.org" rel="noreferrer noreferrer noreferrer" target="_blank">joel@rtems.org</a>>><br>
> wrote:<br>
> On Wed, May 30, 2018 at 3:29 PM, Vijay Kumar Banerjee<br>
> <<a href="mailto:vijaykumar9597@gmail.com" rel="noreferrer noreferrer noreferrer" target="_blank">vijaykumar9597@gmail.com</a> <mailto:<a href="mailto:vijaykumar9597@gmail.com" rel="noreferrer noreferrer noreferrer" target="_blank">vijaykumar9597@gmail.com</a>>> wrote:<br>
> <br>
> On 31 May 2018 at 00:28, Joel Sherrill <<a href="mailto:joel@rtems.org" rel="noreferrer noreferrer noreferrer" target="_blank">joel@rtems.org</a><br>
> <mailto:<a href="mailto:joel@rtems.org" rel="noreferrer noreferrer noreferrer" target="_blank">joel@rtems.org</a>>> wrote:<br>
> I may not understand correctly but there is test_run and<br>
> coverage_run. Someone<br>
> suggested making coverage_running an option to test_run. If that's<br>
> what's being<br>
> asked for, then I think doing it in a follow up patch is OK.<br>
> <br>
> If that's the intended request, perhaps a ticket should be filed.<br>
> <br>
> <br>
> Sorry for all the confusion.<br>
> This patch doesn't change the way test works. It only adds an option to run <br>
> the coverage script. coverage_run just runs the coverage.coverage_run<br>
> <br>
> <br>
> :) And I am saying if we want to have one test_run with an argument, do it as<br>
> a future work iteration. File a ticket. <br>
> <br>
> We need to get the code working on the master.<br>
> <br>
> Okay, we can keep that as a future work (I haven't thought about it though). :)<br>
> Getting it to work on master is our primary objective. <br>
> <br>
<br>
Was a ticket raised to removing 'coverage_run' and to use 'test_run'?<br></blockquote></div></div><div dir="auto"><br></div><div dir="auto">I haven't seen tickets for any of the issues we identified.</div></div></blockquote></div></div><div dir="auto">was there supposed to be tickets for each issue?</div></div></blockquote></div></div><div dir="auto"><br></div><div dir="auto">So trawl back over the emails and make a ticket for anything that hasn't been done, any suggestions for improvements related to the project. Include things that might not be for gsoc but related to the project. They can assigned to people and the priority determined after you've collected them all.</div><div dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><div dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><div dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Chris<br>
</blockquote></div></div></div>
</blockquote></div></div></div>
_______________________________________________<br>
devel mailing list<br>
<a href="mailto:devel@rtems.org" target="_blank" rel="noreferrer">devel@rtems.org</a><br>
<a href="http://lists.rtems.org/mailman/listinfo/devel" rel="noreferrer noreferrer" target="_blank">http://lists.rtems.org/mailman/listinfo/devel</a></blockquote></div></div></div>