Closed Bug 889926 Opened 12 years ago Closed 11 years ago

turn profiling back on in eideticker

Categories

(Testing Graveyard :: Eideticker, defect)

Product:
Testing Graveyard
Component:
Eideticker
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: blassey, Assigned: wlach)

References

Details

No description provided.
I am told that profiling runs would be very useful for some of the startup/pageload perf work that some folks are currently doing, so let's get these re-enabled for the Galaxy Nexus. Let's seperate out profiling runs by their own device id, as comparisons between profiling runs and non-profiling runs are not really that interesting.
Component: General → Eideticker
Product: Firefox for Android → Testing
It would be nice if profiling worked properly too...
Depends on: 803616
I've rewritten the data on the dashboard to seperate out profiling vs. non-profiling runs and have turned on an additional profiling run for nightly. I'll mark this bug fixed when we nail bug 803616 as I'm worried that the current profiles aren't really telling us much.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Product: Testing → Testing Graveyard
You need to log in before you can comment on or make changes to this bug.