Add mbed-os-example-pelion #11588

adbridge · 2019-09-27T14:54:28Z

Description

Add pelion example to the examples.json list. Primarily so that this example can be updated automatically with a pull request when updating Mbed OS version.
Set to compile in the CI but not export or test.

Pull request type

[ ] Fix
[ ] Refactor
[ ] Target update
[ ] Functionality change
[ ] Docs update
[x] Test update
[ ] Breaking change

Reviewers

Release Notes

Primarily so that this example can be updated automatically with a pull request when updating Mbed OS version. Set to compile in the CI but not export or test.

0xc0170 · 2019-09-30T07:06:02Z

CI started

teetak01 · 2019-09-30T08:11:44Z

tools/test/examples/examples.json

+        "compile" : true,
+        "export": false,
+        "test" : false,
+        "baud_rate": 9600,


baud_rate is wrong. Should be 115200

mbed-ci · 2019-09-30T09:48:23Z

Test run: FAILED

Summary: 4 of 4 test jobs failed
Build number : 1
Build artifacts

Failed test jobs:

jenkins-ci/mbed-os-ci_unittests
jenkins-ci/mbed-os-ci_build-GCC_ARM
jenkins-ci/mbed-os-ci_build-IAR
jenkins-ci/mbed-os-ci_build-ARM

0xc0170 · 2019-09-30T14:18:05Z

Will restart CI once the above review comment is resolved

0Grit · 2019-10-10T07:10:14Z

bump

Should be 115200

adbridge · 2019-10-11T10:16:36Z

CI started

mbed-ci · 2019-10-11T11:05:57Z

Test run: FAILED

Summary: 3 of 4 test jobs failed
Build number : 2
Build artifacts

Failed test jobs:

jenkins-ci/mbed-os-ci_build-ARM
jenkins-ci/mbed-os-ci_build-IAR
jenkins-ci/mbed-os-ci_build-GCC_ARM

adbridge · 2019-10-11T13:27:24Z

Suspected CI issue, restarted

mbed-ci · 2019-10-11T15:21:05Z

Test run: FAILED

Summary: 3 of 4 test jobs failed
Build number : 3
Build artifacts

Failed test jobs:

jenkins-ci/mbed-os-ci_build-IAR
jenkins-ci/mbed-os-ci_build-GCC_ARM
jenkins-ci/mbed-os-ci_build-ARM

0xc0170 · 2019-10-14T07:31:13Z

CI restarted

mbed-ci · 2019-10-14T08:21:20Z

Test run: FAILED

Summary: 3 of 4 test jobs failed
Build number : 4
Build artifacts

Failed test jobs:

jenkins-ci/mbed-os-ci_build-IAR
jenkins-ci/mbed-os-ci_build-GCC_ARM
jenkins-ci/mbed-os-ci_build-ARM

0xc0170 · 2019-10-14T09:20:30Z

The failures are expected, aren't they?

From https://github.com/ARMmbed/mbed-os-example-pelion#supported-platforms , there are only couple of supported platforms. The tests are passing for this. Shouldn't this example be tested with targets based on this table?

0xc0170 · 2019-10-14T09:20:50Z

@teetak01 Please review ^^

teetak01 · 2019-10-14T10:31:59Z

This should be tested vs. all boards present in the mbed_app.json. I suggest a dynamic parsing of that.

According to mbed_app.json in the example itself only these specific targets are listed. "K64F", "K66F", "NUCLEO_F429ZI", "UBLOX_EVK_ODIN_W2", "NUCLEO_F411RE", "DISCO_L475VG_IOT01A"

adbridge · 2019-10-14T10:47:27Z

This should be tested vs. all boards present in the mbed_app.json. I suggest a dynamic parsing of that.

That would require significant updates to the CI tools so doubt that is going to happen. I have added:
K64F, K66F, NUCLEO_F429ZI, UBLOX_EVK_ODIN_W2, NUCLEO_F411RE and DISCO_L475VG_IOT01A into here.

