Rollup PR: Rerun falsely-failed PRs for 5.11-RC1 #8800

0xc0170 · 2018-11-19T14:04:42Z

Description

List of PR:

Pull request type

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

…s with multiple segments, as required by NRF52 bootloader.

* Remove max_app_addr logic from tools/config/__init__.py as it was not working properly with some of the .hex files.

NRF Softdevice hex file can be in chunks. Make sure we account for the space where the bootloader resides by including all the chunks within the end of rom marker. This will clearly mark out the initial bootloader region.

RAM/ROM memory data of target is required for statistics and linker files, goal here is to fetch maximum 4 RAM/ROM regions from CMSIS pack and make them available for C/C++/Linker flags as defines

Update the padding sequence so that the gaps are padded after all the regions are merged. This avoids overwriting active regions and serializes the process.

Rename loop varibles for better readability and formatting changes.

Patch from the end of the first segment. Remove unused code.

1. Adding SRAM in available ram 2. If the target doesn't exist in cmsis but targets.json, handle accordingly and raise apt exceptions where needed. 3. If no sram is provided, raise exception

Internal RAM / ROM memory size and start address of target can be fetched using `mbed_stats_sys_get()` API.

1, add "extern "C" {} " to "wifi_ind.h" for being called by CPP files.

…need a try/catch when we call it. Moved "bootloader_not_supported" check to where it was and handle that exception at only one place. Removed ram/rom size info for realtek from targets.json. THe info we have is not correct. was Not handling config exceptions from regions and ram_regions property adding rom-ram info for REALTEK_RTL8195AM

…into dev_rollup

0xc0170 · 2018-11-19T17:35:34Z

/morph build

mbed-ci · 2018-11-19T18:30:31Z

Build : SUCCESS

Build number : 3678
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/8800/

Triggering tests

/morph test
/morph export-build
/morph mbed2-build

mbed-ci · 2018-11-19T19:29:06Z

Exporter Build : SUCCESS

Build number : 3280
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/exporter/8800/

mbed-ci · 2018-11-19T20:13:33Z

Test : FAILURE

Build number : 3448
Test logs :http://mbed-os-logs.s3-website-us-west-1.amazonaws.com/?prefix=logs/8800/3448

cmonr · 2018-11-19T20:33:15Z

/morph test

mbed-ci · 2018-11-19T22:03:26Z

Test : FAILURE

Build number : 3449
Test logs :http://mbed-os-logs.s3-website-us-west-1.amazonaws.com/?prefix=logs/8800/3449

cmonr · 2018-11-19T22:26:02Z

/morph test

mbed-ci · 2018-11-19T23:56:14Z

Test : FAILURE

Build number : 3450
Test logs :http://mbed-os-logs.s3-website-us-west-1.amazonaws.com/?prefix=logs/8800/3450

cmonr · 2018-11-20T01:22:35Z

On the plus side, the failures for the last run seem to have passed on their own, sans network issues.

Restarting.
/morph test

mbed-ci · 2018-11-20T03:04:58Z

Test : FAILURE

Build number : 3452
Test logs :http://mbed-os-logs.s3-website-us-west-1.amazonaws.com/?prefix=logs/8800/3452

cmonr · 2018-11-20T03:11:57Z

Welp, I can say I tried. Of all the ways this could have failed, it had to be this one.
Restarting, while the stability window is still open.
/morph test

cmonr

The NRF PR will not completely go in, since Russ added more commits, but it will be good to have what's here in for now.

deepikabhavnani · 2018-11-20T04:03:06Z

(Fingers Crossed)

mbed-ci · 2018-11-20T08:09:19Z

Test : FAILURE

Build number : 3455
Test logs :http://mbed-os-logs.s3-website-us-west-1.amazonaws.com/?prefix=logs/8800/3455

0xc0170 · 2018-11-20T08:44:24Z

I fetched the binaries, run 2 failed test multiple times, can't reproduce it on K64F

/morph test

mbed-ci · 2018-11-20T10:14:51Z

Test : FAILURE

Build number : 3456
Test logs :http://mbed-os-logs.s3-website-us-west-1.amazonaws.com/?prefix=logs/8800/3456

deepikabhavnani · 2018-11-20T12:26:54Z

fetched the binaries, run 2 failed test multiple times, can't reproduce it on K64F

Should we replace the K64F in CI?

0xc0170 · 2018-11-20T12:50:24Z

Not sure if that helps but worth trying (@cmonr was looking at this option) , see #8807 (comment). it fails for 3 kinetis devices.

0xc0170 · 2018-11-21T07:07:38Z

/morph build

0xc0170 · 2018-11-21T09:16:14Z

/morph build

mbed-ci · 2018-11-21T11:18:22Z

Build : SUCCESS

Build number : 3700
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/8800/

Triggering tests

/morph test
/morph export-build
/morph mbed2-build

mbed-ci · 2018-11-21T13:36:02Z

Test : FAILURE

Build number : 3469
Test logs :http://mbed-os-logs.s3-website-us-west-1.amazonaws.com/?prefix=logs/8800/3469

mbed-ci · 2018-11-21T14:49:12Z

Exporter Build : FAILURE

Build number : 3297
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/exporter/8800/

mbed-ci · 2018-11-21T17:18:26Z

Test run: SUCCESS

Summary: 4 of 4 test jobs passed
Build number : 2
Build artifacts
Build logs

