Closed Bug 1108602 Opened 11 years ago Closed 11 years ago

Android 2.3 reftests sit pending for a long time on the release branches

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task)

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

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: RyanVM, Unassigned)

Details

Just sitting perma-pending. Presumably fallout from the split APK work. All Android-building release branches closed.
OK, looks like they're starting after 10-15min of pending time. I'm going to reopen the trees but leave this bug open for investigation.
Summary: Android 2.3 reftests aren't starting on the release branches → Android 2.3 reftests sit pending for a long time on the release branches
I don't think that this is fallout from the split apk work since that afaik this isn't on the release branches yet (riding trains) I often find that it takes a while for the aws instances to instantiate in the morning when code starts to land and pending count rise. They are all spot instances we have to bid on.
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.