[bitbake-devel] setscene fetch failures are fatal

Joshua Watt jpewhacker at gmail.com
Fri Jun 28 22:23:23 UTC 2019


I'm having an issue with the _setscene tasks failing to fetch causing
our builds to fail. For example: we see the following in our CI build
logs:

 WARNING: flac-1.3.1-r0 do_package_write_ipk_setscene: Failed to fetch
URL file://07/sstate:flac:cortexa15hf-neon-poky-linux-gnueabi:1.3.1:r0:cortexa15hf-neon:3:07fe4a22caf5e326a98e397f7923060a_package_write_ipk.tgz.siginfo;downloadfilename=07/sstate:flac:cortexa15hf-neon-poky-linux-gnueabi:1.3.1:r0:cortexa15hf-neon:3:07fe4a22caf5e326a98e397f7923060a_package_write_ipk.tgz.siginfo,
attempting MIRRORS if available
 ERROR: flac-1.3.1-r0 do_package_write_ipk_setscene: Fetcher failure:
Unable to find file
file://07/sstate:flac:cortexa15hf-neon-poky-linux-gnueabi:1.3.1:r0:cortexa15hf-neon:3:07fe4a22caf5e326a98e397f7923060a_package_write_ipk.tgz.siginfo;downloadfilename=07/sstate:flac:cortexa15hf-neon-poky-linux-gnueabi:1.3.1:r0:cortexa15hf-neon:3:07fe4a22caf5e326a98e397f7923060a_package_write_ipk.tgz.siginfo
anywhere. The paths that were searched were:
  /tmp/tmp.S3vCIuI7SE/sstate

The build carries on as normal and even builds everything
successfully, but the final error code returned from bitbake is '1'.
This is particularly annoying because A) this happens a lot and B) the
build did actually produce usable outputs so failing isn't really
accurate.

Near as I can tell, this is caused because the knotty UI treats any
logging.error() message as fatal and will have a non-zero return code
if one occurs.

I also realize this is probably mostly caused by an infrastructure
problem on our end, but I don't seem to be able to get anyone to
magically make that better so that this failure stops happening :(

Does anyone have any ideas for things that could be done to mitigate
this? So far, the only thing I've come up with is to modify the
bitbake Fetch.download() so that an argument can be passed that says
whether to use logger.error() or logger.warning() when reporting an
error, but that feels really ugly.

Thanks,
Joshua Watt


More information about the bitbake-devel mailing list