Closed Bug 1289406 Opened 8 years ago Closed 8 years ago

Autoclassification does not classify results

Categories

(Tree Management :: Treeherder, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: cbook, Assigned: jgraham)

References

Details

Attachments

(1 file)

Workflow before:

Marking a failure to a bug -> Failure got classified and associated to a bug 

now with bug 1288320 

Marking a failure to a bug in the auto classification panel and click on save all result in either
-> Treeherder tells me it classified the failure but it doesn't mark as such - also the message that the classification is associated to a bug is missing, so i have to go back to the failure summary and classify the job again (kind of double work)

and also in more then 50 % of the cases i get :
https://treeherder.mozilla.org/api/failure-line/5311223/ 
<h1>Server Error (500)</h1>

or on https://treeherder.mozilla.org/api/failure-line/
Depends on: 1289354
Blocks: 1288230
Attachment #8775802 - Flags: review?(emorley)
Attachment #8775802 - Flags: review?(emorley) → review+
Commits pushed to master at https://github.com/mozilla/treeherder

https://github.com/mozilla/treeherder/commit/f5e5961d394c74ceefa7253078bfcfe9451aaf70
Bug 1289406 - Avoid trying to create multiple classifications with the same bug number

https://github.com/mozilla/treeherder/commit/d19b219ea765a70df52348340299e909c62812ca
Bug 1289406 - Don't count classified failures as missing when they have been merged and the client sends the old id.

https://github.com/mozilla/treeherder/commit/1206e02cb8e51ff1ef365a220e3f3fcbd295bae2
Merge pull request #1749 from mozilla/classification_dupe

Bug 1289406 - Handle multiple classifications with the same bug id better.
Assignee: nobody → james
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: