<div dir="auto"><div><br><br><div class="gmail_quote"><div dir="ltr">On Fri, 4 May 2018, 00:04 Joel Sherrill, <<a href="mailto:joel@rtems.org">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="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, May 3, 2018 at 1:45 PM, Vijay Kumar Banerjee <span dir="ltr"><<a href="mailto:vijaykumar9597@gmail.com" target="_blank" rel="noreferrer">vijaykumar9597@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><div class="gmail_quote"><span>On 3 May 2018 at 22:58, Cillian O'Donnell <span dir="ltr"><<a href="mailto:cpodonnell8@gmail.com" target="_blank" rel="noreferrer">cpodonnell8@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><span><div><br><br><div class="gmail_quote"><div dir="ltr">On Thu, 3 May 2018, 16:23 Vijay Kumar Banerjee, <<a href="mailto:vijaykumar9597@gmail.com" target="_blank" rel="noreferrer">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="ltr"><div dir="auto"><div class="gmail_quote" dir="auto"><div dir="ltr">Hello,</div><div dir="ltr"><br></div><div>I want to ask some things about the project to get a clear understanding of the objectives/milestones and current status of the project. I also seek advice on my Tasks/obectives.</div><div><br></div><div>1. The covoar has been updated to read symbols from the library and the next milestone is to remove covoar's dependancy on the external tools, which Chris is working on . ( Is that correct? )</div></div></div></div></blockquote></div></div><div dir="auto"> </div></span><div dir="auto">Looks like it won't be necessary for gsoc, so we won't have to wait for their removal. Chris might still have some other changes to make though and then we can pull master and branch off from there.</div></div></blockquote></span><div>Understood. </div></div></div></div></blockquote><div><br></div><div>If it is working as is, you are OK to work on GSoC objectives. Emphasis on the "working" part. </div><div>If something is broken right now, we want to fix it. :)<br></div><div><br></div><div>We also want to make sure all of the previous work is merged into the master. There may be</div><div>clean up left for this. Cillian is the best person to answer this one.</div><div><br></div><div>Chris has identified things to improve covoar which are not all required to be done now. </div><div><br></div><div>FWIW some history which might help get some perspective.</div><div><br></div><div>covoar was functional about a decade ago and driven by shell scripts that are still</div><div>in the rtems-testing repository. That is executable evidence of the work flow. I have some</div><div>odd figures and presentations from about the same time frame. That means it predates </div><div>the RSB and rtems-tools. Consequently, it predates using Python and C++ on the host</div><div>side for RTEMS tools. The shell scripts driving the process and invoking covoar should</div><div>now be all in Python. covoar itself needs some clean up to match current C++ practices.</div><div><br></div><div>The use of external tools was actually recommended by a binutils maintainer at the</div><div>time because the output of the tools is stable. That let us focus on the algorithms</div><div>to analyse the coverage. Now we can replace the use of those where possible. The</div><div>RTEMS Project did not use the ELF or DWARF libraries back then.</div><div><br></div><div>My shell scripts only did a few subsets of code to run reports on. One of the big</div><div>changes in the move to Python was a move to reporting on a larger number of</div><div>small sets. For example, report coverage on score, rtems, dosfs, etc. rather than</div><div>just "core" or "all". </div><div><br></div><div>I think this is the third GSoC project to work on these tools. That doesn't count</div><div>at least two students working on RTEMS tests to improve the actual coverage.</div><div><br></div><div>Hopefully Cillian's work last summer got us over the hurdle of being able to generate</div><div>the reports using rtems-tester. Pushing to get all that merged is an important and</div><div>critical precondition for this summer. All outstanding work should be in the</div><div>RTEMS.org repository.</div><div><br></div><div>And all your work should land there as well as soon as it is ready. :)</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><span><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="ltr"><div dir="auto"><div class="gmail_quote" dir="auto"><div><br></div><div>2. after it is done , the next step,I think, would be to update the coverage.py and test.py with the changes in covoar.</div></div></div></div></blockquote></div></div><div dir="auto"><br></div></span><div dir="auto">Yeah getting all the rtems tester code up to a standard that Chris will be happy to merge it will be the next step.</div></div></blockquote></span><div>So basically we wait for Chris to make the changes to covoar, needed for us to start working on coverage code to make it running and up to the standards. </div></div></div></div></blockquote><div><br></div><div>Chris can answer this. But if it works and produces coverage reports, it is ready.</div><div>If it is broken, report it. <br></div><div><br></div><div>All clean up and removal of external tools should not impact your project if the</div><div>code is working now. :)</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><span><div dir="auto"><br></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="ltr"><div dir="auto"><div class="gmail_quote" dir="auto"><div><br></div><div>While the Covoar is being updated, shall I be looking into the documentations and read the code to gain better understanding? Do you suggest me to work on some specific task ?</div></div></div></div></blockquote></div></div><div dir="auto"><br></div></span><div dir="auto">Understanding how covoar is working will be useful. Running covoar with -v option and reading down through covoar.cc should help you get an overview of what's going on. You don't need to understand every detail, just get a general sense of it.</div><div dir="auto"><br></div></div></blockquote></span><div>okay, I'll follow this. </div></div></div></div></blockquote><div><br></div><div>There is a Word document in the covoar directory. Cillian does that flow look right to you?</div></div></div></div></blockquote></div></div><div dir="auto"><br></div><div dir="auto">Not seeing the txt file, what's it called?</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="ltr"><div class="gmail_extra"><div class="gmail_quote"><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span><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><div dir="auto">Looks like gcov is going to feature heavily in your project. So reading up on that and understanding what state the gcov support in covoar is like should be useful.</div><div dir="auto"><br></div></div></blockquote></span><div>Understood. I'll read about it.</div><div>Thanks for the suggestions. <br></div></div></div></div></blockquote><div><br></div><div>My understanding is that it works (or worked) and that the reports generated by </div><div>running "gcov" on those output files did not match the results generated by </div><div>covoar's own reports.</div><div><br></div><div>The challenge is to find one of those disagreements and let's make sure covoar</div><div>is right. Then we can bring in the GCC guy who offered to help.</div><div><br></div><div>--joel</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div></div><span><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><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"><span><div dir="ltr"><div dir="auto"><div class="gmail_quote" dir="auto"><div><br></div><div>Please suggest resources to gain better understanding of how coverage analysis works/supposed to work with the rtems tester. (I can even try updating the documentations with some help, this will also help me get better understanding ).</div><div><br></div><div>Thank you.</div></div></div></div></span><span>
_______________________________________________<br>
devel mailing list<br>
<a href="mailto:devel@rtems.org" rel="noreferrer noreferrer" target="_blank">devel@rtems.org</a><br>
<a href="http://lists.rtems.org/mailman/listinfo/devel" rel="noreferrer noreferrer noreferrer" target="_blank">http://lists.rtems.org/mailman/listinfo/devel</a></span></blockquote></div></div></div>
</blockquote></span></div><br></div></div>
<br>_______________________________________________<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><br></blockquote></div><br></div></div>
</blockquote></div></div></div>