RZ_A1H Tests Failing

[bridadan]

Description

• Type: Bug
• Priority: Major

---

Bug

Target
RZ_A1H

Toolchain:
GCC_ARM, ARM, and IAR

Toolchain version:
GCC_ARM - 4.9.3 20141119
ARM - ARM Compiler 5.06 update 1
IAR - V7.80.1.11864/W32 for ARM

mbed-cli version:
0.9.10

meed-os sha:
9d8ec61df5e7442bbde12beabe744ed3a3e13486

DAPLink version:
0221 according to DETAILS.TXT, but I think this is running CMSIS-DAP

Expected behavior
All tests pass!

Actual behavior
Not all tests pass!

Steps to reproduce
mbed test -m RZ_A1H -t GCC_ARM -v -n tests-mbed_drivers-race_test,tests-mbedmicro-rtos-mbed-malloc,tests-mbedmicro-rtos-mbed-threads

Failing tests

NOTE: These failures were consistent across all toolchains

tests-mbed_drivers-race_test

[1479316325.57][HTST][INF] host test detected: default_auto
[1479316325.58][CONN][INF] found KV pair in stream: {{__testcase_count;2}}, queued...
[1479316325.61][CONN][RXD] >>> Running 2 test cases...
[1479316325.66][CONN][INF] found KV pair in stream: {{__testcase_name;function init race}}, queued...
[1479316325.70][CONN][RXD]
[1479316325.70][CONN][INF] found KV pair in stream: {{__testcase_name;class init race}}, queued...
[1479316325.75][CONN][RXD] >>> Running case #1: 'function init race'...
[1479316325.79][CONN][INF] found KV pair in stream: {{__testcase_start;function init race}}, queued...
[1479316325.80][CONN][RXD] Running function race test
[1479316325.82][CONN][RXD] TestClass ctor start
[1479316326.36][CONN][RXD] TestClass ctor end
[1479316345.63][HTST][INF] test suite run finished after 20.10 sec...
[1479316345.64][CONN][INF] received special even '__host_test_finished' value='True', finishing
[1479316345.65][HTST][INF] CONN exited with code: 0
[1479316345.65][HTST][INF] No events in queue
[1479316345.65][HTST][INF] stopped consuming events
[1479316345.65][HTST][INF] host test result(): None
[1479316345.65][HTST][WRN] missing __exit event from DUT
[1479316345.65][HTST][WRN] missing __exit_event_queue event from host test
[1479316345.65][HTST][ERR] missing __exit_event_queue event from host test and no result from host test, timeout...
[1479316345.65][HTST][INF] calling blocking teardown()
[1479316345.65][HTST][INF] teardown() finished
[1479316345.65][HTST][INF] {{result;timeout}}
mbedgt: checking for GCOV data...
mbedgt: mbed-host-test-runner: stopped and returned 'TIMEOUT'
mbedgt: test on hardware with target id: 550002210FB3423630F7860B
mbedgt: test suite 'tests-mbed_drivers-race_test' .................................................... TIMEOUT in 31.87 sec
        test case: 'function init race' .............................................................. ERROR in 0.00 sec
mbedgt: all tests finished!

tests-mbedmicro-rtos-mbed-malloc

