<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On 15 April 2018 at 14:02, Cillian O'Donnell <span dir="ltr"><<a href="mailto:cpodonnell8@gmail.com" target="_blank">cpodonnell8@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><span class="gmail-">On 15 April 2018 at 06:46, Vijay Kumar Banerjee <span dir="ltr"><<a href="mailto:vijaykumar9597@gmail.com" target="_blank">vijaykumar9597@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><span><br clear="all"><div><div class="gmail-m_2627146913720514847m_3741653074207145913gmail_signature"><div dir="ltr"><div dir="ltr">On 15 April 2018 at 01:45, Cillian O'Donnell <span dir="ltr"><<a href="mailto:cpodonnell8@gmail.com" target="_blank">cpodonnell8@gmail.com</a>></span> wrote:<br></div></div></div></div></span><div class="gmail_quote"><span><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Switch one of these lines out in qemu.cfg.<span class="gmail-m_2627146913720514847m_3741653074207145913gmail-"><br><br><table class="gmail-m_2627146913720514847m_3741653074207145913gmail-m_-286821032869333324gmail-highlight gmail-m_2627146913720514847m_3741653074207145913gmail-m_-286821032869333324gmail-tab-size gmail-m_2627146913720514847m_3741653074207145913gmail-m_-286821032869333324gmail-js-file-line-container"><tbody><tr><td id="gmail-m_2627146913720514847m_3741653074207145913gmail-m_-286821032869333324gmail-LC54" class="gmail-m_2627146913720514847m_3741653074207145913gmail-m_-286821032869333324gmail-blob-code gmail-m_2627146913720514847m_3741653074207145913gmail-m_-286821032869333324gmail-blob-code-inner gmail-m_2627146913720514847m_3741653074207145913gmail-m_-286821032869333324gmail-js-file-line"><span class="gmail-m_2627146913720514847m_3741653074207145913gmail-m_-286821032869333324gmail-pl-c"><span class="gmail-m_2627146913720514847m_3741653074207145913gmail-m_-286821032869333324gmail-pl-c">#</span>%define qemu_opts_base -no-reboot -monitor none -serial stdio -nographic</span></td>
</tr>
<tr>
</tr></tbody></table><table class="gmail-m_2627146913720514847m_3741653074207145913gmail-m_-286821032869333324gmail-highlight gmail-m_2627146913720514847m_3741653074207145913gmail-m_-286821032869333324gmail-tab-size gmail-m_2627146913720514847m_3741653074207145913gmail-m_-286821032869333324gmail-js-file-line-container"><tbody><tr><td id="gmail-m_2627146913720514847m_3741653074207145913gmail-m_-286821032869333324gmail-LC55" class="gmail-m_2627146913720514847m_3741653074207145913gmail-m_-286821032869333324gmail-blob-code gmail-m_2627146913720514847m_3741653074207145913gmail-m_-286821032869333324gmail-blob-code-inner gmail-m_2627146913720514847m_3741653074207145913gmail-m_-286821032869333324gmail-js-file-line"><span class="gmail-m_2627146913720514847m_3741653074207145913gmail-m_-286821032869333324gmail-pl-c"><span class="gmail-m_2627146913720514847m_3741653074207145913gmail-m_-286821032869333324gmail-pl-c">#</span>%define qemu_opts_base -no-reboot -serial null -serial mon:stdio -nographic</span></td>
</tr>
<tr>
</tr></tbody></table>%define qemu_opts_base -no-reboot -monitor null -serial stdio -nographic<br><br></span></div>Just comment out the one that's being used and uncomment one of the others. It should cause a complaint when the tests are run and the qemu cmd should show up in the log so we can take a look at it.<br></div></blockquote><div><br></div><div><br></div></span><div>error: qemu.cfg:71: execute failed: qemu-system-sparc -no-reboot -monitor null -serial stdio -nographic -no-reboot -monitor null -serial stdio -nographic -M leon3_generic -kernel /home/lunatic/development/rtem<wbr>s/kernel/leon3/sparc-rtems5/c/<wbr>leon3/testsuites/samples/<wbr>unlimited/unlimited.exe: exit-code:1</div><div><br></div><div><div>run: qemu-system-sparc -no-reboot -monitor null -serial stdio -nographic -no-reboot -mo nitor null -serial stdio -nographic -M leon3_generic -kernel /home/lunatic/development/rtem<wbr> s/kernel/leon3/sparc-rtems5/c/<wbr>leon3/testsuites/samples/unlim<wbr>ited/unlimited.exe -exec-trace /home/lunatic/development/rte<wbr>ms/kernel/leon3/sparc-rtems5/<wbr>c/leon3/testsuites/samples/<wbr>unlimi ted/unlimited.exe.cov</div></div></div></div></div></blockquote><div><br></div></span><div>Are those line breaks actually there or is it from the copy and paste. Like unlimi ted. If so that's definitely the problem. What does your last section in qemu.cfg look like now? The execute section.<br></div></div></div></div></blockquote><div>They are from copy paste . </div><div>I'm pasting the qemu.cfg here </div><div>.....</div><div><br></div><div><div>#</div><div># RTEMS Tools Project (<a href="http://www.rtems.org/">http://www.rtems.org/</a>)</div><div># Copyright 2010-2014 Chris Johns (<a href="mailto:chrisj@rtems.org">chrisj@rtems.org</a>)</div><div># All rights reserved.</div><div>#</div><div># This file is part of the RTEMS Tools package in 'rtems-tools'.</div><div>#</div><div># Redistribution and use in source and binary forms, with or without</div><div># modification, are permitted provided that the following conditions are met:</div><div>#</div><div># 1. Redistributions of source code must retain the above copyright notice,</div><div># this list of conditions and the following disclaimer.</div><div>#</div><div># 2. Redistributions in binary form must reproduce the above copyright notice,</div><div># this list of conditions and the following disclaimer in the documentation</div><div># and/or other materials provided with the distribution.</div><div>#</div><div># this software is provided by the copyright holders and contributors "as is"</div><div># and any express or implied warranties, including, but not limited to, the</div><div># implied warranties of merchantability and fitness for a particular purpose</div><div># are disclaimed. in no event shall the copyright holder or contributors be</div><div># liable for any direct, indirect, incidental, special, exemplary, or</div><div># consequential damages (including, but not limited to, procurement of</div><div># substitute goods or services; loss of use, data, or profits; or business</div><div># interruption) however caused and on any theory of liability, whether in</div><div># contract, strict liability, or tort (including negligence or otherwise)</div><div># arising in any way out of the use of this software, even if advised of the</div><div># possibility of such damage.</div><div>#</div><div><br></div><div>#</div><div># qemu</div><div>#</div><div># use a qemu command to run the executable in the qemu simulator.</div><div>#</div><div><br></div><div>%include %{_configdir}/base.cfg</div><div>%include %{_configdir}/checks.cfg</div><div><br></div><div>#</div><div># console.</div><div>#</div><div>%define console_stdio</div><div>%include %{_configdir}/console.cfg</div><div><br></div><div>#</div><div># rtems version</div><div>#</div><div>%include %{_rtdir}/rtems/version.cfg</div><div><br></div><div>#</div><div># qemu common option patterns.</div><div>#</div><div>%define qemu_opts_base -no-reboot -monitor none -serial stdio -nographic</div><div>#%define qemu_opts_base -no-reboot -serial null -serial mon:stdio -nographic</div><div>#%define qemu_opts_base -no-reboot -monitor null -serial stdio -nographic</div><div>%define qemu_opts_no_net -net none</div><div>#</div><div># qemu executable</div><div>#</div><div>%ifn %{defined bsp_qemu_opts}</div><div> %define bsp_qemu_opts %{nil}</div><div>%endif</div><div>%define qemu_cmd qemu-system-%{bsp_arch}</div><div>%define qemu_opts %{bsp_qemu_opts}</div><div><br></div><div><br></div><div>#</div><div># Coverage analysis</div><div>#</div><div>%define coverage_arg %{nil}</div><div>%if %{defined _coverage}</div><div> %if %{coverage_supported}</div><div> %define coverage_arg -exec-trace %{test_executable}.cov</div><div> %else</div><div> %error "Coverage analysis unsupported for %{bsp}"</div><div> %endif</div><div>%endif</div><div><br></div><div>#</div><div># executable</div><div>#</div><div><br></div><div>#%execute %{qemu_cmd} %{qemu_opts} -kernel %{test_executable}</div><div>%execute %{qemu_cmd} %{qemu_opts_base} %{qemu_opts} -kernel %{test_executable} %{coverage_arg}</div><div><br></div><div><br></div><div>#%define qemu_opts_base -no-reboot -monitor none -serial stdio -nographic</div><div>#%define qemu_opts_base -no-reboot -serial null -serial mon:stdio -nographic</div><div>#%define qemu_opts_base -no-reboot -monitor null -serial stdio -nographic</div><div><br></div><div><br></div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div></div><div><div class="gmail-h5"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div><div class="gmail-m_2627146913720514847h5"><div><br></div><div><br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"></div><div class="gmail-m_2627146913720514847m_3741653074207145913gmail-HOEnZb"><div class="gmail-m_2627146913720514847m_3741653074207145913gmail-h5"><div class="gmail_extra"><br><div class="gmail_quote">On 14 April 2018 at 20:37, Vijay Kumar Banerjee <span dir="ltr"><<a href="mailto:vijaykumar9597@gmail.com" target="_blank">vijaykumar9597@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br clear="all"><div><div class="gmail-m_2627146913720514847m_3741653074207145913gmail-m_-286821032869333324m_8250684945742265825gmail_signature"><div dir="ltr"><div><div dir="ltr">-- vijay</div></div></div></div></div>
<br><div class="gmail_quote"><div><div class="gmail-m_2627146913720514847m_3741653074207145913gmail-m_-286821032869333324h5">On 15 April 2018 at 00:50, Vijay Kumar Banerjee <span dir="ltr"><<a href="mailto:vijaykumar9597@gmail.com" target="_blank">vijaykumar9597@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br clear="all"><div><div class="gmail-m_2627146913720514847m_3741653074207145913gmail-m_-286821032869333324m_8250684945742265825m_-4998241934375491163gmail_signature"><div dir="ltr"><div dir="ltr"><br></div></div></div></div><div class="gmail_quote"><div><div class="gmail-m_2627146913720514847m_3741653074207145913gmail-m_-286821032869333324m_8250684945742265825h5">On 14 April 2018 at 16:42, Cillian O'Donnell <span dir="ltr"><<a href="mailto:cpodonnell8@gmail.com" target="_blank">cpodonnell8@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="gmail-m_2627146913720514847m_3741653074207145913gmail-m_-286821032869333324m_8250684945742265825m_-4998241934375491163gmail-h5">On 14 April 2018 at 07:11, Chris Johns <span dir="ltr"><<a href="mailto:chrisj@rtems.org" target="_blank">chrisj@rtems.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="gmail-m_2627146913720514847m_3741653074207145913gmail-m_-286821032869333324m_8250684945742265825m_-4998241934375491163gmail-m_8524199623565779474gmail-">On 14/4/18 8:02 am, Vijay Kumar Banerjee wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Getting this error now seems like something is missing.<br>
<br>
........<br>
<br>
RTEMS Testing - Tester, 5 (b2ba08b0da42 modified)<br>
Coverage environment prepared<br>
Traceback (most recent call last):<br>
File "/home/lunatic/development/rte<wbr>ms/test/rtems-tools/tester/rte<wbr>ms-test", line 40, in <module><br>
rt.test.run()<br>
File "/home/lunatic/development/rte<wbr>ms/test/rtems-tools/tester/rt/<wbr>test.py", line 353, in run<br>
tst.reraise()<br>
File "/home/lunatic/development/rte<wbr>ms/test/rtems-tools/tester/rt/<wbr>test.py", line 160, in reraise<br>
_test_reraise(*self.result)<br>
NameError: global name '_test_reraise' is not defined<br>
<br>
</blockquote>
<br></span>
The reraise logic was moved to the rtemstoolkit last year:<br>
<br>
<a href="https://git.rtems.org/rtems-tools/commit/?id=fa81491764861e63785a3faa241c488469087209" rel="noreferrer" target="_blank">https://git.rtems.org/rtems-to<wbr>ols/commit/?id=fa81491764861e6<wbr>3785a3faa241c488469087209</a><br>
<br>
It had some issues that have been fixed and it is being reused else where in the tester.<br>
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
-- vijay<span class="gmail-m_2627146913720514847m_3741653074207145913gmail-m_-286821032869333324m_8250684945742265825m_-4998241934375491163gmail-m_8524199623565779474gmail-"><br>
<br>
On 13 April 2018 at 23:57, Vijay Kumar Banerjee <<a href="mailto:vijaykumar9597@gmail.com" target="_blank">vijaykumar9597@gmail.com</a> <mailto:<a href="mailto:vijaykumar9597@gmail.com" target="_blank">vijaykumar9597@gmail.c<wbr>om</a>>> wrote:<br>
<br>
<br>
<br>
On 13 April 2018 at 23:51, Cillian O'Donnell <<a href="mailto:cpodonnell8@gmail.com" target="_blank">cpodonnell8@gmail.com</a><br></span><span class="gmail-m_2627146913720514847m_3741653074207145913gmail-m_-286821032869333324m_8250684945742265825m_-4998241934375491163gmail-m_8524199623565779474gmail-">
<mailto:<a href="mailto:cpodonnell8@gmail.com" target="_blank">cpodonnell8@gmail.com</a>><wbr>> wrote:<br>
<br>
Hmmm it's not there. Even so I can almost guarantee you, the<br>
reason it's not running is that coverage_supported variable is<br>
not being found as true in qemu.cfg and so the the command to<br>
generated the trace files isn't run and there's no .cov files in<br>
the end. So that's what you'll have to dig into.<br>
<br>
Okay , I'll set it to global then.<br>
<br>
</span></blockquote>
<br>
Changes need to be on the latest version of master before I will review them. The failure above indicate the code you have is not up to date.<br></blockquote><div><br></div></div></div><div>Yes that was the plan. Just to check Vijay your starting point was using the ini-update branch from here?<br><br><a href="https://github.com/cillianodonnell/rtems-tools/tree/ini-update" target="_blank">https://github.com/cillianodon<wbr>nell/rtems-tools/tree/ini-upda<wbr>te</a><br><br></div><div>That branch is current rtems-tools master that I started to add things back in. The only reraise in there is the one improrted from rtemstoolkit. <br></div></div></div></div></blockquote><div> </div></div></div><div>yes this is the branch I'm using , I checked the reraise error , <span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">not sure how it showed up buit </span>I called it from the reraise module , and it got fixed . now I'm stuck here </div><div><div><br></div><div>error: config error: qemu.cfg:36: No 'target' defined</div></div></div></div></div></blockquote><div><br></div></div></div><div>okay , fixed that .</div><div>still getting the warnings of the unable to read .cov </div><span><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div><br></div><div>are we supposed to set the bsp to global as well ?</div><span><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div></div><span class="gmail-m_2627146913720514847m_3741653074207145913gmail-m_-286821032869333324m_8250684945742265825m_-4998241934375491163gmail-"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
The change you have made is generating an exception in the tester thread. If you want to continue down this path you will need to fix what ever you have added.<br>
<br>
The tests are run as threads separate from the main thread so the exception is caught and re-raised in the main thread letting you know. This is broken in the old code base you are using.<br>
<br>
Why not investigate the reason as indicated and sort if out what the new format configuration file needs?<span class="gmail-m_2627146913720514847m_3741653074207145913gmail-m_-286821032869333324m_8250684945742265825m_-4998241934375491163gmail-m_8524199623565779474gmail-HOEnZb"><font color="#888888"><br>
<br>
Chris<br>
</font></span></blockquote></span></div><br></div></div>
</blockquote></span></div><br></div></div>
</blockquote></span></div><br></div></div>
</blockquote></div><br></div>
</div></div></blockquote></div></div></div><br></div></div>
</blockquote></div></div></div><br></div></div>
</blockquote></div><br></div></div>