These are release builds on another branch/waterfall.  If you look at the build with 56 you'll see the builder name and waterfall indicate that.

When I originally built things I didn't have a good enough mental model and built things assuming build_config + build number uniquely identify a build.  I think if we change it to waterfall/build_config/build_number, while still not guaranteed to be unique (buildbot_generation could technically change and roll things over), it would be sufficient to address these issues.

+jinjingl who might need to deal with this for GoldenEye as well.

Thank you for the clarification, David.

If it's the same kind of build, just a different branch, maybe it's fine to leave it in the mix?  I don't suppose that the branch is likely to diverge much from ToT in terms of build time.

I am almost tempted to call this a WontFix, but I'll leave it to you.

Fix posted at cl/146135697.

If a waterfall or milestone version are specified, those filters will be applied.  Waterfall will default to 'chromeos' unless milestone version is specified.  

The most recent builds will apply the same logic, except instead of default to chromeos, it will default to the waterfall of the build being displayed.


Re: c#3 I've cleaned it up to try and remove the confusion.  I think there's still some edge cases that might not be handled 100% correctly, but it's also not clear what the absolute correct behaviour is, so I think I'm okay with leaving those edge cases unhandled for now.