search

ARMmbed / mbed-os

Arm Mbed OS is a platform operating system designed for the internet of things
https://mbed.com
Other
4.67k stars 2.98k forks source link

Green tea test failing on EFM32GG11_STK3701 #9933

Closed deepikabhavnani closed 5 years ago

deepikabhavnani commented 5 years ago

Description

Failure is noted on master branch of mbed-os

mbedgt: test suite report:
| target                | platform_name     | test suite                                       | result | elapsed_time (sec) | copy_method |
|-----------------------|-------------------|--------------------------------------------------|--------|--------------------|-------------|
| EFM32GG11_STK3701-ARM | EFM32GG11_STK3701 | mbed-os-tests-mbed_hal-stack_size_unification    | FAIL   | 21.14              | default     |
| EFM32GG11_STK3701-ARM | EFM32GG11_STK3701 | mbed-os-tests-mbedmicro-rtos-mbed-heap_and_stack | FAIL   | 21.5               | default     |

Steps to reproduce:

  1. Cloning https://github.com/ARMmbed/pelion-enablement or https://github.com/ARMmbed/pelion-ready-example (either of these work)
  2. Update your Mbed CLI to the latest version – 1.9.x
  3. Initialize your Pelion credentials (you don’t really need them to run these tests, but good to have). Test setup described here - https://github.com/ARMmbed/simple-mbed-cloud-client/#testing-setup
  4. Switch mbed-os to your branch.
  5. Run the tests with mbed test -t ARM -m <target/MCU> -n *stack*

Issue request type

[ ] Question
[ ] Enhancement
[X] Bug

CC @screamerbg

ciarmcom commented 5 years ago

Internal Jira reference: https://jira.arm.com/browse/MBOCUSTRIA-957

0xc0170 commented 5 years ago

cc @ARMmbed/team-silabs

stevew817 commented 5 years ago

We didn't submit any patches to EFM32 lately, so I'm taking a guess this is related to #9571.

I can't see the test job results for #9571. If I had to guess, these didn't run against EFM32 and therefore caused failure down the line when EFM32GG11_STK3701 is now being tested as part of pelion_enablement.

@0xc0170 Can you check whether #9571 was run against EFM32 boards before being merged in, before I spend any time looking into this?

0xc0170 commented 5 years ago

@0xc0170 Can you check whether #9571 was run against EFM32 boards before being merged in, before I spend any time looking into this?

Reviewed. It did not run for the PR.

stevew817 commented 5 years ago

On a broader note, @0xc0170 do you have any idea why it wasn't run?

stevew817 commented 5 years ago

@mprse Can you take a look at this, since the apparently offending PR is yours?

0xc0170 commented 5 years ago

We have nightly running - has wider coverage. The latests runs do not contain emf32. I'll talk to the test team

cc @ARMmbed/mbed-os-test

deepikabhavnani commented 5 years ago

@stevew817 - issue was identified and fix was going as part of other PR, this was to record that we get the fix in 5.12.

9910 has added fix for this. https://github.com/ARMmbed/mbed-os/pull/9910/commits/8b25887021c58261204935083ab477b467e08c3d

Sorry for trouble. Will close this once PR is merged

deepikabhavnani commented 5 years ago

Also though device was not part of CI test were executed locally to verify linker script updates

cmonr commented 5 years ago

Closing, since PR is merged.