adbridge · 2019-10-14T10:48:12Z

CI started

mbed-ci · 2019-10-14T11:19:26Z

Test run: FAILED

Summary: 3 of 4 test jobs failed
Build number : 5
Build artifacts

Failed test jobs:

jenkins-ci/mbed-os-ci_build-ARM
jenkins-ci/mbed-os-ci_build-IAR
jenkins-ci/mbed-os-ci_build-GCC_ARM

0xc0170 · 2019-10-14T11:42:22Z

Failures look better now

[Error] mbed_cloud_dev_credentials.c@22,2: "Replace mbed_cloud_dev_credentials.c with your own developer cert."
[ERROR] ./mbed_cloud_dev_credentials.c:22:2: error: "Replace mbed_cloud_dev_credentials.c with your own developer cert."
#error "Replace mbed_cloud_dev_credentials.c with your own developer cert."

How to fix this one in our CI env?

trowbridgec · 2019-10-14T12:10:14Z

@adbridge
Can you also add the EP_AGORA target to your CI testing? We have a PR (ARMmbed/mbed-os-example-pelion#21) in to add our target to the mbed-os-example-pelion app.

adbridge · 2019-10-16T09:31:35Z

@adbridge
Canr you also add the EP_AGORA target to your CI testing? We have a PR (ARMmbed/mbed-os-example-pelion#21) in to add our target to the mbed-os-example-pelion app.

@trowbridgec We can't add that board here until we have it in our CI I'm afraid.

trowbridgec · 2019-10-16T13:44:15Z

@adbridge: @maclobdell just received our boards in for CI and is in the process of testing them right now. Assuming he gives them the green light, can the EP_AGORA target be added?

0xc0170 · 2019-10-18T13:49:49Z

@adbridge: @maclobdell just received our boards in for CI and is in the process of testing them right now. Assuming he gives them the green light, can the EP_AGORA target be added?

It definitely can be. Let @maclobdell request that via our test team to make sure it is in CI and we can add it to examples right after.

mbed-ci · 2019-10-18T16:25:49Z

Test run: FAILED

Summary: 3 of 4 test jobs failed
Build number : 6
Build artifacts

Failed test jobs:

jenkins-ci/mbed-os-ci_build-IAR
jenkins-ci/mbed-os-ci_build-ARM
jenkins-ci/mbed-os-ci_build-GCC_ARM

0xc0170 · 2019-10-21T09:15:10Z

I was too quick for CI here. We still need to figure out how to add cert header file. This needs work

0xc0170 · 2019-11-26T10:48:07Z

@adbridge Worth still keeping opened?

adbridge · 2019-11-26T11:04:21Z

@0xc0170 It's still required so I guess we are just waiting on the Pelion / tools guys to work out how to get this working in the CI

JanneKiiskila · 2019-12-11T13:26:22Z

Yep, we need to get this in. If we can't implement the dynamic target parsing, we need to keep updating the targets as go - once a month or so at least? A regular task we need to keep in mind...

0xc0170 · 2019-12-11T13:34:04Z

@0xc0170 It's still required so I guess we are just waiting on the Pelion / tools guys to work out how to get this working in the CI

@JanneKiiskila @adbridge Is there a ticket for this work to track this ? This would be good to have prior 6.0.0rc1 ?

adbridge · 2019-12-11T13:37:21Z

@JanneKiiskila @adbridge Is there a ticket for this work to track this ? This would be good to have prior 6.0.0rc1 ?

Not that I am aware of , this is a Pelion/tools problem as far as I know so would expect them to be working together to work out exactly what the issue is and how to fix it.....

teetak01 · 2019-12-11T17:20:39Z

Wrote a task with decription what is missing; https://jira.arm.com/browse/MBEDOSTEST-910

0xc0170 · 2020-01-03T12:44:14Z

I'll close this, will be reopened once ticket is resolved.

Add mbed-os-example-pelion

5e714b0

Primarily so that this example can be updated automatically with a pull request when updating Mbed OS version. Set to compile in the CI but not export or test.

adbridge requested a review from 0xc0170 September 27, 2019 14:54

adbridge added needs: review release-version: 5.14.1 labels Sep 27, 2019

0xc0170 approved these changes Sep 30, 2019

View reviewed changes

0xc0170 added needs: CI and removed needs: review labels Sep 30, 2019

teetak01 reviewed Sep 30, 2019

View reviewed changes

0xc0170 added needs: work and removed needs: CI labels Sep 30, 2019

Update baud rate of pelion example

b086965

Should be 115200

adbridge added needs: CI and removed needs: work labels Oct 11, 2019

0xc0170 added needs: work and removed needs: CI labels Oct 14, 2019

Update mbed-os-example-pelion for supported targets

23af290

According to mbed_app.json in the example itself only these specific targets are listed. "K64F", "K66F", "NUCLEO_F429ZI", "UBLOX_EVK_ODIN_W2", "NUCLEO_F411RE", "DISCO_L475VG_IOT01A"

adbridge added release-version: 5.14.2 and removed release-version: 5.14.1 labels Oct 14, 2019

adbridge removed the release-version: 5.14.2 label Nov 15, 2019

0xc0170 added the release-version: 6.0.0-alpha-1 First pre-release version of 6.0.0 label Dec 11, 2019

0xc0170 closed this Jan 3, 2020

0xc0170 removed needs: work release-version: 6.0.0-alpha-1 First pre-release version of 6.0.0 labels Jan 3, 2020

Add mbed-os-example-pelion #11588

Add mbed-os-example-pelion #11588

Uh oh!

Conversation

adbridge commented Sep 27, 2019

Description

Pull request type

Reviewers

Release Notes

Uh oh!

0xc0170 commented Sep 30, 2019

Uh oh!

teetak01 Sep 30, 2019

Choose a reason for hiding this comment

Uh oh!

mbed-ci commented Sep 30, 2019

Test run: FAILED

Uh oh!

0xc0170 commented Sep 30, 2019

Uh oh!

0Grit commented Oct 10, 2019

Uh oh!

adbridge commented Oct 11, 2019

Uh oh!

mbed-ci commented Oct 11, 2019

Test run: FAILED

Uh oh!

adbridge commented Oct 11, 2019

Uh oh!

mbed-ci commented Oct 11, 2019

Test run: FAILED

Uh oh!

0xc0170 commented Oct 14, 2019

Uh oh!

mbed-ci commented Oct 14, 2019

Test run: FAILED

Uh oh!

0xc0170 commented Oct 14, 2019

Uh oh!

0xc0170 commented Oct 14, 2019

Uh oh!

teetak01 commented Oct 14, 2019

Uh oh!

adbridge commented Oct 14, 2019

Uh oh!

adbridge commented Oct 14, 2019

Uh oh!

mbed-ci commented Oct 14, 2019

Test run: FAILED

Uh oh!

0xc0170 commented Oct 14, 2019

Uh oh!

trowbridgec commented Oct 14, 2019

Uh oh!

adbridge commented Oct 16, 2019

Uh oh!

trowbridgec commented Oct 16, 2019

Uh oh!

0xc0170 commented Oct 18, 2019

Uh oh!

mbed-ci commented Oct 18, 2019

Test run: FAILED

Uh oh!

0xc0170 commented Oct 21, 2019

Uh oh!

0xc0170 commented Nov 26, 2019

Uh oh!

adbridge commented Nov 26, 2019

Uh oh!

JanneKiiskila commented Dec 11, 2019

Uh oh!

0xc0170 commented Dec 11, 2019

Uh oh!

adbridge commented Dec 11, 2019

Uh oh!

teetak01 commented Dec 11, 2019

Uh oh!

0xc0170 commented Jan 3, 2020

Uh oh!

Uh oh!