639898 - Tracking bug for talos performance testing on firebug (non-clean state)

Status: RESOLVED FIXED

(Testing :: Talos, defect, P2)

Description

[Steve Roussey (:sroussey)]

User-Agent:       Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b13pre) Gecko/20110303 Firefox/4.0b13pre
Build Identifier: 

In reference to bug 599169:

Firebug, just after install, has all its panels disabled, and even if they are
enabled, it also has an activation list of sites, initially zero. There are
some hooks and plenty of startup code, but you will likely get different
results based on what preferences are set. I don't think it is the only
extension to act that way. Think of greasemonkey with no user scrips.

Perhaps it could be done this with a clean profile (bug 599169), and also do it
for a "dirty" profile with extension settings turned on all over the place.
That would give best case and worst case. Rather than just best case of bug 599169.

For Firebug we can have all panels enabled, and have it activate on all sites.

Reproducible: Always

Comment 1

[alice nodelman [:alice] [:anode]]

Can you give the list of preference that you would like set?

Comment 2

[Steve Roussey (:sroussey)]

Honza, what prefs would activate Firebug on all sites and enable all panels? Possibly open FB, or no?

Comment 3

[Jan Honza Odvarko [:Honza] (always need-info? me)]

- extensions.firebug.allPagesActivation : activate Firebug on all sites.

- extensions.firebug.console.enableSites : enable the Console panel
- extensions.firebug.net.enableSites : enable the Net panel
- extensions.firebug.script.enableSites : enable the Script panel (debugger)

Honza

Comment 4

[alice nodelman [:alice] [:anode]]

It is relatively easy to run with a custom set of prefs for a given set of tests.  Is there any reason to do run the firebug test without these prefs enabled?

Reducing bug summary to firebug, as that is what all the comments are referring to.

Comment 5

[alice nodelman [:alice] [:anode]]

Attachment: [checked in]create new addon.config with special extension settings (take 1)

Comment 6

[alice nodelman [:alice] [:anode]]

Attachment: [checked in]have addon tests run using the new addon.config (take 1)

Comment 7

[Joel Maher ( :jmaher ) (UTC -8)]

Comment on attachment 523135 [details] [diff] [review]
[checked in]have addon tests run using the new addon.config (take 1)

r=me, straightforward change.

Comment 8

[Joel Maher ( :jmaher ) (UTC -8)]

Comment on attachment 523132 [details] [diff] [review]
[checked in]create new addon.config with special extension settings (take 1)

my only concern is adding more and more .config special case files.  It sounds like all addons related config changes can continue to go in this new addons.config file and life will be good!

Comment 9

[alice nodelman [:alice] [:anode]]

Comment on attachment 523132 [details] [diff] [review]
[checked in]create new addon.config with special extension settings (take 1)

changeset:   228:65f8c60e5199

Comment 10

[alice nodelman [:alice] [:anode]]

Comment on attachment 523135 [details] [diff] [review]
[checked in]have addon tests run using the new addon.config (take 1)

changeset:   3959:964cca043512

Comment 11

[alice nodelman [:alice] [:anode]]

Rolled out in bug 649175.

Comment 12

[John J. Barton]

Are the results from any tests run with the settings discussed here available anywhere?

Comment 13

[alice nodelman [:alice] [:anode]]

The results will be those reported to AMO - so whatever the current results available there are they are using this code.