[1479316525.24][SERI][TXD] mbedmbedmbedmbedmbedmbedmbedmbedmbedmbed
[1479316525.24][CONN][INF] sending up to 2 __sync packets (specified with --sync=2)
[1479316525.24][CONN][INF] sending preamble '065f9f88-7637-459d-917c-e099d8ed706e'
[1479316525.24][SERI][TXD] {{__sync;065f9f88-7637-459d-917c-e099d8ed706e}}
[1479316525.36][CONN][RXD] mbedmbedmbedmbedmbedmbedmbedmbed
[1479316525.41][CONN][INF] found SYNC in stream: {{__sync;065f9f88-7637-459d-917c-e099d8ed706e}} it is #0 sent, queued...
[1479316525.41][HTST][INF] sync KV found, uuid=065f9f88-7637-459d-917c-e099d8ed706e, timestamp=1479316525.413000
[1479316525.42][CONN][INF] found KV pair in stream: {{__version;1.3.0}}, queued...
[1479316525.43][HTST][INF] DUT greentea-client version: 1.3.0
[1479316525.45][CONN][INF] found KV pair in stream: {{__timeout;20}}, queued...
[1479316525.46][HTST][INF] setting timeout to: 20 sec
[1479316525.48][CONN][INF] found KV pair in stream: {{__host_test_name;default_auto}}, queued...
[1479316525.49][HTST][INF] host test class: '<class 'mbed_host_tests.host_tests.default_auto.DefaultAuto'>'
[1479316525.49][HTST][INF] host test setup() call...
[1479316525.49][HTST][INF] CALLBACKs updated
[1479316525.49][HTST][INF] host test detected: default_auto
[1479316545.77][HTST][INF] test suite run finished after 20.31 sec...
[1479316545.78][CONN][INF] received special even '__host_test_finished' value='True', finishing
[1479316545.82][HTST][INF] CONN exited with code: 0
[1479316545.82][HTST][INF] No events in queue
[1479316545.82][HTST][INF] stopped consuming events
[1479316545.82][HTST][INF] host test result(): None
[1479316545.82][HTST][WRN] missing __exit event from DUT
[1479316545.82][HTST][WRN] missing __exit_event_queue event from host test
[1479316545.82][HTST][ERR] missing __exit_event_queue event from host test and no result from host test, timeout...
[1479316545.82][HTST][INF] calling blocking teardown()
[1479316545.82][HTST][INF] teardown() finished
[1479316545.82][HTST][INF] {{result;timeout}}
mbedgt: checking for GCOV data...
mbedgt: mbed-host-test-runner: stopped and returned 'TIMEOUT'
mbedgt: test case summary event not found
        no test case report present, assuming test suite to be a single test case!
        test suite: tests-mbedmicro-rtos-mbed-malloc
        test case: tests-mbedmicro-rtos-mbed-malloc
mbedgt: test on hardware with target id: 550002210FB3423630F7860B
mbedgt: test suite 'tests-mbedmicro-rtos-mbed-malloc' ................................................ TIMEOUT in 31.59 sec
        test case: 'tests-mbedmicro-rtos-mbed-malloc' ................................................ ERROR in 31.59 sec
mbedgt: test case summary: 0 passes, 1 failure
mbedgt: all tests finished!

tests-mbedmicro-rtos-mbed-threads

