The ConfigParsed event is raised multiple times during a build which resulted
in the sanity warning appearing up to 4 times per build. Instead we should be
watching for the SanityCheck event (this is what the sanity checks in oe-core
watch for).
Signed-off-by: Paul Barker <pbar...@toganlabs.com>
---
classes/sanity-meta-virt.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/classes/sanity-meta-virt.bbclass b/classes/sanity-meta-virt.bbclass
index 417ab6f..b4ed082 100644
--- a/classes/sanity-meta-virt.bbclass
+++ b/classes/sanity-meta-virt.bbclass
@@ -1,5 +1,5 @@
addhandler virt_bbappend_distrocheck
-virt_bbappend_distrocheck[eventmask] = "bb.event.ConfigParsed"
+virt_bbappend_distrocheck[eventmask] = "bb.event.SanityCheck"
python virt_bbappend_distrocheck() {
skip_check = e.data.getVar('SKIP_META_VIRT_SANITY_CHECK') == "1"
if 'virtualization' not in e.data.getVar('DISTRO_FEATURES').split() and
not skip_check:
--
2.7.4
--
_______________________________________________
meta-virtualization mailing list
meta-virtualization@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-virtualization
