WIP: Build failure debug tips
One thing we can do to help the end user when confronting them with a build failure is making a sort-of-educated guess about what modules should likely be tackled first. This is a first stab at doing so by printing a top 5 modules that look the 'most interesting'.
There is a few heuristics/assumptions about what constitutes interesting. There is room for improvement here, and also unit tests.
Edited by Johan Ouwerkerk