[1479316643.12][SERI][TXD] mbedmbedmbedmbedmbedmbedmbedmbedmbedmbed
[1479316643.12][CONN][INF] sending up to 2 __sync packets (specified with --sync=2)
[1479316643.12][CONN][INF] sending preamble '6ece48cc-293d-4b23-9c80-c426c84f4f7e'
[1479316643.12][SERI][TXD] {{__sync;6ece48cc-293d-4b23-9c80-c426c84f4f7e}}
[1479316643.25][CONN][RXD] mbedmbedmbedmbedmbedmbedmbedmbed
[1479316643.30][CONN][INF] found SYNC in stream: {{__sync;6ece48cc-293d-4b23-9c80-c426c84f4f7e}} it is #0 sent, queued...
[1479316643.33][HTST][INF] sync KV found, uuid=6ece48cc-293d-4b23-9c80-c426c84f4f7e, timestamp=1479316643.295000
[1479316643.35][CONN][INF] found KV pair in stream: {{__version;1.3.0}}, queued...
[1479316643.35][CONN][INF] found KV pair in stream: {{__timeout;40}}, queued...
[1479316643.35][HTST][INF] DUT greentea-client version: 1.3.0
[1479316643.35][HTST][INF] setting timeout to: 40 sec
[1479316643.38][CONN][INF] found KV pair in stream: {{__host_test_name;default_auto}}, queued...
[1479316643.39][HTST][INF] host test class: '<class 'mbed_host_tests.host_tests.default_auto.DefaultAuto'>'
[1479316643.39][HTST][INF] host test setup() call...
[1479316643.39][HTST][INF] CALLBACKs updated
[1479316643.39][HTST][INF] host test detected: default_auto
[1479316643.41][CONN][RXD] >>> Running 16 test cases...
[1479316643.47][CONN][INF] found KV pair in stream: {{__testcase_name;Testing single thread}}, queued...
[1479316643.52][CONN][INF] found KV pair in stream: {{__testcase_name;Testing parallel threads}}, queued...
[1479316643.56][CONN][INF] found KV pair in stream: {{__testcase_name;Testing serial threads}}, queued...
[1479316643.61][CONN][INF] found KV pair in stream: {{__testcase_name;Testing single thread with yield}}, queued...
[1479316643.66][CONN][INF] found KV pair in stream: {{__testcase_name;Testing parallel threads with yield}}, queued...
[1479316643.73][CONN][INF] found KV pair in stream: {{__testcase_name;Testing serial threads with yield}}, queued...
[1479316643.78][CONN][INF] found KV pair in stream: {{__testcase_name;Testing single thread with wait}}, queued...
[1479316643.86][CONN][INF] found KV pair in stream: {{__testcase_name;Testing parallel threads with wait}}, queued...
[1479316643.91][CONN][INF] found KV pair in stream: {{__testcase_name;Testing serial threads with wait}}, queued...
[1479316643.96][CONN][INF] found KV pair in stream: {{__testcase_name;Testing single thread with child}}, queued...
[1479316644.02][CONN][INF] found KV pair in stream: {{__testcase_name;Testing parallel threads with child}}, queued...
[1479316644.08][CONN][INF] found KV pair in stream: {{__testcase_name;Testing serial threads with child}}, queued...
[1479316644.12][CONN][INF] found KV pair in stream: {{__testcase_name;Testing single thread with murder}}, queued...
[1479316644.18][CONN][INF] found KV pair in stream: {{__testcase_name;Testing parallel threads with murder}}, queued...
[1479316644.24][CONN][INF] found KV pair in stream: {{__testcase_name;Testing serial threads with murder}}, queued...
[1479316644.29][CONN][INF] found KV pair in stream: {{__testcase_name;Testing thread self terminate}}, queued...
[1479316644.30][CONN][RXD]
[1479316644.35][CONN][RXD] >>> Running case #1: 'Testing single thread'...
[1479316644.39][CONN][INF] found KV pair in stream: {{__testcase_start;Testing single thread}}, queued...
[1479316683.96][HTST][INF] test suite run finished after 40.61 sec...
[1479316683.97][CONN][INF] received special even '__host_test_finished' value='True', finishing
[1479316683.98][HTST][INF] CONN exited with code: 0
[1479316683.98][HTST][INF] No events in queue
[1479316683.98][HTST][INF] stopped consuming events
[1479316683.98][HTST][INF] host test result(): None
[1479316683.98][HTST][WRN] missing __exit event from DUT
[1479316683.98][HTST][WRN] missing __exit_event_queue event from host test
[1479316683.98][HTST][ERR] missing __exit_event_queue event from host test and no result from host test, timeout...
[1479316683.98][HTST][INF] calling blocking teardown()
[1479316683.98][HTST][INF] teardown() finished
[1479316683.98][HTST][INF] {{result;timeout}}
mbedgt: checking for GCOV data...
mbedgt: mbed-host-test-runner: stopped and returned 'TIMEOUT'
mbedgt: test on hardware with target id: 550002210FB3423630F7860B
mbedgt: test suite 'tests-mbedmicro-rtos-mbed-threads' ............................................... TIMEOUT in 52.73 sec
        test case: 'Testing single thread' ........................................................... ERROR in 0.00 sec
mbedgt: all tests finished!

cc @toyowata, @TomoYamanaka

[TomoYamanaka]

@bridadan

