Closed Bug 877553 Opened 13 years ago Closed 12 years ago

Switch to running b2g VM reftests on a twig instead of on mozilla-central

Categories

(Release Engineering :: General, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: philor, Unassigned)

Details

We started running b2g reftests on ec2 slaves on mozilla-central, knowing that they were all failing, so they could be looked at, three weeks ago. It's entirely possible that the person who is in theory looking at them still doesn't actually realize that he is supposed to be looking at them, much less realize that we are spending actual cash money to do 40 or 80 runs per day every one of which gets the exact same results, "yeah, r1 is still permaorange, and r2 is still permaorange, and r3 is still permaorange, and r4 is still..." This is a perfect job for a twig, where we can build only b2g, run only reftests, and not build or run a single thing except when the person who is looking at them wants to look at something different, and where experimental pushes aren't going to require landing directly on mozilla-central, something that in these days just isn't done.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
Product: mozilla.org → Release Engineering
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.