Looking at any autobuilder log (e.g. https://autobuilder.yoctoproject.org/main/builders/nightly-arm/builds/303/steps/BuildImages/logs/stdio) we see: NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "1.27.0" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "CentOS-6.6" TARGET_SYS = "arm-poky-linux-gnueabi" MACHINE = "qemuarm" DISTRO = "poky" DISTRO_VERSION = "1.8+snapshot-20150515" TUNE_FEATURES = "arm armv5 thumb dsp" TARGET_FPU = "soft" meta meta-yocto meta-yocto-bsp = "master-next:3cca4fa0d9541d87d8f53c2544bfbef171caa20b" meta-qt3 = "master:3016129d90b7ac8517a5227d819f10ad417b5b45" Failure expanding variable SRCPV, expression was ${@bb.fetch2.get_srcrev(d)} which triggered exception FetchError: Fetcher failure: SRCREV was used yet no valid SCM was found in SRC_URI NOTE: Preparing RunQueue Note the FetchError. This only occurs when the -w option is passed to bitbake (and this occurs locally too). We need to find a way to remove this error message.
http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=8b5ee367a630027d478aed265ee79a7230e91673
Verified on master: da13f0bce5d1b3c52f5716ae8d104372a820e5f9 Steps: 1. $ git checkout 947e5260f9f3a68e51ccc456610bad9a8b200224 2. $ bitbake ed -w WRITEEVENTLOG Failure expanding variable SRCPV, expression was ${@bb.fetch2.get_srcrev(d)} which triggered exception FetchError: Fetcher failure: SRCREV was used yet no valid SCM was found in SRC_URI 3. $ git checkout master 4. $ bitbake ed -w WRITEEVENTLOG --> build successfully