The artifacts created are quite large and keeping multiple of them will consume a notable amount of disk space while the expected speed-up is minimal.
(For the same reasons, the image class does not generate SSTATE artifacts).
Having SSTATE artifacts for bundles enabled can also lead to unexpected/unwanted behavior if a rootfs image recipe was rebuild and the binary output (file system image) changed but did not make it into the final bundle.
This becomes a major problem, e.g. in the context of verified boot.
The artifacts created are quite large and keeping multiple of them will consume a notable amount of disk space while the expected speed-up is minimal. (For the same reasons, the image class does not generate SSTATE artifacts).
Having SSTATE artifacts for bundles enabled can also lead to unexpected/unwanted behavior if a rootfs image recipe was rebuild and the binary output (file system image) changed but did not make it into the final bundle. This becomes a major problem, e.g. in the context of verified boot.