Sort build completed messages with worst results first

So the attention is drawn on the worst results.  Otherwise users
may e.g. miss an UNSTABLE result because they see SUCCESS first.
Why this change?

It was a long time ago, but I think the 32 was explicit to make sure that the code review value was actually calculated and not the default int.