Thank you for giving me the comment. And sorry for this late reply.

I don't understand well the occurs.
Does this errors cause by the version of the automatic test tool (mbed-cli, mbed-greentea, mbed-ls etc)?
Because we passed these three tests for mbed-os 5 in Aug.
After that, I made a minor fix, but I don't think I changed the content that affects these tests.

cc @toyowata

[bridadan]

@TomoYamanaka Thanks for your reply. I was just doing a general check up on this platform and saw there were a few test failures and I thought I'd notify you.

The tests-mbed_drivers-race_test test was added to the code base on Aug 30 in this PR: #2562. This was added by @c1728p9, maybe he has some insight as to what's the problem?

The tests-mbedmicro-rtos-mbed-malloc test was also added by @c1728p9 so I might let him comment on that.

The tests-mbedmicro-rtos-mbed-threads may be related to the two tests above, so let's focus on those two at the moment.

[adbridge]

@c1728p9 Russ can you comment please?

[c1728p9]

I took a look at the test tests-mbedmicro-rtos-mbed-malloc in depth and found a couple of problems that are causing these failures:

1. Cortex A is using an older version of RTX which is causing problems. Specifically, rt_tsk_delete isn't releasing mutexes held by a task that exits or is terminated. This causes the function thread.join() to get stuck. Updating to RTX 4.8 will fix this problem. Worst case, just rt_tsk_delete could be patched.

2. With ARMCC there is a stack overflow in this test. The define THREAD_STACK_SIZE is too small for cortex A which is causing this overflow.

3. Malloc locking is missing for GCC_ARM. The functions __rtos_malloc_lock, __rtos_malloc_unlock and __rtos_env_lock need to be implemented in mbed-os\rtos\rtx\TARGET_CORTEX_A\RTX_CM_lib.h for GCC.

[TomoYamanaka]

@bridadan
Thanks for your reply. I understood that those was a newly added tests.

@c1728p9
Thanks you for your commnets.
My understandind on your feedback is that these test error occur because "Cortex-A" is using an older version of "RTX" and some functions are nothing.
Is it right ?

[c1728p9]

Hi @TomoYamanaka, the old version of RTX is 1 of the 3 problems. To pass testing all 3 need to be fixed. The old version of RTX is causing problems because rt_tsk_delete() has a bug in it - it does not release mutexes held by the terminated task.

[TomoYamanaka]

@c1728p9
Thanks you for your commnets. I was misunderstanding.
Renesas will consider measures for three problems.

[TomoYamanaka]

@c1728p9

2.With ARMCC there is a stack overflow in this test. The define THREAD_STACK_SIZE is too small for
cortex A which is causing this overflow.

I recognize this THREAD_STACK_SIZE macro defined to the following file. It is right ?
  TESTS\mbedmicro-rtos-mbed\malloc\main.cpp

This main.cpp is a test file for tests-mbedmicro-rtos-mbed-malloc .
Therefore, I think that it is necessary to "#ifdef" the definition of THREAD_STACK_SIZE for each target.
For example, as in main.cpp below.
  TESTS\mbedmicro-rtos-mbed\basic\main.cpp

Is it possible to modify it by an ARM member who is a test case creator?

[c1728p9]

Hi @TomoYamanaka I created this test so feel free to modify it. I would recommend an "#if defined(__CORTEX_A9)" and inside it set the stack to a larger value. I think cortex-A in general will require more stack space. If you would like I can make this change.

[TomoYamanaka]

@c1728p9
Thank you for your prompt reply and suggestions.

I will be very helpful if you change it. Please make this change.
As is the other main.cpp for test, I think that this stack size will be DEFAULT_STACK_SIZE(= 2048).

[c1728p9]

Hi @TomoYamanaka, I created #3362 to increase the stack size.

[TomoYamanaka]

@c1728p9
Thank you for your support.

[TomoYamanaka]

Now Renesas is resolving this issue.
After fix it, I will push PR.

If anything, please let me ask a question again.

Best regards