Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • M meta-virtualization
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Terraform modules
    • Model experiments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • automation
  • so
  • mirror
  • meta-virtualization
  • Repository
  • meta-virtualization
  • classes
  • sanity-meta-virt.bbclass
Find file Blame History Permalink
  • Paul Barker's avatar
    sanity-meta-virt: Watch for SanityCheck event · 638ba962
    Paul Barker authored Oct 12, 2017
    
    
    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: default avatarPaul Barker <pbarker@toganlabs.com>
    Signed-off-by: default avatarBruce Ashfield <bruce.ashfield@windriver.com>
    638ba962