Closed
Bug 1167671
Opened 10 years ago
Closed 10 years ago
run Android 4.3 debug xpshell on c3.xlarge
Categories
(Infrastructure & Operations Graveyard :: CIDuty, task)
Infrastructure & Operations Graveyard
CIDuty
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: kmoir, Assigned: kmoir)
References
Details
Attachments
(3 files)
|
1.27 KB,
patch
|
jlund
:
review+
kmoir
:
checked-in+
|
Details | Diff | Splinter Review |
|
514 bytes,
text/plain
|
Details | |
|
916 bytes,
patch
|
jlund
:
review+
kmoir
:
checked-in+
|
Details | Diff | Splinter Review |
as per bug 1164996
| Assignee | ||
Updated•10 years ago
|
Assignee: nobody → kmoir
| Assignee | ||
Comment 1•10 years ago
|
||
| Assignee | ||
Comment 2•10 years ago
|
||
builder diff
| Assignee | ||
Updated•10 years ago
|
Attachment #8610226 -
Flags: review?(jlund)
Comment 3•10 years ago
|
||
Comment on attachment 8610226 [details] [diff] [review]
bug1167671.patch
Review of attachment 8610226 [details] [diff] [review]:
-----------------------------------------------------------------
the builderlist diff suggests that you just changed try jobs. I'm guessing this will change across all branches and the builderlist diff only caught a change in order for the try branch specifically?
Attachment #8610226 -
Flags: review?(jlund) → review+
| Assignee | ||
Comment 4•10 years ago
|
||
No, I only wanted to enabled it on try. The loops that enable the tests on trunk etc. exclude try.
| Assignee | ||
Comment 5•10 years ago
|
||
cloud tools patch to enable c3.xlarge for xpcshell on debug for Android 4.3
Attachment #8611212 -
Flags: review?(jlund)
| Assignee | ||
Updated•10 years ago
|
Attachment #8610226 -
Flags: checked-in+
Updated•10 years ago
|
Attachment #8611212 -
Flags: review?(jlund) → review+
| Assignee | ||
Updated•10 years ago
|
Attachment #8611212 -
Flags: checked-in+
| Assignee | ||
Comment 6•10 years ago
|
||
So I have an AWS question
in configs/watch_pending.cfg tst-emulator64 has a limit of 1300
"tst-emulator64": 1300,
but in production_config.py in bbconfigs, there are only 400 machines allocated for this class. I noticed that the pending counts for this pool of machines is going up since I'm enabling a lot of Android 4.3 debug tests on them. Will the pool every exceed 400 given the limits in production_config.py?
Flags: needinfo?(rail)
Comment 7•10 years ago
|
||
Setting the limit in configs/watch_pending.cfg unfortunately is not enough. We have 2 additional systems that have to know about this:
1) buildbot uses slaves set in production_config.py, this is the first step you need to do to add more slaves. Reconfig is required to make it live.
2) slavealloc needs to be updated to be able to route slaves to masters. could-tools also uses slavealloc data to determine available slave name.
I hope this helps.
Flags: needinfo?(rail)
| Assignee | ||
Comment 8•10 years ago
|
||
thanks rail, that's what I suspected:-)
| Assignee | ||
Comment 9•10 years ago
|
||
The pending counts have been okay so I'm going to close this bug.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Updated•7 years ago
|
Component: Platform Support → Buildduty
Product: Release Engineering → Infrastructure & Operations
Updated•6 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•