It is important to test with real MACHINE values, otherwise changes
introduced by layers only when their machines are selected wouldn't
show up. The new test_machine_signatures and test_machine_world tests
cover two aspects of that (signature differences and world build
failures).
V2: - use self.fail() instead of self.assertTrue(False, ...)
- test_machine_signatures check (work in progress)
V3: - rebased onto master where some yocto-compat-layer enhancements were
already merged
- added OE-core fixes for issues found by the per-machine signature
comparison
- finished test_machine_signatures (shorter output, explanations
on how to run bitbake-diffsigs, end report with one bitbake-diffsigs
invocation)
- allow "bitbake -S none world" to fail during test_machine_signatures,
report such failures in a separate test_machine_world
V4: - avoid DEPENDS_remove for go-cross
- commit message spelling fixes
V5: - rebased after preceeding patches were merged
- generate task list dynamically based on depgraph instead of hard-coding it
Patrick Ohly (2):
yocto-compat-layer: test signature differences when setting MACHINE
yocto-compat-layer: better handling of per-machine world build breakage
scripts/lib/compatlayer/__init__.py | 23 +++-
scripts/lib/compatlayer/cases/bsp.py | 180 +++++++++++++++++++++++++++-
scripts/yocto-compat-layer.py | 3 +-
3 files changed, 201 insertions(+), 5 deletions(-)
base-commit: e41c90b852167bbcb434da57b84280e855acae33
--
git-series 0.9.1
--
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
