1308669 - Find a way to make philor file fewer bugfiler bugs in the wrong component

Status: RESOLVED FIXED

(Tree Management :: Treeherder, defect)

Description

[Phil Ringnalda (:philor)]

The only idea I've got so far is to weight the matching results by a per-component count of open intermittent bugs that we could produce while fetching for the bugscache, since that would put Testing::web-platform-tests with a billion open bugs above Infrastructure & Operations::WebOps: Community Platform, and the devtools debugger above the Tamarin one, and Core::JavaScript Engine above Developer Documentation::JavaScript.

Comment 1

[GitHub Autolander Bot]

Attachment: [treeherder] KWierso:bug1308669 > mozilla:master

Comment 2

[Wes Kocher (:KWierso) (Not reading bugmail; email directly if needed)]

Comment on attachment 8799099 [details] [review]
[treeherder] KWierso:bug1308669 > mozilla:master

This PR makes sure the web-platform-tests component is always suggested for failing wpt jobs.

Additionally, there were instances where the initial search for a decent product/component were attempting to use "TEST-UNEXPECTED-foo" as the root of the failure path. This patch also makes an attempt to use the actual file path for the initial search if that's the case.

Comment 3

[Phil Ringnalda (:philor)]

Comment on attachment 8799099 [details] [review]
[treeherder] KWierso:bug1308669 > mozilla:master

An amusing solution, given that we're in theory supposed to somehow file wpt failures against the code they test.

Comment 4

[Treeherder GitHub Bugbot]

Commit pushed to master at https://github.com/mozilla/treeherder

https://github.com/mozilla/treeherder/commit/4acd66b06f8d634df78f731b59bd1aa03906db79
Bug 1308669 - Make sure web-platform-tests is suggested for wpt jobs (#1909) r=wlach

This just makes sure that when the selected failing job is a wpt test, the
Testing :: web-platform-tests product/component pair is offerred as a
suggestion.

This also helps make sure we don't try to use "TEST-UNEXPECTED-foo" as a
potential path root for the initial product searches, because that makes
the feature fail to find anything if the "TEST-UNEXPECTED-foo" isn't
omitted.