-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove uVisor from mbed-os #7592
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One question about the test, if its fine for removal
@@ -1,8 +1,3 @@ | |||
{ | |||
"name": "lib2", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removing tools/test/config/feature_recursive_add
test as it uses uvisor feature, wont need any replacement?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, lets do that! (Someone else needs to review the details)
/morph build |
Build : FAILUREBuild number : 2727 |
@orenc17 Thanks for the quick fix, but please also fix the intentation in that particular function. On a quick glance, it was not obvious why that was a fix. |
rtos/TARGET_CORTEX/mbed_boot.c
Outdated
@@ -712,7 +712,6 @@ void __iar_program_start( void ) | |||
low_level_init_needed_local = __low_level_init(); | |||
if (low_level_init_needed_local) { | |||
__iar_data_init3(); | |||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is an error that this is actually fixing? I don't think this is related to uvisor anyhow.
By removing }
, the lines 717 and 718 becomes unaligned.
2556c64
to
feb9362
Compare
/morph build |
Build : SUCCESSBuild number : 2734 Triggering tests/morph test |
Test : SUCCESSBuild number : 2461 |
Exporter Build : SUCCESSBuild number : 2368 |
@studavekar FYI |
Once this PR gets in we would need to
cc @ARMmbed/mbed-os-maintainers for suggestions, how do we take this PR formward. |
As much as we'd like to move this forward, removing uVisor at this point would cause one of two things to happen:
The safest time to pull this in will probably be immediately after the last patch release is merged, at which point we won't have to worry about the 5.9 branch's CI. |
I think the solution for now is to park this PR until the second to last patch release is made. |
Is 5.9.5 the last patch release of 5.9? |
@mikisch81 Sorry, it's not. 5.9.6 will be happening next week, then 5.9.7 code freeze (the last patch) will be on Sept 6th. @ARMmbed/mbed-os-maintainers |
Can we get that in for 5.10? |
This was the plan every one agreed on. |
Rebased on top of master and remover #7830 |
Alright, so here's the plan. This is ready to go (aside from another run of CI since rebasing updates commit hashes), We need this to come in as a part of 5.10, but not come into the 5.9.x branch. We should be able to do that by simply leaving the 5.10 label, and getting this merged before then. Once this comes in, we'll remove the "AWS-CI uVisor Build & Test" merge check from the master branch, but keep it in the 5.9 branch. For 5.9.7, if we encounter any patches that for some reason don't manage to pass "AWS-CI uVisor Build & Test" once the release PR is being made, we'll remove it from the patch and only bring it in for 5.10. After 5.9.7 has been released, the Jenkins job(s) behind "AWS-CI uVisor Build & Test" can be removed. @orenc17 @alzix @ARMmbed/mbed-os-maintainers Sound like a plan? |
Finally someone with a plan. LGTM. |
/morph build |
Build : SUCCESSBuild number : 2898 Triggering tests/morph test |
Exporter Build : FAILUREBuild number : 2523 |
Ooph. License checkout issues. /morph export-build |
Exporter Build : SUCCESSBuild number : 2526 |
/morph uvisor-test |
What do we expect uvisor-test check to do when this PR removed uVisor? |
Test : SUCCESSBuild number : 2649 |
@alzix My mistake, was on autopilot. |
Bringing this in. I disabled the test in GitHub for the master branch, but I guess the check isn't going away since it was run for this PR. @ARMmbed/mbed-os-maintainers Make note that uVisor will not be tested on master, and if a PR fails for 5.9.7, it will be taken out of the patch. |
Remove uVisor from mbed-os
Pull request type