| Summary: | oe-selftest devtool tests fails when repository comes from a tarball | ||
|---|---|---|---|
| Product: | [QA/Testing] Runtime Testing | Reporter: | Leonardo Sandoval Gonzalez <leonardo.sandoval.gonzalez> |
| Component: | general | Assignee: | Thomas Roos <thomas> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | bluelightning, randy.macleod, rebecca.swee.fun.chang, richard.purdie, thomas |
| Version: | 2.4 | ||
| Target Milestone: | 5.99 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | NEWCOMER | ||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Leonardo Sandoval Gonzalez
2017-11-29 21:04:07 UTC
In general, the whole suite must be exercised (oe-selftest -a) based on release tarball and see if other areas are affected. We should probably just skip the tests in this case if the tree isn't a git repo (or just error out upfront and refuse to run the tests at all if too many are affected). What about making it a git before starting tests? -> git init? Is there any possibility to skip a whole class of tests?
At test level skipping would be possible by something like this:
try:
runCmd("git rev-parse --is-inside-work-tree")
except:
self.skipTest("Devtool tests require folder to be a git repo")
In general those are the numbers for oe-selftest -a 2023-04-22 01:42:10,561 - oe-selftest - INFO - oe-selftest () - Ran 530 tests in 49170.163s 2023-04-22 01:42:10,561 - oe-selftest - INFO - oe-selftest - FAIL - Required tests failed (successes=472, skipped=10, failures=19, errors=33) -> so we could skip to whole devtool class and then also skip others. Thanks for sorting the patch out for this! Bulk move from 4.99 or 0.00 to 5.99 |