| Summary: | oe-selftest: error output shown with --coverage when coverage module not installed | ||
|---|---|---|---|
| Product: | [QA/Testing] Build Testing | Reporter: | Humberto Ibarra <humberto.ibarra.lopez> |
| Component: | general | Assignee: | Humberto Ibarra <humberto.ibarra.lopez> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | minor | ||
| Priority: | Medium | CC: | richard.purdie |
| Version: | 2.1 | ||
| Target Milestone: | 2.1 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Humberto Ibarra
2016-03-23 16:07:48 UTC
The thing which worries me more is that the system doesn't stop after the failure or set an error exit code? The script doesn't stop after the coverage module isn't found because the script is not trying to find the coverage module. A different file is trying to do the import. The coverage module is imported by a temporary file saved under the user site directory. Python tries to import it every time it runs. The problem is that oe-selftest creates this file when given the --coverage option, even if coverage is not installed. Sent patches http://lists.openembedded.org/pipermail/openembedded-core/2016-April/119900.html http://lists.openembedded.org/pipermail/openembedded-core/2016-April/119901.html http://lists.openembedded.org/pipermail/openembedded-core/2016-April/119902.html http://lists.openembedded.org/pipermail/openembedded-core/2016-April/119903.html |