1473494 - treeherder carries the classification of a previous bug, on to the next failure to be classified

Status: RESOLVED WORKSFORME

(Tree Management :: Treeherder, defect, P1)

Description

[Andreea Pavel [:apavel]]

When classifying failures, there are situations where 2 bugs are added - 1 related to the failure and one completely unrelated. 
This seems to occur in different scenarios, one of which is when you look at a failure and click on the bug suggestion for Bugzilla to open that bug but one does not pin it and passes on to the next failure.
When you try to classify the current failure, the bug suggestion from the previous one is already in the "add a related bug" area. 

Aryx: Seems like the latter one gets carried over from the classification of a different bug.

Please ni? me if you need additional info.

Comment 1

[Cameron Dawson [:camd]]

I'm not able to reproduce this bug.  Here's the steps I'm using:

1. Click a failure
2. Click the bug link (not the pin button) for one of the bugs
-- Opens that bug in bugzilla in a new tab
3. Close bugzilla tab
4. Hit 'n' to go to next failure
5. Click the pin button next to a bug
-- See only that new job and the new bug in the "add a related bug" area.  Do not see the bug number for the previous job.

Andrea-- Would you provide specific STR?  Thanks!  :)

Comment 2

[Andreea Pavel [:apavel]]

Hi:
1. selected https://treeherder.mozilla.org/#/jobs?repo=mozilla-inbound&filter-resultStatus=testfailed&filter-resultStatus=busted&filter-resultStatus=exception&filter-classifiedState=unclassified&fromchange=047484a0a18ae2e73300aeb4c00936e6d7ef8f8d&selectedJob=187007926 to ask aryx about it
3.aryx gave me this bug on irc Bug 1459775
-- opened the bug in bugzilla in a new tab
2. switched to the tab with the failure https://treeherder.mozilla.org/#/jobs?repo=mozilla-inbound&filter-resultStatus=testfailed&filter-resultStatus=busted&filter-resultStatus=exception&filter-classifiedState=unclassified&fromchange=047484a0a18ae2e73300aeb4c00936e6d7ef8f8d&selectedJob=187007926  - noticed it already had a bug typed in the "add related bug" area, bug 1440059 (which i did not open/see today before)

(the failure from the above link was selected, but not pinned to anything)

This is only one case with exact STR. I'll update this bug along the way. 
Thanks.

Comment 3

[Cameron Dawson [:camd]]

Talked to Andrea on IRC and she's no longer experiencing this.