1179308 - Determine workflows impacted by disabling classification bug comments

Status: RESOLVED FIXED

(Tree Management :: Treeherder, defect, P2)

Description

[Ed Morley [:emorley]]

As part of bug 1179263 (and mentioned in the intermittent failure talk at Whistler), we'd like to turn off the bug comments made on intermittent failure bugs for every classification submission in Treeherder - to reduce spam and the impact on the BMO database.

I've proposed doing this in the past, but met resistance:
https://groups.google.com/forum/#!topic/mozilla.dev.planning/VCSGfBj-VXQ/discussion

Whilst long term we want to create an OrangeFactor v2 that uses Treeherder's DB (vs ElasticSearch) and has much more functionality, the BMO team would rather us turn off bug comments in a much shorter timeframe.

As such, we should find out what the minimal set of features/changes that are required, so we can turn off the bug comments.

My hunch is:
* Make a few small changes to the OrangeFactor UI to surface info currently only available in the bug comments
* Come up with a way to notify people as to the relative frequency of each bug, so they can prioritise their work. (Whilst this is available on OrangeFactor, people have to remember to check it - so some script that emails people or comments on the top bugs once per day/week would be great).

However we should email the newsgroups to find out; which I will do shortly.

Comment 1

[Phil Ringnalda (:philor)]

* Make OF actually cover everything rather than the limited set of things it wants to cover.

Compare https://bugzilla.mozilla.org/show_bug.cgi?id=1165469 and https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1165469

Comment 2

[Ed Morley [:emorley]]

Thank you, I was not aware of that issue (there doesn't seem to be a bug on file); will investigate in bug 1179316.

Comment 3

[Ed Morley [:emorley]]

Holding off on emailing the newsgroups until some of the more obvious OF issues are fixed:
https://bugzilla.mozilla.org/showdependencytree.cgi?id=1179310&hide_resolved=0

Comment 4

[Phil Ringnalda (:philor)]

This round will be "keep on filing bugs, and just don't comment in them while starring," right? One use case that you'll wontfix, impacted by that: I don't bother with a comment 0 while filing anymore since the starring comment from c1 is good enough, and one for the eventual "no bugs until it gets horrible" round, that just occurred to me - we have handfuls of honeypot bugs like "Only broken slaves running at a too-small resolution hit ___" and "You only need to clobber the OS X opt build when you hit ___" which would require the ability to manually edit whatever thing will replace bug suggestions.

Comment 5

[Ed Morley [:emorley]]

Yeah agreed the workflow of being able to omit comment 0 when creating a new intermittent failure bug won't work - the best fix for that is bug 1117583.

The rest is orthogonal, but yeah we can have a way to flag certain issues as not being closed/ignored due to time since last occurrence.