Release candidate 2 for mbed-os-5.9.0 #7122

adbridge · 2018-06-05T14:12:03Z

No description provided.

In case when base tick count is different than next tick count check first if the difference is equal to 1 tick (this is what we are looking for) if not then decrease the tick count. Repeat counting process few times before incrementing the number of cycles in case when base tick count is equal to next tick count.

…h release

…ions

… path separator.

…. Corrected instance of hard-coded unix path separator.

Remove additional redundant libraries, that were accidently added in merges

… iteration over values. Py3 no longer supports dictionaries that self-modify their item lists during iteration.

…art of test that was incompatible with Py3 on Windows.

… a BufferedReader instead of a file.

adbridge · 2018-06-05T14:18:54Z

/morph build
/morph mbed2-release

mbed-ci · 2018-06-05T15:19:44Z

Build : SUCCESS

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

Triggering tests

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

mbed-ci · 2018-06-05T16:49:02Z

Test : SUCCESS

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

studavekar · 2018-06-05T16:58:39Z

/morph mbed2-release

studavekar · 2018-06-05T19:36:40Z

mbed2 release command has to only morph command in the comment for it to get triggered
/morph mbed2-release

mbed-ci · 2018-06-05T19:42:13Z

Build : SUCCESS

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

Triggering tests

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

mbed-bot · 2018-06-05T20:03:43Z

Result: FAILURE

Your command has finished executing! Here's what you wrote!

/morph mbed2-release

Output

mbed Build Number: 106

Build failed!

mbed-ci · 2018-06-05T21:19:36Z

Test : SUCCESS

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

mbed-ci · 2018-06-05T21:51:25Z

Exporter Build : SUCCESS

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

cmonr · 2018-06-05T22:21:49Z

/morph build

mbed-ci · 2018-06-05T23:22:29Z

Build : SUCCESS

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

Triggering tests

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

mbed-ci · 2018-06-06T01:20:13Z

Test : SUCCESS

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

mbed-ci · 2018-06-06T01:32:45Z

Exporter Build : SUCCESS

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

cmonr · 2018-06-06T03:36:20Z

@TomoYamanaka @toyowata Do you think you could take a look at these issues today? It's not apparent because the last build didn't report properly, but the most recent ci-morph-mbed2-build job failed, with only the Cortex-A devices not building.

I've attached a few of the logs that have caused the failure. The failure is compiler agnostic, and appears to be rooted in a requirement on mbed_rtx_conf.h.

Reproduction of the error is actually quite simple. Checkin out this PR branch, and running the command in the logs results in the failure. For reference, the following is what I use whenever I need to check out a specific branch:

git clone https://github.com/ARMmbed/mbed-os
cd mbed-os

git fetch refs/pull/7122/head:pr7122
git checkout pr7122

Any help and/or insight y'all could provide would be helpful as we're trying to get this out ASAP. We have the extreme option of removing Mbed 2 support for the devices, but of course we'd like to avoid this if at all possible.

Notifier should be passed to build libs functions, otherwise it's none and fails. Missing notify object in toolchain also fixed.

it was removed recently, not used anymore

0xc0170 · 2018-06-06T07:22:08Z

I've attached a few of the logs that have caused the failure. The failure is compiler agnostic, and appears to be rooted in a requirement on mbed_rtx_conf.h.

fixed on master. I changed the label version for the fix, should be here. And also another PR. We need to run release candidate script once more, should pick up 3 more commits. I can build with those 3 additional commits locally (tested few toolchains, RZ A1H, and few other targets).

@TomoYamanaka @toyowata Do you think you could take a look at these issues today? It's not apparent because the last build didn't report properly, but the most recent ci-morph-mbed2-build job failed, with only the Cortex-A devices not building.

Resolved on master, will be also here once we add 3 additional commits.

0xc0170 · 2018-06-06T07:25:15Z

@adbridge If we run release script, those 3 additional commits should be in.

See #7053 and #6914. However one commit from here is not yet on master (d743f7f), I'll try to add it to #7132

0xc0170 · 2018-06-06T07:36:11Z

/morph build
/morph mbed2-release

mbed-ci · 2018-06-06T08:46:48Z

Build : SUCCESS

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

Triggering tests

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

0xc0170 · 2018-06-06T08:51:11Z

/morph mbed2-release

Update: I should have restarted build not release 😖 will fix

0xc0170 · 2018-06-06T09:02:37Z

/morph mbed2-build

mbed-bot · 2018-06-06T09:16:36Z

Result: FAILURE

Your command has finished executing! Here's what you wrote!

