In some cases, it can take quite a while for rebuilding a package. To the normal user, this might look like the machine is stuck. But even running ps/top in a separate window doesn't give any idea about how long it will take. It would be useful to have statistics (for example embedded in the SSTATE content) that would support the execution of: bitbake -c show-stats recipe Then one would know how long it took to perform a task, on the machine that populated the SSTATE, and weigh the decision of rebuilding some or all of it.
This probably ties in with the work I have done for bug 5383 (which went significantly further than the original request; I've attempted to produce a general solution that would work for any task).
Yes, it looks like it could go under that umbrella. If you prefer to consolidate them, feel free to add this proposal to 5383 and mark this as duplicate.
Marking as duplicate as agreed. *** This bug has been marked as a duplicate of bug 5383 ***