Bug 9390

Summary: oeqa: don't write anything to local.conf or bblayers.conf
Product: [Build System, Metadata & Runtime] OE-Core Reporter: Robert Yang <liezhi.yang>
Component: coreAssignee: Jose Lamego <jose.a.lamego>
Status: RESOLVED FIXED QA Contact:
Severity: enhancement    
Priority: Medium CC: bluelightning, leonardo.sandoval.gonzalez, meta.mr.watcher, meta.watcher
Version: 2.2   
Target Milestone: 2.3 M1   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)
Bug Depends on:    
Bug Blocks: 9389    

Description Robert Yang 2016-04-05 03:23:24 UTC
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.
Comment 1 Richard Purdie 2016-04-07 14:44:10 UTC
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.
Comment 2 Paul Eggleton 2016-04-29 04:11:50 UTC
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.
Comment 3 Jose Lamego 2016-09-21 19:11:26 UTC
Fix submitted for review: https://patchwork.openembedded.org/patch/132083/
Comment 4 Jose Lamego 2016-09-23 14:34:38 UTC
Fix merged in commit 0877278e07e4c2494c4c23199490dc47a5cee69d
Comment 5 Jose Lamego 2016-09-23 14:43:17 UTC
Edit, commit: c902e7b93700e56245d8f04397ff01fa278183a3