Closed
Bug 1426509
Opened 7 years ago
Closed 7 years ago
In desktop-instrumentation runs in automation, keep a count of every time a XBL binding is attached to an element and save the data as an artifact
Categories
(Core :: DOM: Core & HTML, task, P2)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: bgrins, Assigned: mossop)
References
Details
Attachments
(2 files)
The desktop-instrumentation taskcluster job (added in Bug 1376546) runs the entire b-c suite in one chunk on Nightly builds. This is useful for getting information about what elements get created in the browser UI.
Right now we use JS only to capture this information which is intentionally focused only on the browser.xul document and also attempts to 'de-dupe' certain elements that get created in each test (i.e. the main browser chrome). See https://dxr.mozilla.org/mozilla-central/rev/1624b88874765bf57e9feba176d30149c748d9d2/testing/mochitest/browser-test.js#122-127.
But an alternate and more comprehensive view of this data would be to instrument the platform at least in the parent proess, i.e. nsXBLBinding::SetBoundElement. This would get instances in all documents and also let us track things like which bindings get created before the first paint.
Here's a push that does a printf with the binding id and includes boilerplate needed to get the inst job to run on try: https://hg.mozilla.org/try/rev/4f40f02c359fd12b5fa7e977261701c28f2ed5a8. Ideally we could turn this into something that could be landed and tracked over time though. Here's the basic idea:
* Check if the TEST_SUITE env variable is equal to "browser-chrome-instrumentation"
* Keep a map of binding ids and the number of times they get created
* At browser shutdown serialize that map and write it out to an artifact file at the path specified in the MOZ_UPLOAD_DIR environment variable
Updated•7 years ago
|
Priority: -- → P2
Assignee | ||
Updated•7 years ago
|
Assignee: nobody → dtownsend
Comment hidden (mozreview-request) |
Comment hidden (mozreview-request) |
Assignee | ||
Comment 3•7 years ago
|
||
As discussed this morning the try results we have for this are enough for now, no need to land this at the moment.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
Updated•5 years ago
|
Type: enhancement → task
You need to log in
before you can comment on or make changes to this bug.
Description
•