approved revision no longer in the source branch happens very often with this repo

[Daniel Manrique]

Hey folks,

The canonical-mojo-specs branch is ending up in the above-mentioned situation very frequently. Latest example is:

https://code.launchpad.net/~roadmr/canonical-mojo-specs/sca-up-deploy-timeout/+merge/388573

1- Pushed and mentioned at 9:51 AM
2- Guillermo community-approved around 9:54 AM
3- Gareth top-approved at 10:03 AM

(so I think it should have been enough for any scans or async operations to complete). Yet once it was top-approved, the merge bot got confused:

Canonical IS Mergebot (canonical-is-mergebot) wrote 3 minutes ago: #

Merge proposal is approved, but source revision has changed, setting status to needs review.

The same thing happened last week at least 3 times early in the week (deej was around for those). Interestingly, last Friday the merge worked well, so maybe it's related to some weekend maintenance/failures?

One other thing I noticed last week is that after Dave merged the changes manually, I got the "branch is merged" email from Launchpad like a day after the fact.

[Tom Wardill (twom)]

If this was git, I'd suggest that something is force pushing the trunk branch. But it's not, so this will need some investigation from someone that understands bzr.