<div dir="ltr">There are patches for this on the ML from long time ago. They were rejected that it's just hiding the real infrastructure issue which should be fixed, but I keep them in my builds as well because as you say, errors like this triggering the CI build failures of unrelated changes is quite annoying.<div><br></div><div><a href="https://github.com/shr-distribution/bitbake/commit/75858b7f4f03137646cb934b8e3cde0807493eed">https://github.com/shr-distribution/bitbake/commit/75858b7f4f03137646cb934b8e3cde0807493eed</a><br></div><div>+</div><div><a href="http://git.openembedded.org/openembedded-core-contrib/commit/?h=jansa/master&id=dec7674a1cb501ee8e4f864dcb4adc307c10c159">http://git.openembedded.org/openembedded-core-contrib/commit/?h=jansa/master&id=dec7674a1cb501ee8e4f864dcb4adc307c10c159</a><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Jun 29, 2019 at 12:23 AM Joshua Watt <<a href="mailto:jpewhacker@gmail.com">jpewhacker@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">I'm having an issue with the _setscene tasks failing to fetch causing<br>
our builds to fail. For example: we see the following in our CI build<br>
logs:<br>
<br>
WARNING: flac-1.3.1-r0 do_package_write_ipk_setscene: Failed to fetch<br>
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,<br>
attempting MIRRORS if available<br>
ERROR: flac-1.3.1-r0 do_package_write_ipk_setscene: Fetcher failure:<br>
Unable to find file<br>
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<br>
anywhere. The paths that were searched were:<br>
/tmp/tmp.S3vCIuI7SE/sstate<br>
<br>
The build carries on as normal and even builds everything<br>
successfully, but the final error code returned from bitbake is '1'.<br>
This is particularly annoying because A) this happens a lot and B) the<br>
build did actually produce usable outputs so failing isn't really<br>
accurate.<br>
<br>
Near as I can tell, this is caused because the knotty UI treats any<br>
logging.error() message as fatal and will have a non-zero return code<br>
if one occurs.<br>
<br>
I also realize this is probably mostly caused by an infrastructure<br>
problem on our end, but I don't seem to be able to get anyone to<br>
magically make that better so that this failure stops happening :(<br>
<br>
Does anyone have any ideas for things that could be done to mitigate<br>
this? So far, the only thing I've come up with is to modify the<br>
bitbake Fetch.download() so that an argument can be passed that says<br>
whether to use logger.error() or logger.warning() when reporting an<br>
error, but that feels really ugly.<br>
<br>
Thanks,<br>
Joshua Watt<br>
-- <br>
_______________________________________________<br>
bitbake-devel mailing list<br>
<a href="mailto:bitbake-devel@lists.openembedded.org" target="_blank">bitbake-devel@lists.openembedded.org</a><br>
<a href="http://lists.openembedded.org/mailman/listinfo/bitbake-devel" rel="noreferrer" target="_blank">http://lists.openembedded.org/mailman/listinfo/bitbake-devel</a><br>
</blockquote></div>