/morph mbed2-release

Output

mbed Build Number: 107

Build failed!

adbridge · 2018-06-06T09:57:44Z

mbed2 still failing, several Nucleo boards.

04:02:05   * NUCLEO_F030R8::ARM::MBED
04:02:05         "/home/jenkins/build_node_4_2/workspace/bm_wrap/1698/mbed-os/targets/TARGET_STM/rtc_api.c", line 289: Warning:  #223-D: function "__HAL_RTC_WAKEUPTIMER_GET_IT" declared implicitly
04:02:05         "/home/jenkins/build_node_4_2/workspace/bm_wrap/1698/mbed-os/targets/TARGET_STM/rtc_api.c", line 293: Warning:  #223-D: function "__HAL_RTC_WAKEUPTIMER_CLEAR_FLAG" declared implicitly
04:02:05         "/home/jenkins/build_node_4_2/workspace/bm_wrap/1698/mbed-os/targets/TARGET_STM/rtc_api.c", line 309: Warning:  #223-D: function "__HAL_RTC_WAKEUPTIMER_EXTI_CLEAR_FLAG" declared implicitly
04:02:05         "/home/jenkins/build_node_4_2/workspace/bm_wrap/1698/mbed-os/targets/TARGET_STM/rtc_api.c", line 359: Warning:  #223-D: function "HAL_RTCEx_SetWakeUpTimer_IT" declared implicitly
04:02:05         "/home/jenkins/build_node_4_2/workspace/bm_wrap/1698/mbed-os/targets/TARGET_STM/rtc_api.c", line 359: Error:  #20: identifier "RTC_WAKEUPCLOCK_RTCCLK_DIV4" is undefined
04:02:05         "/home/jenkins/build_node_4_2/workspace/bm_wrap/1698/mbed-os/targets/TARGET_STM/rtc_api.c", line 380: Warning:  #223-D: function "HAL_RTCEx_DeactivateWakeUpTimer" declared implicitly
04:02:05         /home/jenkins/build_node_4_2/workspace/bm_wrap/1698/mbed-os/targets/TARGET_STM/rtc_api.c: 5 warnings, 1 error

0xc0170 · 2018-06-06T10:06:03Z

@ARMmbed/team-st-mcd Please review above failure. I was able to reproduce this on master, a bug in rtc implementation, I am investigating.

0xc0170 · 2018-06-06T10:19:03Z

@ARMmbed/team-st-mcd Please review above failure. I was able to reproduce this on master, a bug in rtc implementation, I am investigating.

Tracking issue with details: #7140

mbed-ci · 2018-06-06T10:58:43Z

Exporter Build : SUCCESS

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

jeromecoutant · 2018-06-06T11:38:36Z

Hi
Please try #7143
Regards,

studavekar · 2018-06-06T15:13:44Z

Test results : http://mbed-os-logs.s3-website-us-west-1.amazonaws.com/?prefix=logs/7122/2035

Comment from CI failed with following traceback hinting github server issue

Caused: org.kohsuke.github.HttpException: Server returned HTTP response code: -1, message: 'null' for URL: https://api.github.com/repos/ARMmbed/mbed-os/commits/c9338d180069087199744aa9fa4e9310737d8d95
	at org.kohsuke.github.Requester.parse(Requester.java:633)
	at org.kohsuke.github.Requester.parse(Requester.java:631)
	at org.kohsuke.github.Requester.parse(Requester.java:631)
	at org.kohsuke.github.Requester.parse(Requester.java:594)
	at org.kohsuke.github.Requester._to(Requester.java:272)
	at org.kohsuke.github.Requester.to(Requester.java:234)
	at org.kohsuke.github.GHRepository.getCommit(GHRepository.java:944)
	at org.jenkinsci.plugins.pipeline.githubstatusnotification.GitHubStatusNotificationStep$Execution.run(GitHubStatusNotificationStep.java:377)
Caused: java.lang.IllegalArgumentException: The specified commit does not exist in the specified repository
	at org.jenkinsci.plugins.pipeline.githubstatusnotification.GitHubStatusNotificationStep$Execution.run(GitHubStatusNotificationStep.java:379)
	at org.jenkinsci.plugins.pipeline.githubstatusnotification.GitHubStatusNotificationStep$Execution.run(GitHubStatusNotificationStep.java:355)
	at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47)
	at hudson.security.ACL.impersonate(ACL.java:260)
	at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

mprse and others added 26 commits June 5, 2018 15:05

OS version is not available in code, need a fix for this in next patc…

