Launchpad itself

no-change MPs not marked as Merged?

Asked by Marcus Tomlinson on 2016-06-17

Curious: Are no-change-rebuild MPs supposed to get marked as "Merged" when they land via a silo?

E.g.
    https://code.launchpad.net/~thomas-voss/platform-api/no-change-rebuild/+merge/296017 &
    https://code.launchpad.net/~marcustomlinson/unity-scopes-shell/no-change-rebuild/+merge/296019

These landed in https://requests.ci-train.ubuntu.com/#/ticket/1451, but are not marked as such on Launchpad. Is this because there are no commits in the branch?

Thanks!

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Solved by:
Marcus Tomlinson
Solved:
2016-06-25
Last query:
2016-06-25
Last reply:
2016-06-18
William Grant (wgrant) said : #1

That's a very weird MP, because there were no new revisions. It's impossible to merge no revisions, so I assume the CI Train must detect those MPs and manually create a no-change rebuild revision. Since it's not actually merging the MP, Launchpad can't close it -- CI Train needs to close it itself.

Robert Bruce Park (robru) said : #2

Nope, train does not detect this at all, it merges it like any other MP. Bzr reports." nothing to do" and then commits it anyway.

Marcus Tomlinson (marcustomlinson) said : #3

Assigned a bug to the Bileto project (linked).