Double merge and failed runs with a CPI MP
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ols-jenkaas |
Fix Released
|
High
|
Unassigned |
Bug Description
This seems to be the run where it got first merged (before the last commit got in):
https:/
I'm sure I didn't top-approve the MP, but maybe someone else? So I never noticed this was merged until I pushed my last changes (suggestions from the review) and then top-approved.
Successive runs (including the changes from the last commit) were failing until Daniel moved it back to Needs Review, voted and re-top-approved. Then the MP got merged, again:
https:/
[1] https:/
Changed in ols-jenkaas: | |
status: | New → Confirmed |
importance: | Undecided → High |
https:/ /jenkins. ols.canonical. com/online- services/ job/click- package- index/47/ console mentions:
16:29:26 E: Merging https:/ /code.launchpad .net/~matiasb/ click-package- index/check- for-device- refresh at revision <email address hidden>
https:/ /jenkins. ols.canonical. com/online- services/ job/click- package- index/77/ console
18:19:35 E: Merging https:/ /code.launchpad .net/~matiasb/ click-package- index/check- for-device- refresh at revision <email address hidden>
Setting the status to Approve on a launchpad merge proposal sets the reviewed_revid proposal attribute.
The value is pre-loaded in the page with that last revision presented there.
So the scenario is: load the MP page at revision N, push N+1, top approve (approving and triggering landing N).