Closed
Bug 1254821
(perf-e10s-timeout)
Opened 9 years ago
Closed 3 years ago
[e10s] Many of the devtools/client/performance tests timeout on Linux debug/ASAN with e10s enabled
Categories
(DevTools :: Performance Tools (Profiler/Timeline), defect, P2)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: RyanVM, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(1 obsolete file)
This is pretty widespread, so I'm filing one bug as a catch-all. While I'm somehow guessing we hit some of these intermittently in non-e10s as well, the overhead from that puts us over the top into a permafail situation basically. https://treeherder.mozilla.org/logviewer.html#?job_id=17784628&repo=try https://treeherder.mozilla.org/logviewer.html#?job_id=17686761&repo=try https://treeherder.mozilla.org/logviewer.html#?job_id=17686577&repo=try https://treeherder.mozilla.org/logviewer.html#?job_id=17716826&repo=try
Updated•9 years ago
|
Blocks: dte10s
tracking-e10s:
--- → +
Comment 2•9 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/8fb49080668e
Status: NEW → RESOLVED
Closed: 9 years ago
status-firefox48:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 48
Reporter | ||
Comment 3•9 years ago
|
||
Whoops, forgot a leave-open on this one.
Status: RESOLVED → REOPENED
status-firefox48:
fixed → ---
Resolution: FIXED → ---
Target Milestone: Firefox 48 → ---
Comment 4•9 years ago
|
||
This should theoretically not be a problem anymore now after bug 1245886 landed. Will keep an eye on it.
Assignee: nobody → vporof
Status: REOPENED → ASSIGNED
Reporter | ||
Comment 5•9 years ago
|
||
Looks like we're not out of the woods yet. https://treeherder.mozilla.org/logviewer.html#?job_id=18220348&repo=try
Updated•9 years ago
|
Alias: perf-e10s-timeout
Comment 28•9 years ago
|
||
Can't work on this right now, busy with Tofino.
Assignee: vporof → nobody
Status: ASSIGNED → NEW
Comment 29•8 years ago
|
||
Ryan: Can I get an update on the status of this bug? I'm looking at Q3 work and prioritizing bugs. Victor is working on Tofino now, and isn't available to work on this. I don't have enough knowledge of the perf tool to help out with this bug at this time, although part of my plan is to learn the ins and outs of the tool this upcoming quarter. I was thinking about setting it as P2 for now, and re-evaluate next quarter.
Flags: needinfo?(ryanvm)
Reporter | ||
Comment 30•8 years ago
|
||
Fix at your leisure, the tests are all being skipped anyway and nobody seems to mind. http://hg.mozilla.org/mozilla-central/file/tip/devtools/client/performance/test/browser.ini#l4
Flags: needinfo?(ryanvm)
Updated•8 years ago
|
Priority: P1 → P2
Updated•6 years ago
|
Product: Firefox → DevTools
Updated•6 years ago
|
tracking-e10s:
+ → ---
Reporter | ||
Comment 31•3 years ago
|
||
NI myself to see if we can re-enable these now.
Flags: needinfo?(ryanvm)
Reporter | ||
Comment 32•3 years ago
|
||
Reporter | ||
Comment 33•3 years ago
|
||
ASAN was green without any issue and I was able to get debug green as well with only a few disabled tests:
https://treeherder.mozilla.org/jobs?repo=try&group_state=expanded&revision=e1a4d2a540fe2cbfead98af8e9723bd50395d5b0
While I was there, I took the liberty of disabling browser_perf-calltree-js-categories.js unconditionally because recent history would suggest that it's failing across the board pretty consistently these days.
Flags: needinfo?(ryanvm)
Updated•3 years ago
|
Assignee: nobody → ryanvm
Status: NEW → ASSIGNED
Comment 34•3 years ago
|
||
Hey Ryan, if that's not too urgent, I'd suggest that you don't spend too much time on this as we'll remove the code in the coming months. So disabling sounds good enough.
Updated•3 years ago
|
Attachment #9254159 -
Attachment is obsolete: true
Reporter | ||
Comment 35•3 years ago
|
||
I'm fine WONTFIX!
Assignee: ryanvm → nobody
Status: ASSIGNED → RESOLVED
Closed: 9 years ago → 3 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•