Closed
Bug 1995627
Opened 1 year ago
Closed 1 year ago
Longer xpcshell tests should start first when running in parallel
Categories
(Testing :: XPCShell Harness, enhancement)
Testing
XPCShell Harness
Tracking
(firefox146 fixed)
RESOLVED
FIXED
146 Branch
| Tracking | Status | |
|---|---|---|
| firefox146 | --- | fixed |
People
(Reporter: florian, Assigned: florian)
References
Details
Attachments
(4 external files)
Very often, the parallel execution phase of xpcshell test jobs has a significant time with only one or two tests still running at the end. Example profile: https://share.firefox.dev/4niH90G
Now that all long running tests have a requesttimeoutfactor annotation, we could use these annotations to sort the tests so the long tests start first.
| Assignee | ||
Comment 1•1 year ago
|
||
| Assignee | ||
Comment 2•1 year ago
|
||
| Assignee | ||
Comment 3•1 year ago
|
||
| Assignee | ||
Comment 4•1 year ago
|
||
| Assignee | ||
Updated•1 year ago
|
Keywords: leave-open
Pushed by fqueze@mozilla.com:
https://github.com/mozilla-firefox/firefox/commit/e0622dafb37d
https://hg.mozilla.org/integration/autoland/rev/e094f91e49ca
optimize xpcshell test parallel execution by avoiding long-running tests at the end, r=jmaher.
https://github.com/mozilla-firefox/firefox/commit/8e2068044c50
https://hg.mozilla.org/integration/autoland/rev/0247cbb6387a
adjust timeouts for high cpu use tests that will now run first and in parallel with more other tests, r=jmaher.
Comment 6•1 year ago
|
||
| bugherder | ||
Pushed by fqueze@mozilla.com:
https://github.com/mozilla-firefox/firefox/commit/2465f82a89b5
https://hg.mozilla.org/integration/autoland/rev/8a78e14c9bc3
show non-default timeout factors on test markers in resource usage profiles, r=ahal.
https://github.com/mozilla-firefox/firefox/commit/c7ef36c36ab7
https://hg.mozilla.org/integration/autoland/rev/d193966cdd35
use the structured log time field for begin_test and end_test in resourcemonitor.py, r=ahal.
Comment 8•1 year ago
|
||
| bugherder | ||
| Assignee | ||
Updated•1 year ago
|
Updated•1 year ago
|
status-firefox146:
--- → fixed
Target Milestone: --- → 146 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•