Skip to content

Conversation

@ithinuel
Copy link
Member

@ithinuel ithinuel commented Jun 5, 2020

Summary of changes

This PR adds armmbed/mbed-os-example-aws to the CI build test list.

Impact of changes

None

Migration actions required

None

Documentation

None

Pull request type

[x] Patch update (Bug fix / Target update / Docs update / Test update / Refactor)
[] Feature update (New feature / Functionality change / New API)
[] Major update (Breaking change E.g. Return code change / API behaviour change)

Test results

[] No Tests required for this change (E.g docs only update)
[x] Covered by existing mbed-os tests (Greentea or Unittest)
[] Tests / results supplied as part of this PR

Reviewers


@ciarmcom ciarmcom requested review from a team June 5, 2020 09:00
@ciarmcom
Copy link
Member

ciarmcom commented Jun 5, 2020

@ithinuel, thank you for your changes.
@ARMmbed/mbed-os-tools @ARMmbed/mbed-os-maintainers please review.

"compile" : true,
"export": true,
"test" : false,
"baud_rate": 9600,
Copy link

@MarceloSalazar MarceloSalazar Jun 5, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch!

@evedon evedon requested a review from jamesbeyond June 5, 2020 10:07
@LDong-Arm
Copy link
Contributor

Blocked by ARMmbed/mbed-os-example-for-aws#3

@0xc0170
Copy link
Contributor

0xc0170 commented Jun 8, 2020

Blocked by ARMmbed/mbed-os-example-for-aws#3

To verify, I'll trigger now CI , should fail

@mergify mergify bot added needs: work and removed needs: CI labels Jun 8, 2020
@mbed-ci
Copy link

mbed-ci commented Jun 8, 2020

Test run: FAILED

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

Failed test jobs:

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

@0xc0170
Copy link
Contributor

0xc0170 commented Jun 9, 2020

CI confirmed, blocked by ARMmbed/mbed-os-example-for-aws#3

@adbridge adbridge added the release-type: patch Indentifies a PR as containing just a patch label Jun 11, 2020
@LDong-Arm
Copy link
Contributor

CI confirmed, blocked by ARMmbed/mbed-os-example-aws#3

Fixed now, this PR should work. Could you trigger the CI again? @0xc0170

Copy link
Contributor

@LDong-Arm LDong-Arm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@0xc0170
Copy link
Contributor

0xc0170 commented Jun 17, 2020

Looks like GCC ARM already failed, please review (logs will be published once arm also completes)

@mbed-ci
Copy link

mbed-ci commented Jun 17, 2020

Test run: FAILED

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

Failed test jobs:

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

@LDong-Arm
Copy link
Contributor

LDong-Arm commented Jun 17, 2020

@0xc0170 Looks like we have duplicated copies of the wifi-ism43362 library.

During the Greentea stage, the CI script added that library into the mbed-os/ directory:

[2020-06-17T09:47:02.112Z] + python -m mbed add wifi-ism43362
[Pipeline] // dir
[Pipeline] // dir
[Pipeline] // dir
[Pipeline] sh
[2020-06-17T09:47:02.378Z] + export DAPLINK_TIMESTAMP=0
[2020-06-17T09:47:02.378Z] + echo 
[2020-06-17T09:47:02.378Z] + echo python -m mbed test --compile -j 8 -m NUCLEO_F429ZI -t GCC_ARM --build-data BUILD/tests/build_data.json -DMBED_TRAP_ERRORS_ENABLED=1 -DSKIP_TIME_DRIFT_TESTS=1 

But it doesn't seem to clean it up afterwards.

When it came to testing our AWS example, the example fetched wifi-ism43362 into its own directory and we ended up with two copies.

@LDong-Arm
Copy link
Contributor

In fact, mbed-os-example-wifi relies on the wifi-ism43362 added by the CI script. (In a non-CI setup, the README tells the user to manually import it.)

If we add a step to clean it up, I suppose the AWS example will work but the WiFi example will not compile in CI anymore... We need to align them I guess.

@0xc0170
Copy link
Contributor

0xc0170 commented Jun 17, 2020

@LDong-Arm please talk to @jamesbeyond how to address this wifi copy/clean up issue

"sub-repo-example": false,
"subs": [],
"features" : [],
"targets" : [],
Copy link
Contributor

@LDong-Arm LDong-Arm Jun 17, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we limit the targets? For example, the previous CI run also tried to build for NUCLEO_F411RE and failed, and I don't think it's a WiFi or Ethernet target.

It's due to the lack of TRNG on this target, see ARMmbed/mbed-os-example-tls-socket#34

For the WiFi example (line 120) we only build it for one target.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe K64F (Ethernet), and one WiFi target TBC

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should limit to a few targets with supported HW. @jamesbeyond

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we have a blocker created for this ? To my understanding this should be in 6.1 correct?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This needs to go in 6.1.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okay if we set targets in the future, since the example is disabled for now...

@0xc0170
Copy link
Contributor

0xc0170 commented Jun 22, 2020

This needs to go in 6.1.

@LDong-Arm Please let us know how to proceed here. I've reviewed the dependencies and it's not clear to me (providing the status here would help). If we can resolve this by end of today it would be great.

0xc0170
0xc0170 previously approved these changes Jun 22, 2020
@evedon
Copy link
Contributor

evedon commented Jun 22, 2020

This needs to go in 6.1.

@LDong-Arm Please let us know how to proceed here. I've reviewed the dependencies and it's not clear to me (providing the status here would help). If we can resolve this by end of today it would be great.

We agreed to set "targets" to DISCO_L475VG_IOT01A and K64F and "compile" to false pending updates to CI that will be done post 6.1.

@ithinuel ithinuel changed the title add mbed-os-example-aws to the test build list add mbed-os-example-aws to the example list Jun 22, 2020
@mergify mergify bot dismissed 0xc0170’s stale review June 22, 2020 13:16

Pull request has been modified.

@0xc0170
Copy link
Contributor

0xc0170 commented Jun 22, 2020

CI started

"sub-repo-example": false,
"subs": [],
"features" : [],
"targets" : [],
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okay if we set targets in the future, since the example is disabled for now...

@mbed-ci
Copy link

mbed-ci commented Jun 22, 2020

Test run: SUCCESS

Summary: 6 of 6 test jobs passed
Build number : 3
Build artifacts

@0xc0170 0xc0170 merged commit 107d9bb into ARMmbed:master Jun 22, 2020
@mergify mergify bot removed the ready for merge label Jun 22, 2020
@adbridge adbridge added release-version: 6.1.0 Release-pending and removed release-type: patch Indentifies a PR as containing just a patch Release-pending labels Jun 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants