9390 2016-04-05 03:23:24 +0000 oeqa: don't write anything to local.conf or bblayers.conf 2016-09-23 14:43:17 +0000 1 1 7 Build System, Metadata & Runtime OE-Core core 2.2 x86 Multiple RESOLVED FIXED Medium enhancement 2.3 M1 9389 1 liezhi.yang jose.a.lamego bluelightning leonardo.sandoval.gonzalez meta.mr.watcher meta.watcher --- --- No (bug/feature does not impact docs) oldest_to_newest 60777 0 liezhi.yang 2016-04-05 03:23:24 +0000 So that when the running is aborted by control-C, it won't affect the next run. We can use bitbake -R and -r to do this. 60911 1 richard.purdie 2016-04-07 14:44:10 +0000 This implies that the seltest code would never need to cleanup and that isn't the case. We need to make sure the cleanup code runs correctly even in the Ctrl+C case. 61820 2 bluelightning 2016-04-29 04:11:50 +0000 Right, some of the tests actually need to test adding items to configuration files as the user would, so I don't think this is going to be practical for all of oe-selftest. Besides, configuration is only part of the picture - e.g. files left around in the sysroot or the metadata could also cause problems for future runs. As Richard says it's about ensuring the cleanup runs even when interrupted with Ctrl+C. Something related to (but not the same as) this is covered under bug 8105. 66433 3 jose.a.lamego 2016-09-21 19:11:26 +0000 Fix submitted for review: https://patchwork.openembedded.org/patch/132083/ 66549 4 jose.a.lamego 2016-09-23 14:34:38 +0000 Fix merged in commit 0877278e07e4c2494c4c23199490dc47a5cee69d 66550 5 jose.a.lamego 2016-09-23 14:43:17 +0000 Edit, commit: c902e7b93700e56245d8f04397ff01fa278183a3