Rtems-test cortex-m3

[Sebastian Huber]

On 28/03/16 21:01, Aurelio Remonda wrote:
> Hello, we were trying to get Sebastian's patches to work on the latest
> qemu. It seems the board is running ok on qemu 2.5.50 without the
> patches except for:
> -Memory hack: The memory on this board is still fixed to default
> value. I already submit a patch that allows you to change the memory
> size we are waiting for revision.

Nice.

> -Disable-priority_mask: this patch does not apply directly and rtems
> is running without it.

I am not sure which side-effects has this.

>
> So I run the rtems-test script:
> ./rtems-test --log=lm3s6965_qemu --timeout=60
> --rtems-bsp=lm3s6965_qemu
> --rtems-tools=/home/aurelio-remonda/rtems/install
> /home/aurelio-remonda/rtems/build/arm-rtems4.11/c/lm3s6965/testsuites/
>
> Passed:   342
> Failed:     0
> Timeouts: 175
> Invalid:    0
> -------------
> Total:    517
>
> Average test time: 0:00:15.392969
> Testing time     : 2:12:38.165222
>
> And then again with default time out:
>   ./rtems-test --log=lm3s6965_qemu --rtems-bsp=lm3s6965_qemu
> --rtems-tools=/home/aurelio-remonda/rtems/install
> /home/aurelio-remonda/rtems/build/arm-rtems4.11/c/lm3s6965/testsuites/
>
> Passed:   345
> Failed:     0
> Timeouts: 172
> Invalid:    0
> -------------
> Total:    517
>
> Average test time: 0:00:46.056823
> Testing time     : 6:36:51.377917
>
> So the test resulting in timeouts are known cases? Any of these test
> will pass if I set a larger timeout value?
> Do you think we can change the qemu version for this board?

This timeout count is too high. Only the spintrcritical* tests may 
timeout out. All other timeouts should be looked at individually.

-- 
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.huber at embedded-brains.de
PGP     : Public key available on request.

Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.