use t-linux-docker{,-noscratch} pools instead of t-linux-{large,xlarge}{,-source}{,-noscratch}-gcp
Categories
(Firefox Build System :: Task Configuration, task, P2)
Tracking
(firefox140 fixed)
| Tracking | Status | |
|---|---|---|
| firefox140 | --- | fixed |
People
(Reporter: jcristau, Assigned: jcristau)
References
(Blocks 1 open bug)
Details
(Keywords: perf-alert)
Attachments
(4 files, 1 obsolete file)
| Assignee | ||
Updated•8 months ago
|
Updated•8 months ago
|
| Assignee | ||
Comment 1•8 months ago
|
||
An exception is made for xpcshell on ccov, due to unresolved timeout /
out of memory issues.
| Assignee | ||
Comment 2•8 months ago
|
||
retry-exit-status 137 was added during the migration from aws to gcp as it was
generally a symptom of spot termination. Since then, worker-runner has learned
to detect when that happens and terminate the task as worker-shutdown, so
this should no longer be necessary when using a recent worker image. It
also interacts badly with how d2g deals with exceeding maxRunTime.
| Assignee | ||
Comment 3•8 months ago
|
||
| Assignee | ||
Comment 4•8 months ago
|
||
I should note this switches some tasks from n2-standard-4 to c2-standard-4 instance types. They should have roughly the same specs though. Previously we had "large" and "xlarge" pools that mapped to basically the same thing (since bug 1862675).
Updated•8 months ago
|
| Assignee | ||
Comment 5•8 months ago
|
||
| Assignee | ||
Comment 6•8 months ago
|
||
Comment 8•8 months ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/5cbedf2ce275
https://hg.mozilla.org/mozilla-central/rev/089f4eaad6e6
https://hg.mozilla.org/mozilla-central/rev/90b2a589155c
https://hg.mozilla.org/mozilla-central/rev/fe6dfa38d472
Comment 9•7 months ago
|
||
Julien, is D246601 going to be pushed as well? It hasn't been landed yet but this bug is closed as fixed.
| Assignee | ||
Comment 10•7 months ago
|
||
Probably not. I split out the 2 permanent failures, the rest actually seemed to be pre-existing intermittents.
Comment 11•7 months ago
|
||
(In reply to Pulsebot from comment #7)
Pushed by jcristau@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/5cbedf2ce275
switch most linux tests to new worker pools based on generic-worker + d2g
r=taskgraph-reviewers,bhearsum
https://hg.mozilla.org/integration/autoland/rev/089f4eaad6e6
don't retry tasks on SIGKILL. r=taskgraph-reviewers,Eijebong
https://hg.mozilla.org/integration/autoland/rev/90b2a589155c
disable webdriver/tests/bidi/network/add_intercept/contexts.py on linux
asan. r=jdescottes,webdriver-reviewers
https://hg.mozilla.org/integration/autoland/rev/fe6dfa38d472
disable browser_fullscreen_warning.js on linux socketprocess for frequent
failures. r=jmaher
Perfherder has detected a devtools performance change from push fe6dfa38d472be8cdab3e1c7c74bebe4331d8323.
If you have any questions, please reach out to a performance sheriff. Alternatively, you can find help on Slack by joining #perf-help, and on Matrix you can find help by joining #perftest.
Improvements:
| Ratio | Test | Platform | Options | Absolute values (old vs new) |
|---|---|---|---|---|
| 10% | reload-inspector:content-process memory | linux1804-64-qr | 8,960,000.00 -> 8,022,357.33 | |
| 10% | reload-inspector:content-process memory | linux1804-64-qr | 9,459,466.24 -> 8,501,248.00 |
Details of the alert can be found in the alert summary, including links to graphs and comparisons for each of the affected tests.
If you need the profiling jobs you can trigger them yourself from treeherder job view or ask a performance sheriff to do that for you.
You can run all of these tests on try with ./mach try perf --alert 44987
The following documentation link provides more information about this command.
Updated•7 months ago
|
Description
•