Closed Bug 1757660 Opened 3 years ago Closed 3 years ago

when filing a new bug use meta tracking bug instead of raw error message

Categories

(Tree Management :: Treeherder: Frontend, task)

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jmaher, Unassigned)

References

(Blocks 1 open bug)

Details

As we are switching to a single bug per test case, we will need to file new bugs in the new format.

Specifically the summary should be: Intermittent <path> | single tracking bug and we should have keywords: intermittent-failure and whiteboard with [intermittent-testcase]

This will only be for tests that match some criteria:

  • has a test path
  • no CRASH
  • no TIMEOUT
  • in list of tasks we support SIMPLE_BUG_TASKS

SIMPLE_BUG_TASKS = ['xpcshell'] # if any words in array match task, use simple bug format.

we will need to hard code SIMPLE_BUG_TASKS within treeherder for now.

treeherder code for bugfiler:
https://github.com/mozilla/treeherder/blob/40de4922ad884e749ed57bd41e106231ce806b7e/ui/shared/BugFiler.jsx

this is most likely called from:
https://github.com/mozilla/treeherder/blob/40de4922ad884e749ed57bd41e106231ce806b7e/ui/shared/tabs/failureSummary/FailureSummaryTab.jsx#L44

I would prefer to hack as few files as possible, so given that we are hacking FailureSummaryTab.jsx in bug 1757222, if we could do the same here it would be nice. Possibly we could hack the suggestion that we pass into BugFiler so that it has what we need if the conditions are met.

we discussed adding a second keyword intermittent-testcase, I would need to get that added, or use a whiteboard tag. :aryx, would a whiteboard tag work, or should I formally add the new keyword.

Flags: needinfo?(aryx.bugmail)

Keyword works better when it comes to parsing and querying.

Flags: needinfo?(aryx.bugmail)

a pull request here:
https://github.com/mozilla/treeherder/pull/7407

I want to see how this is perceived, possibly I will re-work this to be in FailureSummaryTab.jsx

this is in production now

Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.