10817 2016-12-16 00:47:38 +0000 oe-selftest: add a test for devtool modify on the kernel 2017-03-23 13:37:49 +0000 1 1 10 QA/Testing Build Testing general 2.3 x86 Multiple RESOLVED FIXED Medium+ enhancement 2.4 M1 1 bluelightning jose.perez.carranza gizero jair.de.jesus.gonzalez.plascencia jose.perez.carranza leonardo.sandoval.gonzalez richard.purdie ross.burton jair.de.jesus.gonzalez.plascencia --- --- No (bug/feature does not impact docs) oldest_to_newest 69180 0 bluelightning 2016-12-16 00:47:38 +0000 We need to create an oe-selftest test for "devtool modify virtual/kernel" to verify at least the following: 1) That it checks out the source correctly 2) That you can build the kernel successfully 3) That the resulting configuration is the same as what you get when you haven't run devtool modify on it 4) That you can make changes to the code and those get incorporated in a subsequent build 5) That you can make changes to the configuration and those get incorporated in a subsequent build 70057 1 jose.perez.carranza 2017-01-23 22:15:28 +0000 Patch sent for review http://lists.openembedded.org/pipermail/openembedded-core/2017-January/131636.html 71197 2 jose.perez.carranza 2017-03-10 22:06:22 +0000 V2 of the patch sent to the list http://lists.openembedded.org/pipermail/openembedded-core/2017-March/133982.html 71364 3 gizero 2017-03-16 16:28:21 +0000 How about also checking that changes can be finalised by finish/update-recipe. This might be or not in the scope of this specific test, but should probably be done. I just filed [1] while noticing that I can't capture kernel configuration fragments with devtool... [1] https://bugzilla.yoctoproject.org/show_bug.cgi?id=11171 71635 4 ross.burton 2017-03-23 13:37:49 +0000 Merged in oe-core 0fa3d331df7d5a5fbd8431febc75efe6bcc6f96b.