Using the same branch to fix different bugs confuses the tagger

[Diogo Matsubara]

In an attempt to fix bug 674829, I found out the deployment-db-stable.html report is blocking on the wrong revision. The root cause is that commit.fixed_bugtasks gets its bugtasks from, among other places, bugs linked to the branch.

So in this specific case, the branch used to fix bug 54009 was https://code.launchpad.net/~stub/launchpad/pending-db-changes, r9977

Afterwards the same branch was used to fix bug 368600 and bug 678289, r9997

Later on the same branch was used to fix bug 684672

So, the end result was that those 3 bugs were linked to the pending-db-changes branch and when the tagger tried to build its fixed_bugtasks set, it thought those 3 bugs belonged to r9977.

I unlinked those bugs from the pending-db-changes branch in an attempt to make the report happy. A copy of the broken report can be found here: https://devpad.canonical.com/~matsubara/deployment-db-stable.html

There might be a bug for this but I couldn't find one. The closest one is bug 640566 but that one only deals with fix released bugs.

[Robert Collins (lifeless)]

I think this is a dupe, not sure of the number though.

[Ursula Junque (ursinha)]

This is a dupe of an already fixed bug, bug 640566. This behavior Diogo described doesn't happen anymore as we don't consider Fix Released bugs. If a Fix Released bug is mentioned in a commit message or the branch has Fix Released bugs linked to it, qa-tagger will ignore them for QA purposes. If this problem happened, it was because one of the "wrong" linked bugs aren't properly marked as Fix Released.

Please, let me know if this happens again. Thanks!