Skip to content

Remove FEATURE_STORAGE and all underlying deprecated features #10258

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

Merged
merged 1 commit into from
Apr 26, 2019

Conversation

davidsaada
Copy link
Contributor

Description

FEATURE_STORAGE and underlying features - cfstore, flash-journal and storage-volume-manager, have long been deprecated. This PR removes them all.
In addition, remove references to these in nanostack (used cfstore in uninvoked tests) and tools metadata such as astyle and doxygen.

Pull request type

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

Reviewers

@SenRamakri

Release Notes

Remove FEATURE_STORAGE and all underlying deprecated features: cfstore, flash-journal and storage-volume-manager.

@ciarmcom ciarmcom requested review from SenRamakri and a team March 28, 2019 18:00
@ciarmcom
Copy link
Member

@davidsaada, thank you for your changes.
@SenRamakri @ARMmbed/mbed-os-storage @ARMmbed/mbed-os-tools @ARMmbed/mbed-os-ipcore @ARMmbed/mbed-os-maintainers please review.

@@ -1,6 +1,6 @@
{
"test_target": {
"expected_features": ["BOOTLOADER", "STORAGE"],
"included_source": ["FEATURE_BOOTLOADER/lib1/lib1.c", "FEATURE_STORAGE/lib2/lib2.c"]
"expected_features": ["BOOTLOADER"],
Copy link
Contributor

Choose a reason for hiding this comment

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

Please don't remove code that tests how the tools work WRT features just because the feature that's used as test data is no longer part of Mbed OS

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I don't mind reverting this file, but will this work even if STORAGE feature and FEATURE_STORAGE directory no longer exist?
Alternatively, I can replace these with other feature and directory, if this only requires any two features.

Copy link
Contributor

Choose a reason for hiding this comment

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

Yes. it uses a local folder. You're welcome to rework it to not use the string "STORAGE" if you're so inclined, but I don't think it's worth the time.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thanks. Indeed got better things to do with my time. Reverted.

@SenRamakri
Copy link
Contributor

@cmonr and @ARMmbed/mbed-os-maintainers - Can we please tag this change for 5.12.1. Without this change we cannot compile with ARM Compiler 6.12 which is the ARM compiler version with latest Keil MDK. Im afraid there will be lot of developers trying to use latest Keil MDK with MbedOS and the builds will be broken. So we need this change in ASAP(5.12.1).

@cmonr
Copy link
Contributor

cmonr commented Mar 28, 2019

@SenRamakri @davidsaada

I'm not sure I understand. Why does removing this code happen to make compilation work with ARMC6?

And where is the tracking issue for this removal? Was it discovered during OOB?

@davidsaada davidsaada force-pushed the david_remove_feature_storage branch from 26f7b06 to 2a771fc Compare March 28, 2019 20:56
@davidsaada
Copy link
Contributor Author

@cmonr We had this change planned anyway. As for the ARMC6 problem, will let @SenRamakri answer that.

@davidsaada davidsaada force-pushed the david_remove_feature_storage branch from 2a771fc to 732dd36 Compare March 28, 2019 21:11
@SenRamakri
Copy link
Contributor

@cmonr - Its not discovered during OOB because OOB used ARMC 6.11 version. We have identified some header file conflicts with ARMC 6.12 with header files present under the directories which @davidsaada is trying to remove with this commit. I brought this up to him yesterday and he prioritized this change to fix ARMC 6.12 issue although it was planned for later.

Copy link
Contributor

@SenRamakri SenRamakri left a comment

Choose a reason for hiding this comment

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

@davidsaada - Changes look good to me, Ill approve.
Btw, are there any docs which also needs removed or changed based on this change?

@adbridge
Copy link
Contributor

My concern with this PR is that we explicit state in our guidelines that we do not deprecate features in patch releases. If there is a specific fix that is required for ARMC6 then I would prefer to see that split out into a separate PR that we can take into a patch release and then move the deprecation to the next minor...

@bulislaw
Copy link
Member

Mbed deprecation policy says that we can remove features that were marked as deprecated for at least 6 months. Can you confirm all of the removed items were explicitly marked as deprecated for at least 6 months?

Also that will need to go into 5.13 not any of the 5.12 patch releases.

@davidsaada
Copy link
Contributor Author

@adbridge @SenRamakri @bulislaw All three features have been deprecated since mbed-os 5.5.
Neither have any reference in our documentation.

@SenRamakri
Copy link
Contributor

Sounds good - But we need "VERSION" file removed to fix the ARMC 6.12 build failures for 5.12.1.
@davidsaada - Is that ok to just remove the VERSION file for now with a separate PR and target this PR for 5.13?

@davidsaada
Copy link
Contributor Author

Sounds good - But we need "VERSION" file removed to fix the ARMC 6.12 build failures for 5.12.1.
@davidsaada - Is that ok to just remove the VERSION file for now with a separate PR and target this PR for 5.13?

Will do (on Sunday). In that case I believe a tracking issue would help.

@0xc0170
Copy link
Contributor

0xc0170 commented Apr 11, 2019

@davidsaada What's the status here? The fix was merged, can this proceed?

@davidsaada
Copy link
Contributor Author

@davidsaada What's the status here? The fix was merged, can this proceed?

From my POV it can proceed. Nothing more I have to do here. But thought this would wait for 5.13.

@0xc0170 0xc0170 dismissed theotherjimmy’s stale review April 11, 2019 13:02

Review addressed

@0xc0170 0xc0170 removed the request for review from a team April 11, 2019 13:02
@0xc0170
Copy link
Contributor

0xc0170 commented Apr 11, 2019

CI started while waiting for reviews

@mbed-ci
Copy link

mbed-ci commented Apr 11, 2019

Test run: FAILED

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

Failed test jobs:

  • jenkins-ci/mbed-os-ci_exporter

@cmonr
Copy link
Contributor

cmonr commented Apr 12, 2019

CI job restarted: jenkins-ci/exporter

Failures appear relevant, but making sure.

@0xc0170
Copy link
Contributor

0xc0170 commented Apr 12, 2019

Restarted, latest failure was success but exporter reported failure

@0xc0170
Copy link
Contributor

0xc0170 commented Apr 12, 2019

@bulislaw Please review

@mbed-ci
Copy link

mbed-ci commented Apr 17, 2019

Test run: FAILED

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

Failed test jobs:

  • jenkins-ci/mbed-os-ci_greentea-test

Copy link
Member

@bulislaw bulislaw left a comment

Choose a reason for hiding this comment

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

Could you like to PR with docs changes?

@adbridge
Copy link
Contributor

ci started

@mbed-ci
Copy link

mbed-ci commented Apr 25, 2019

Test run: SUCCESS

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

@adbridge adbridge merged commit b1cd3da into ARMmbed:master Apr 26, 2019
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.

9 participants