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
Patch sent for review http://lists.openembedded.org/pipermail/openembedded-core/2017-January/131636.html
V2 of the patch sent to the list http://lists.openembedded.org/pipermail/openembedded-core/2017-March/133982.html
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
Merged in oe-core 0fa3d331df7d5a5fbd8431febc75efe6bcc6f96b.