Comment 2 for bug 1250553

This one might actually be quite easy to fix, although in a slightly different way. Most tests don't care, but as it turned out I already have one test which has three candidate paths, but only two leave you at the highest version.

Without significant (and not worth it) refactoring, I can't actually filter out the paths that don't leave you at the maximum build, but I can instead assign those candidates a ridiculously high score making it highly unlikely those paths would get chosen.