build system: disgraceful fail when no space
When (re-)building rootfs with low space (<1Gb), the build throws an error:
ERROR: No new tasks can be executed since the disk space monitor action is "STOPTASKS"!
and does not crate image. However, the build system continues to the next step in which it fails because no image is created. The problem is that the error is thrown in a wrong stage of the build... and it's tricky to find out what's wrong.