Closed
Bug 1802567
Opened 2 years ago
Closed 1 year ago
Determine if 300 maximum tasks is too little
Categories
(Testing :: Performance, task, P2)
Testing
Performance
Tracking
(firefox118 fixed)
RESOLVED
FIXED
118 Branch
| Tracking | Status | |
|---|---|---|
| firefox118 | --- | fixed |
People
(Reporter: sparky, Assigned: sparky)
References
(Blocks 1 open bug)
Details
(Whiteboard: [fxp])
Attachments
(1 file)
I was using the tool locally and found that 300 might be a bit too low in certain situations. It did prevent me from pushing 700 tasks (per push) and there were a lot that I didn't want so it did it's purpose. However, 400-500 might be more reasonable for larger tests.
|
||
Updated•1 year ago
|
Whiteboard: [fxp]
|
Assignee | |
Comment 1•1 year ago
|
||
We should increase this to ~600 tasks.
|
|
Assignee | |
Comment 2•1 year ago
|
||
Depends on D186046
|
||
Updated•1 year ago
|
Assignee: nobody → gmierz2
Status: NEW → ASSIGNED
Pushed by gmierz2@outlook.com:
https://hg.mozilla.org/integration/autoland/rev/d276fb10dd59
Increase task selection limit in mach try perf to 600. r=perftest-reviewers,kshampur DONTBUILD
|
||
Comment 4•1 year ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
status-firefox118:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 118 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•