On 2013-12-17 15:08, Joel Sherrill wrote:
On 12/17/2013 7:27 AM, Sebastian Huber wrote:
>On 2013-12-17 14:20, Jennifer Averett wrote:
>>I started out with it as one, but because of the way the tests run
>>a lot of data comes out (one line for each comparison). I split them
>>up so each test doesn't output so many screens of data. If I put them
>>back as one, would it be better only print at the top of the test (ex.
>>AND test) then print details upon a failure within that (this doesn't
>>match the way other tests work though)
>
>The only interesting output is the "END OF TEST" message, since this checked by
>the RTEMS testing script. I case of failure you get an assert message, this
>should be enough.
>
Depends on what you mean by interesting. The intent
was to note what the test was doing before the asserts.
If I run the tests I don't care about the test output at all. I look at the
check_endof output.
Combining the tests also has a tendency to give us huge tests
which don't run on all targets. I don't know in this case
how large the resulting combined test would be.
I don't think these trivial bit manipulations leads in huge test binaries.
--
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail : sebastian.hu...@embedded-brains.de
PGP : Public key available on request.
Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
_______________________________________________
rtems-devel mailing list
rtems-devel@rtems.org
http://www.rtems.org/mailman/listinfo/rtems-devel
