Hi Richard, That makes sense if SRCREV is completely missing the recipe is unbuildable anyway, so the parse failure is an acceptable outcome for that case.
So the complete solution would be: - BB_NO_NETWORK:layer-core = "1" in OE-core to prevent floating branch/tag lookups - A QA check in insane.bbclass to warn about missing SRCREV for external layers - yocto-check-layer catches parse failures during validation Is this the right direction? Best regards, Sai Sneha On Tue, 9 Jun 2026 at 5:11 PM, Richard Purdie < [email protected]> wrote: > On Tue, 2026-06-09 at 16:04 +0530, Sai Sneha wrote: > > Hi Richard, > > > > Please correct me if am wrong. > > BB_NO_NETWORK:layer-core = "1" > > would work for the case where SRCREV is set to a floating > > branch or tag, since _lsremote() calls check_network_access() > > which raises NetworkAccess when BB_NO_NETWORK is set. > > > > However for the case where SRCREV is completely missing the > > crash happens earlier in srcrev_internal_helper() which raises > > FetchError before latest_revision() is even called so > > BB_NO_NETWORK wouldn’t catch that case. > > In that case the build fails to parse and is unbuildable? That is > probably fine as check-layer tests whether it parses? > > Cheers, > > Richard >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#238312): https://lists.openembedded.org/g/openembedded-core/message/238312 Mute This Topic: https://lists.openembedded.org/mt/119719972/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
