Closed Bug 971016 Opened 11 years ago Closed 11 years ago

Increase AWS testing limit

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task)

Product:
Infrastructure & Operations Graveyard
Component:
CIDuty
Platform:
ARM
All
Type:
task
Priority:
Not set
Severity:
blocker

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: RyanVM, Assigned: armenzg)

Details

It's been 25-30min since any started. They all show as pending. All trees closed.
It seems that we're maxed out the number of tst-linux64-ec2 testers: http://people.mozilla.org/~armenzg/sattap/615b1b64.png We're also seeing a huge spike of pushes in the last 3 hours: http://people.mozilla.org/~armenzg/sattap/e6871bf3.png We're going to increase our maximum limit. It will take some time.
Assignee: nobody → armenzg
Hi rail, What do I need to do to increase the maximum number of test machines we generate on EC2?
Summary: AWS and tegra test jobs not starting → Increase AWS testing limit
Before we increase, let's see how bug 969590 impacts us. All jobs with status retry are not run on spot instances what increased the load on on-demand instances. The procedures for on-demand and spot instances are different and have been changed for spot instances recently (because of bug 965001).
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
Product: Release Engineering → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.