<div dir="ltr">Hi,<div><br></div><div>I would also like to ask if I have to prove my ability to work with RTEMS again (as last year I did Hello World, and then I worked on project during SOCIS)?</div><div><br></div><div>Thanks in advance for replies.</div>
<div>Krzysiek</div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">2013/7/29 Krzysztof Mięsowicz <span dir="ltr"><<a href="mailto:krzysztof.miesowicz@gmail.com" target="_blank">krzysztof.miesowicz@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Thank you for all replies very much. <div><br></div><div>I read about libfiu and it seems really interesting and I believe it can be quite easy applied to RTEMS testing. I hope so :) </div>
<div><br></div><div>
According to Joel's mail:</div><div class="im"><div><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div><i><span style="font-family:arial,sans-serif;font-size:13px">Another area which we need help in is the coverage and testing</span><br style="font-family:arial,sans-serif;font-size:13px">
<span style="font-family:arial,sans-serif;font-size:13px">scripts. The coverage reporting really should be by directory or</span><br style="font-family:arial,sans-serif;font-size:13px"><span style="font-family:arial,sans-serif;font-size:13px">capability. It is now reported in "lumps" that are too large.</span><br style="font-family:arial,sans-serif;font-size:13px">
<span style="font-family:arial,sans-serif;font-size:13px">Also rewriting as much of this as possible in Python including the</span><br style="font-family:arial,sans-serif;font-size:13px"><span style="font-family:arial,sans-serif;font-size:13px">sim-scripts is highly desirable.</span></i><br>
</div><div><br></div></div><div>Do you mean that coverage reporting framework should be rewrited and reports should be generated for source directories instead of core and developmental parts (as it is done now) ?</div><div>
And what particularly do you mean by "rewriting as much of THIS as possible" - do you mean all coverage reporting scripts which is now written as bash scripts? Do I understand you correctly? </div>
<div><br></div><div>Greetings,</div><div>Krzysiek</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">2013/7/29 Rempel, Cynthia <span dir="ltr"><<a href="mailto:cynt6007@vandals.uidaho.edu" target="_blank">cynt6007@vandals.uidaho.edu</a>></span><div>
<div class="h5"><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
Did a quick write-up on the fault-injection open-project...<br>
<a href="http://blitiri.com.ar/p/libfiu/" target="_blank">http://blitiri.com.ar/p/libfiu/</a> looks interesting... (the python bindings have been Debian packaged)<br>
it would probably need to be evaluated more thoroughly as part of the project though...<br>
<br>
Thanks,<br>
Cindy<br>
________________________________________<br>
From: <a href="mailto:rtems-devel-bounces@rtems.org" target="_blank">rtems-devel-bounces@rtems.org</a> [<a href="mailto:rtems-devel-bounces@rtems.org" target="_blank">rtems-devel-bounces@rtems.org</a>] on behalf of Rempel, Cynthia [<a href="mailto:cynt6007@vandals.uidaho.edu" target="_blank">cynt6007@vandals.uidaho.edu</a>]<br>
Sent: Monday, July 29, 2013 9:06 AM<br>
To: Joel Sherrill; Gedare Bloom<br>
Cc: Krzysztof Mięsowicz; <a href="mailto:rtems-devel@rtems.org" target="_blank">rtems-devel@rtems.org</a><br>
Subject: RE: ESA SOCIS - Fault injection tools topic<br>
<div><div><br>
Hi,<br>
<br>
Thanks for the link! This will be helpful with fleshing out the project...<br>
Yes, the initial idea was to get a tool the RTEMS development community could use to help with certification efforts...<br>
and having the certification report would be very helpful...<br>
Given this information, we can start to write an open-project page for this...<br>
<br>
The criteria we typically use for evaluating other projects are:<br>
1. Free and open source (usually modified BSD or special exception GPLv2, but as this is testing GPL would be fine)<br>
2. Works under Linux and Windows<br>
3. Still under maintainence<br>
<br>
Thanks!<br>
Cindy<br>
________________________________________<br>
From: <a href="mailto:rtems-devel-bounces@rtems.org" target="_blank">rtems-devel-bounces@rtems.org</a> [<a href="mailto:rtems-devel-bounces@rtems.org" target="_blank">rtems-devel-bounces@rtems.org</a>] on behalf of Joel Sherrill [joel.sherrill@OARcorp.com]<br>
Sent: Monday, July 29, 2013 8:23 AM<br>
To: Gedare Bloom<br>
Cc: Krzysztof Mięsowicz; <a href="mailto:rtems-devel@rtems.org" target="_blank">rtems-devel@rtems.org</a><br>
Subject: Re: ESA SOCIS - Fault injection tools topic<br>
<br>
If I forgot the link:<br>
<br>
<a href="ftp://www.rtems.org/pub/rtems/esa_validation_report_450/" target="_blank">ftp://www.rtems.org/pub/rtems/esa_validation_report_450/</a><br>
<br>
On 7/29/2013 9:45 AM, Gedare Bloom wrote:<br>
> This seems like a good project. Ballista looks like it is "dead"<br>
> upstream. You'll want to scope your project to decide what / how much<br>
> of RTEMS you can reasonably instrument with fault injection. I also<br>
> wonder if it would be sensible to first start with a tool that can<br>
> support test input "fuzzing", which is related to but somewhat<br>
> different than fault injection. I think "fuzzing" is more<br>
> appropriately related to test coverage /testing, whereas fault<br>
> injection can include also non-valid inputs and faults, such as<br>
> flipping bits in code or modifying values on-the-fly.<br>
><br>
> On Mon, Jul 29, 2013 at 4:25 AM, Krzysztof Mięsowicz<br>
> <<a href="mailto:krzysztof.miesowicz@gmail.com" target="_blank">krzysztof.miesowicz@gmail.com</a>> wrote:<br>
>> Hi!<br>
>><br>
>> My name is Krzysiek. I participated in ESA SOCIS 2012 for RTEMS and worked<br>
>> on improving test coverage. I'm interested in participating in this edition<br>
>> of SOCIS again.<br>
>><br>
>> I browse Open Projects page of RTEMS and I have question about topic related<br>
>> to fault injection tools. Have you any tips or suggestions to this topic<br>
>> (especially which tools are most desired or promising and how this project<br>
>> should look in details).<br>
>><br>
>> I googled a bit about fault injection and free tools and find some:<br>
>> Ballista, LFI, Fuzz, or JACA which potentially could be applied to RTEMS<br>
>> testing. But I'm looking forward to any tips or thoughts from you and<br>
>> additionaly is it possible to be selected again this year.<br>
>><br>
>> Thanks in advance for your replies.<br>
>> Krzysiek Mięsowicz<br>
>><br>
>> _______________________________________________<br>
>> rtems-devel mailing list<br>
>> <a href="mailto:rtems-devel@rtems.org" target="_blank">rtems-devel@rtems.org</a><br>
>> <a href="http://www.rtems.org/mailman/listinfo/rtems-devel" target="_blank">http://www.rtems.org/mailman/listinfo/rtems-devel</a><br>
>><br>
> _______________________________________________<br>
> rtems-devel mailing list<br>
> <a href="mailto:rtems-devel@rtems.org" target="_blank">rtems-devel@rtems.org</a><br>
> <a href="http://www.rtems.org/mailman/listinfo/rtems-devel" target="_blank">http://www.rtems.org/mailman/listinfo/rtems-devel</a><br>
<br>
<br>
--<br>
Joel Sherrill, Ph.D. Director of Research & Development<br>
joel.sherrill@OARcorp.com On-Line Applications Research<br>
Ask me about RTEMS: a free RTOS Huntsville AL 35805<br>
Support Available <a href="tel:%28256%29%20722-9985" value="+12567229985" target="_blank">(256) 722-9985</a><br>
<br>
_______________________________________________<br>
rtems-devel mailing list<br>
<a href="mailto:rtems-devel@rtems.org" target="_blank">rtems-devel@rtems.org</a><br>
<a href="http://www.rtems.org/mailman/listinfo/rtems-devel" target="_blank">http://www.rtems.org/mailman/listinfo/rtems-devel</a><br>
<br>
<br>
_______________________________________________<br>
rtems-devel mailing list<br>
<a href="mailto:rtems-devel@rtems.org" target="_blank">rtems-devel@rtems.org</a><br>
<a href="http://www.rtems.org/mailman/listinfo/rtems-devel" target="_blank">http://www.rtems.org/mailman/listinfo/rtems-devel</a><br>
<br>
<br>
</div></div></blockquote></div></div></div><br></div>
</blockquote></div><br></div>