39a08f7

…h release

Removed test that needs to be rearchitected due to subprocess limitat…

8de0876

…ions

Modified memap tests to perform file path comparisons agnostic of the…

b5789f3

… path separator.

Added windows path separator to list of alphabet characters to ignore…

03a51d6

…. Corrected instance of hard-coded unix path separator.

Updated local variable in memap/parse_test.py to be lower case.

2c750c4

Remove redundant Cryptocell libraries

54e2bae

Remove additional redundant libraries, that were accidently added in merges

Edit warning about FEATURE_UVISOR being deprecated

78de5c3

Update uvisor_deprecation.h

ac03c12

set the tolerance to 5% if NO_SYSTICK is enabled

5c8236e

us_ticker is not yet initialised at this stage

998b4b8

Fix for filename capture not working

e2fe4fa

Fix for error report not printing when calling error API

19f2a73

Do not capture filename for release builds

01f7a33

fix not updating size of array

5aaca08

check for invalid param

ab51109

fix erroneous assert

bf4a804

Nordic FIX: place observers sequentially in flash.

3fc2d33

BLE Nordic: Initialize and teardown tls platform context

f4089a0

Encapsulated Windows file separator for proper regex parsing

f84c74a

Added basestring import for proper string concatenation in Py3

a7f73de

Modified LazyDict to inherit from object instead of dict, and removed…

6daf367

… iteration over values. Py3 no longer supports dictionaries that self-modify their item lists during iteration.

Sets module no longer needed to use set()

e8661f5

Modified memap path separator parsing to support Py3. Had to remove p…

25c49f2

…art of test that was incompatible with Py3 on Windows.

Modified IntelHex tofile parameter to use path. Py3 open(...) returns…

cc5a36b

… a BufferedReader instead of a file.

Removed extraneous file open

97028c5

Updated lines missed during Notifier API migration

d743f7f

0xc0170 added 2 commits June 6, 2018 08:03

build: fix notifier typo and passing to builds API

3e8488a

Notifier should be passed to build libs functions, otherwise it's none and fails. Missing notify object in toolchain also fixed.

test: remove verbose from buil libs calls

d3e48c2

it was removed recently, not used anymore

Fix RTOS-less build failed with cmsis/RTE_Components.h

c9338d1

cmonr approved these changes Jun 6, 2018

View reviewed changes

0xc0170 merged commit 4aa2bf6 into mbed-os-5.9 Jun 6, 2018

theotherjimmy deleted the 5.9-release-candidate branch June 20, 2018 13:46

Release candidate 2 for mbed-os-5.9.0 #7122

Release candidate 2 for mbed-os-5.9.0 #7122

Uh oh!

Conversation

adbridge commented Jun 5, 2018

Uh oh!

adbridge commented Jun 5, 2018

Uh oh!

mbed-ci commented Jun 5, 2018

Triggering tests

Uh oh!

mbed-ci commented Jun 5, 2018

Uh oh!

studavekar commented Jun 5, 2018

Uh oh!

studavekar commented Jun 5, 2018

Uh oh!

mbed-ci commented Jun 5, 2018

Triggering tests

Uh oh!

mbed-bot commented Jun 5, 2018

Output

Uh oh!

mbed-ci commented Jun 5, 2018

Uh oh!

mbed-ci commented Jun 5, 2018

Uh oh!

cmonr commented Jun 5, 2018

Uh oh!

mbed-ci commented Jun 5, 2018

Triggering tests

Uh oh!

mbed-ci commented Jun 6, 2018

Uh oh!

mbed-ci commented Jun 6, 2018

Uh oh!

cmonr commented Jun 6, 2018

Uh oh!

0xc0170 commented Jun 6, 2018

Uh oh!

0xc0170 commented Jun 6, 2018

Uh oh!

0xc0170 commented Jun 6, 2018

Uh oh!

mbed-ci commented Jun 6, 2018

Triggering tests

Uh oh!

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

Uh oh!

Uh oh!

0xc0170 commented Jun 6, 2018

Uh oh!

mbed-bot commented Jun 6, 2018

Output

Uh oh!

adbridge commented Jun 6, 2018

Uh oh!

0xc0170 commented Jun 6, 2018

Uh oh!

0xc0170 commented Jun 6, 2018

Uh oh!

mbed-ci commented Jun 6, 2018

Uh oh!

jeromecoutant commented Jun 6, 2018

Uh oh!

studavekar commented Jun 6, 2018

Uh oh!

Uh oh!

0xc0170 commented Jun 6, 2018 •

edited

Loading