-
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
Nanostack release v704 #5602
Nanostack release v704 #5602
Conversation
… from b1c9efb..471121d 471121d Update apache license (ARMmbed#84) 7cb9f65 Enable COAP traces in Linux builds (ARMmbed#82) git-subtree-dir: features/nanostack/FEATURE_NANOSTACK/coap-service git-subtree-split: 471121d
@artokin Thanks, we will review it shortly |
One question - https://github.com/ARMmbed/mbed-os/tree/70e7b40468854d33431889a9cd415364c00a2501/features/nanostack/FEATURE_NANOSTACK/sal-stack-nanostack - all the files in the root are relevant (makefiles, scripts, .git files) |
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.
@artokin
The following points need addressing before this is considered suitable for 5.7 release:
-
Why is the structure:
features/nanostack/FEATURE_NANOSTACKinstead of just
features/FEATURE_NANOSTACK ?? -
clone_nanostack.sh
Should this be in the mbed-os repo? If so should it have a licence header ?
-
coap_service
a) Should the .sh, makefile etc files have licence headers ? Should these files even be here ?
b) How are the tests compiled and run? If these are to remain here and public then there should be documentation on how to run them ... -
/mbed-mesh-api/test/6lowpan_nd
This mentions yotta as a requirement - is this still correct? This is deprecated from mbed-os so is going to send mixed messages? Do these test instructions actually work when run from mbed-os clone ?
-
sal-stack-nanostack
Also has a huge set of unit tests in two different folders. Do we really want them here and if so there needs to be instructions on running them and licence headers in files accordingly...
General comment: We are not happy to take all the test code as it currently stands, if you do not have time to bring all that up to scratch including the running instructions prior to Thursday's release deadline, can i suggest that all the test code is removed ? It can always be added again at a later date when ready..
@0xc0170, Makefile and scripts are needed to execute unit tests. git-files are there like in the other "git-subtree" released components (coap-service, mbed-trace, etc). |
OK then if we are keeping them, have similar question to Anna, will wait for the answer to those. |
@adbridge, thanks for the comments.
@mikter and @TuomoHautamaki, how do we proceed with the unit tests? Any suggestions? |
I would actually propose not to modify any of those Makefiles, etc. that are from original repository. If this is not acceptable, then probably all the Makefiles and unittests have to be gone. Makes no sense to keep Makefiles just for unittests because no modifications to stack would be accepted here. All testing is to be done against the master copy of Nanostack's repository. Therefore, either remove all that is not relevant to Mbed OS, or keep structure intact for purpose of helping merges. |
… from 471121d..29bfb78 29bfb78 Add apache license to Makefiles and scripts (ARMmbed#85) git-subtree-dir: features/nanostack/FEATURE_NANOSTACK/coap-service git-subtree-split: 29bfb78
Previous commit will fix item 3a, license headers added to makefiles and scripts in coap-service |
Please note that there are already released components including similar unit tests in mbed OS which need the same guidelines (coap-service, libservice, mbed-client-randlib). In short term enabling release testing and helping merges seen more crucial than temporarily removing nanostack tests due to missing guidelines. Fully agree the need to have proper documentation for the unit tests. We will take action to solve this issue with coap-service, libservice, mbed-client-randlib and nanostack libraries but it will not be ready for mbed OS 5.7. |
Understood, thus our proposal is as below.
@SeppoTakalo +1. The rest of the tests in the repository will be taken care of separately. This scope is for nanostack, so lets focus about nanostack and its unittest or scripts within. |
@tommikas Can you please review the history of jenkins CI , are there any problems today we should be aware? |
Why is Nanostack still in a FEATURE_ directory? I'd expected this would always be part of the build now... So feature/nanostack/ Soon all FEATURE_ will be gone and we can move these to the root level like /networking/ |
@sg- , we still like to use existing FEATURE-configuration to include/exclude Nanostack from the application build. This ensures that existing applications are still working without surprises. |
When will that change and be part of the default build? |
@sg- I'll contact you to discuss more about this future change. Not in the scope of this release. |
Unit tests are now removed from Nanostack. All items should be solved now (unit tests in other components will be addressed separately). |
/morph build |
Build : SUCCESSBuild number : 625 Triggering tests/morph test |
Exporter Build : SUCCESSBuild number : 252 |
Test : SUCCESSBuild number : 447 |
Description
Nanostack v7.0.4 release for mbed-os-5.7
-Apache license added to files that were missing it
-Obsolete files removed
Libraries updated:
Status
READY