| 1 | The tests were designed to operate in a very controlled environment. If |
|---|
| 2 | one uses interrupt-driven console output, then tasks will block unexpectedly |
|---|
| 3 | when a buffer filles and interrupts will perturb with the task execution order. |
|---|
| 4 | |
|---|
| 5 | The tmtests should only be run with all interrupt sources disabled using |
|---|
| 6 | polled IO. |
|---|
| 7 | |
|---|
| 8 | The following is a list of reported failures from running the tests on |
|---|
| 9 | a board with interrupt driven console IO. These problems do not |
|---|
| 10 | occur when using polled IO. |
|---|
| 11 | |
|---|
| 12 | tm03, tm04, tm05, tm07, tm11, tm12, tm13, tm14, tm15, tm16, tm17, |
|---|
| 13 | tm19, tm22, tm23, tm24 - All hit my breakpoint at |
|---|
| 14 | _Internal_error_Occurred. |
|---|
| 15 | |
|---|
| 16 | tm20, tm27 - hang in middle of tests. |
|---|
| 17 | tm26 - hangs at end of tests. |
|---|
| 18 | |
|---|
| 19 | sp02 - Gets through some tests, then attempts to execute code at |
|---|
| 20 | location 0. |
|---|
| 21 | sp04 - hangs at end of tests. |
|---|
| 22 | sp06 - rtems_task_restart of TA3 FAILED -- expected (0) got (4) |
|---|
| 23 | sp07, sp14 - hang in middle of tests |
|---|
| 24 | sp13, sp15 - terminate properly, but output at end is missing. |
|---|
| 25 | sp16 - _Internal_error_Occurred. |
|---|
| 26 | sp19 - rtems_clock_get FAILED -- expected (0) got (11), and hangs in |
|---|
| 27 | middle of test. |
|---|
| 28 | |
|---|
| 29 | cpuuse - hangs in middle of tests |
|---|
| 30 | malloctest - prints nothing |
|---|
| 31 | |
|---|
| 32 | psx05 - Init: pthread_mutex_init - EINVAL (bad protocol) |
|---|
| 33 | ../../../../../../../src/rtems-981001/c/src/tests/psxtests/psx05/../../../../../ |
|---|
| 34 | ../../src/rtems-981001/c/src/tests/psxtests/psx05/task.c:35: |
|---|
| 35 | failed assertion `status == EBUSY' |
|---|
| 36 | N\: pthread_mutex_init - EINVAL (bad priority ceiling) |
|---|
| 37 | |
|---|
| 38 | |
|---|
![[RTEMS Logo]](/images/logo.png){kind=logo}
