Add browsertime and awsy perf tests for firefox built with clang-trunk
Categories
(Testing :: General, task)
Tracking
(firefox91 fixed)
Tracking | Status | |
---|---|---|
firefox91 | --- | fixed |
People
(Reporter: andi, Assigned: andi)
References
Details
Attachments
(1 file)
On a daily basis we have two targets that build firefox on m-c and m-b with a fresh snapshot of clang-trunk. In order to track performance over time for clang-trunk we need to add perf tests for the ff build using clang-trunk.
Assignee | ||
Comment 1•4 years ago
|
||
Updated•4 years ago
|
Comment 3•4 years ago
|
||
Backed out for causing linting failures.
Backout link: https://hg.mozilla.org/integration/autoland/rev/d348162773828452359b3f8a7339f11cd13c815c
Failure log: https://treeherder.mozilla.org/logviewer?job_id=343766341&repo=autoland&lineNumber=68
Comment 6•4 years ago
|
||
bugherder |
Comment 7•3 years ago
|
||
:andi, I don't see any perf tests running on mozilla-central, are these tests still desired? Who is looking at the data regularly?
Comment 9•2 years ago
|
||
Hi :andi, is anyone monitoring the results from these tests? If not, is there a reason why performance tests are running on this platform? The tier-2 clang build is causing issues for some of our test setup changes (increasing tiers), so I'm considering either reducing the number of test that run with the clang build, or disabling browsertime on this platform.
Assignee | ||
Comment 10•2 years ago
|
||
Yes, we want to have an idea where changes from clang-trunk might affect firefox perf. If we wouldn't have these tests when we will update to the next clang version we might hit perf issues that could have been foreseen.
Comment 11•2 years ago
|
||
Ok great thanks! So what we'll do is remove the problematic tests from the clang builds since they can't run at tier-1 using a tier-2 build.
Description
•