I think this is just a bug in the current implementation of how we figure out what shipped where :(

We've known for a while that the current algorithm for polling / storing version details has occasionally missed CLs, generally for higher order channels eg dev / beta / stable (canary is pretty solid) - sadly it looks like 2-3 of your CLs have been busted, which might mean our miss rate is higher than anticipated.

We are currently building a new backend with known bugs addressed - it will be a month or two before it's deployed though, since it required re-architecting a fair chunk of code.  Can you please let us know if you see more instances of this issue though, so we can better understand current miss rate?

Sorry about the hassle in the interim.  +cc prasadv@ as FYI, I think we def need to implement some monitoring of how much this occurs in the new implementation to make sure all issues are ironed out prior to public launch.

Sure, I'll post updates here if I notice anything similar come up again.

Just noticed today that the changes which hadn't been showing the merge branches before are now correctly displaying them.  I'm not sure if there was some other change to fix this, but you can probably close this out if it's expected to be working.

Hmm, we didn't change anything I know of and I think it's a bad experience for things to have been missing for so long.  I'm kind of using this as a meta-bug for auditing our data services at some point so if you're OK with us keeping it open for a bit longer it'd be appreciated.

We spent a *lot* of time reviewing our implementation and made a substantial number of fixes.  We also launched our staging instance to production.  Thus, you should no longer see any issues here: https://chromiumdash.appspot.com/

Please let us know if you do see any more missing commits though.  Thanks for using Chromium Dash!