approved revision no longer in the source branch happens very often with this repo
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
High
|
Unassigned |
Bug Description
Hey folks,
The canonical-
https:/
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-
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/
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.
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.