On 2014-06-10 14:32, Gedare Bloom wrote:
On Tue, Jun 10, 2014 at 2:51 AM, Sebastian Huber
<sebastian.hu...@embedded-brains.de> wrote:
>Hello,
>
>the check submission script
>
>http://git.rtems.org/rtems-testing/tree/merge-helpers/check_submission
>
>contains a test for timing values
>
> # Hopefully have some output from the tmtests
> echo "=== Checking for timing information"
> c=$(ls -1 times* 2>/dev/null | wc -l)
> if [[ ${c} -eq 0 ]]; then
> echo "Please run the timing tests and include the results."
> fi
>
>Is it really useful to add such timing values to the sources? They may be
>out of date right with the next commit.
>
I agree. The only place timing results make sense is for a release.
Using the tmtests can also be important when making changes in
supercore, but that is less often done and should be better handled by
the developer/tester.
A long term goal should be to monitor the timing test results in automatic test
runs to catch timing regressions, but there are many steps necessary to get to
this point.
--
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
