Closed
Bug 1747918
Opened 2 years ago
Closed 2 years ago
Don't run pingsender during performance tests
Categories
(Toolkit :: Telemetry, task)
Toolkit
Telemetry
Tracking
()
RESOLVED
FIXED
97 Branch
Tracking | Status | |
---|---|---|
firefox97 | --- | fixed |
People
(Reporter: bholley, Assigned: bholley)
References
Details
Attachments
(1 file)
When we enabled pingsender2, we got some Talos regressions in bug 1736796, along with Talos timeouts in bug 1736189. This is presumably because Talos starts and stops the browser in quick succession, and pingsender2 takes longer to start up (by virtue of loading libxul and creating a scratch profile), making it more likely to compete for system resources with the next test.
Easiest thing to do here is just to avoid launching pingsender during performance tests.
Assignee | ||
Comment 1•2 years ago
|
||
Assignee | ||
Comment 2•2 years ago
|
||
For posterity, this try push [1] shows the pingsender2 talos regression disappearing with this patch.
[1] https://treeherder.mozilla.org/jobs?repo=try&revision=2befab546047ff4f1f59a48cd8d8648b6f6662fe
Pushed by bholley@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/6ab17de66b22 Don't invoke pingsender in performance tests. r=chutten,perftest-reviewers,AlexandruIonescu
Comment 4•2 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 2 years ago
status-firefox97:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 97 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•