Closed
Bug 1643284
Opened 4 years ago
Closed 4 years ago
move talos/raptor profiling jobs under --full as they not needed for full runs
Categories
(Testing :: Performance, enhancement, P3)
Testing
Performance
Tracking
(firefox79 fixed)
RESOLVED
FIXED
mozilla79
| Tracking | Status | |
|---|---|---|
| firefox79 | --- | fixed |
People
(Reporter: jmaher, Assigned: jmaher)
Details
(Whiteboard: [ci-costs-2020:done])
Attachments
(1 file)
|
(deleted),
text/x-phabricator-request
|
Details |
here is an example of what is easy to schedule on try server for perf tests:
https://treeherder.mozilla.org/#/jobs?repo=try&author=emilio%40crisal.io&tochange=d10f4829f30e01ff5edbc8c0fc18095ea548e64a&fromchange=2f3b40532ee54ebcb3f1b640410f817b54aa93c3
it looks like everything was scheduled with --rebuild 10 on both pushes.
While there are other ways to reduce the need for --rebuild 10, the profiling jobs do not need to be run all the time and should only be run intentionally.
|
Assignee | |
Comment 1•4 years ago
|
||
this really falls into the category of tier-2 tests shouldn't be scheduled by default
|
|
Assignee | |
Comment 2•4 years ago
|
||
require --full to schedule talos/raptor profiling jobs on try.
|
||
Updated•4 years ago
|
Assignee: nobody → jmaher
Status: NEW → ASSIGNED
|
||
Updated•4 years ago
|
Priority: -- → P3
Pushed by jmaher@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/44585c915bfd
require --full to schedule talos/raptor profiling jobs on try. r=davehunt,ahal
|
||
Comment 4•4 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
status-firefox79:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla79
|
|
Assignee | |
Updated•4 years ago
|
Whiteboard: [ci-costs-2020:todo] → [ci-costs-2020:done]
You need to log in
before you can comment on or make changes to this bug.
Description
•