cmonr · 2018-11-21T17:20:41Z

First PR with new CI!

Ignoring old CI jobs:

ci-morph-build
ci-morph-exporter
ci-morph-test

cmonr · 2018-11-21T22:46:05Z

Closing since will regenerate with more PRs, and some other PRs need to be removed.

Jammu Kekkonen and others added 30 commits September 12, 2018 09:30

Fix bootloader build region generation and add support for bootloader…

4952e31

…s with multiple segments, as required by NRF52 bootloader.

Review fixes for bootloader region generation

ae4b67e

Review fixes 2 for bootloader region generation

c069cef

Remove max_app_addr checking from .hex

fac5ff4

* Remove max_app_addr logic from tools/config/__init__.py as it was not working properly with some of the .hex files.

tools: process bootloader chunks

2da8950

NRF Softdevice hex file can be in chunks. Make sure we account for the space where the bootloader resides by including all the chunks within the end of rom marker. This will clearly mark out the initial bootloader region.

tools: update build_api and __init__ as per review comments

e28c260

Fetch RAM/ROM information from CMSIS pack and add as defines

27f20c7

RAM/ROM memory data of target is required for statistics and linker files, goal here is to fetch maximum 4 RAM/ROM regions from CMSIS pack and make them available for C/C++/Linker flags as defines

tools: Update build_api padding method

bd40457

Update the padding sequence so that the gaps are padded after all the regions are merged. This avoids overwriting active regions and serializes the process.

tools: Update build_api

858a7a8

Rename loop varibles for better readability and formatting changes.

Add ESP8266 driver v1.7

8dd6a5d

esp8266 driver - don't set UART flow control if no support

934472b

tools: fix up build_api padding logic and clean up unused code

38ce7b1

Patch from the end of the first segment. Remove unused code.

Fixing some corner cases

3956451

1. Adding SRAM in available ram 2. If the target doesn't exist in cmsis but targets.json, handle accordingly and raise apt exceptions where needed. 3. If no sram is provided, raise exception

Missed one change to convert into right data type

1627968

Add RAM/ROM memory statistics to system stats structure

ad736e9

Internal RAM / ROM memory size and start address of target can be fetched using `mbed_stats_sys_get()` API.

Add tests to verify RAM/ROM sizes

e3c4dae

wifi-headerfile-updates

c97d343

1, add "extern "C" {} " to "wifi_ind.h" for being called by CPP files.

Adding Murata WSM-BL241 as new target

8ef1378

Removing unnecessary pin defines

1bdfcba

Adding LED defines for CI

ec78ca9

Incorporating review comments

fce42ae

Changing license header

ff55961

ifdef ram/rom size/start in case they dont exist

329c553

Crash Reporting Design

d4fc8fe

Crash reporting design doc

5489eac

Updated design doc

28a0b45

Adding usage scenarios

a6e7604

Fixed sentences and context

c3d2c44

Boot sequence diagram added

a721158

Merge branch 'br-Murata-BL241' of https://github.com/ashok-rao/mbed-os …

dfe717e

…into dev_rollup

cmonr changed the title ~~Rollup for 5.11rc1~~ Rollup PR: Rerun falsely-failed PRs for 5.11-RC1 Nov 19, 2018

cmonr approved these changes Nov 20, 2018

View reviewed changes

cmonr closed this Nov 21, 2018

cmonr removed the needs: CI label Nov 21, 2018

Rollup PR: Rerun falsely-failed PRs for 5.11-RC1 #8800

Rollup PR: Rerun falsely-failed PRs for 5.11-RC1 #8800

Uh oh!

Conversation

0xc0170 commented Nov 19, 2018 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Description

Pull request type

Uh oh!

0xc0170 commented Nov 19, 2018

Uh oh!

mbed-ci commented Nov 19, 2018

Triggering tests

Uh oh!

mbed-ci commented Nov 19, 2018

Uh oh!

mbed-ci commented Nov 19, 2018

Uh oh!

cmonr commented Nov 19, 2018

Uh oh!

mbed-ci commented Nov 19, 2018

Uh oh!

cmonr commented Nov 19, 2018

Uh oh!

mbed-ci commented Nov 19, 2018

Uh oh!

cmonr commented Nov 20, 2018

Uh oh!

mbed-ci commented Nov 20, 2018

Uh oh!

cmonr commented Nov 20, 2018

Uh oh!

cmonr left a comment

Choose a reason for hiding this comment

Uh oh!

deepikabhavnani commented Nov 20, 2018

Uh oh!

mbed-ci commented Nov 20, 2018

Uh oh!

0xc0170 commented Nov 20, 2018

Uh oh!

mbed-ci commented Nov 20, 2018

Uh oh!

deepikabhavnani commented Nov 20, 2018

Uh oh!

0xc0170 commented Nov 20, 2018

Uh oh!

0xc0170 commented Nov 21, 2018

Uh oh!

0xc0170 commented Nov 21, 2018

Uh oh!

mbed-ci commented Nov 21, 2018

Triggering tests

Uh oh!

mbed-ci commented Nov 21, 2018

Uh oh!

mbed-ci commented Nov 21, 2018

Uh oh!

mbed-ci commented Nov 21, 2018

Uh oh!

cmonr commented Nov 21, 2018

Uh oh!

cmonr commented Nov 21, 2018

Uh oh!

Uh oh!

0xc0170 commented Nov 19, 2018 •

edited

Loading