Created attachment 5106 [details] screenshots of the described misbehavior for rust-llvm-native recipe if the "do_populate_sysroot_setscene" task fails in Fetcher action, e.g. because the sstate archive is not available, it will run the full task instead. but: even if running the full task succeeds, the whole build (e.g. image recipe), in which this recipe was included, will report failure - because the Fetcher-failure for that sstate archive has ERROR severity! suggested fix: change Fetcher log-severity to Warning or even Info here. see attachements for rust-llvm-native: this failed installation from sstate cache, but its rebuild succeeded - nevertheless the parent image recipe failed...
actually this bug was seen in poky DISTRO_VERSION "5.0.1" -- but this I cannot select in the dropdown list :-/
The question would be why the sstate task thought the sstate was obtainable, then when it tried, it couldn't. We do consider this an error situation since it seems as if there was some kind of network failure during the build. This only happens if the initial "does sstate exist?" test passes but then fails later in the build.
ok, understood - yeah could have been some temp. network issue. but - since you consider this an error situation: why even trying to recover from that by building from sources, if you anyhow fail the whole build later on? you already could stopp the build here!
This behaviour is expected but it does need documentation in the FAQ section.