summary is undefined when opening bug filer for xperf failure

RESOLVED FIXED

Status

Tree Management
Treeherder
RESOLVED FIXED
7 months ago
7 months ago

People

(Reporter: KWierso, Assigned: KWierso)

Tracking

Details

Attachments

(1 attachment)

(Assignee)

Description

7 months ago
I'm trying to file a bug for this xperf failure: https://treeherder.mozilla.org/#/jobs?repo=mozilla-inbound&revision=865e18f01ece0838ea9767f200a52df68154b62e&bugfiler&noautoclassify&filter-searchStr=8c859e5e168988b7aeafaf37c42d0d6d7dc61061

But when I click the button to open the bug filer UI, nothing visible happens. An error gets logged to the console. From production, the error is "Q is undefined", but if I run the unminified UI, I get "summary is undefined".


The formatting of the failure is untypical:  TEST-UNEXPECTED-FAIL : xperf: File '{firefox}\browser\extensions\{972ce4c6-7e08-4474-a285-3208198ce6fd}.xpi' was accessed and we were not expecting it. DiskReadCount: 2, DiskWriteCount: 0, DiskReadBytes: 16384, DiskWriteBytes: 0

This causes the bug filer to reach some code it shouldn't reach, making it pass a non-existent second item in an array of length=1.

Comment 1

7 months ago
Created attachment 8890641 [details] [review]
[treeherder] KWierso:fixxperffiler > mozilla:master
(Assignee)

Updated

7 months ago
Assignee: nobody → wkocher
(Assignee)

Comment 2

7 months ago
Comment on attachment 8890641 [details] [review]
[treeherder] KWierso:fixxperffiler > mozilla:master

No rush on this one, I can just file these manually until it gets dealt with. :)
Attachment #8890641 - Flags: review?(cdawson)

Updated

7 months ago
Attachment #8890641 - Flags: review?(cdawson) → review+

Comment 3

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

https://github.com/mozilla/treeherder/commit/5bd8e7a1499ef88464a5b766fb95d58edba4ca0e
Bug 1384788 - (bug filer) handle xperf failures' non-typical formatting (#2661) r=camd
(Assignee)

Updated

7 months ago
Status: NEW → RESOLVED
Last Resolved: 7 months ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.