Closed Bug 1091072 Opened 11 years ago Closed 11 years ago

Run eideticker galaxy nexus android against inbound

Categories

(Testing Graveyard :: Eideticker, defect)

Product:
Testing Graveyard
Component:
Eideticker
Platform:
x86_64
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: wlach, Assigned: wlach)

Details

Let's try to run eideticker android against m-i. With another node (which I have the materials for), a reduced test scope (i.e. killing wikipedia and timecube, which never find anything useful) I think we should be able to keep up and have reduced regression ranges for the stuff we care about.
Ok, this is working. I forgot that two nodes can't run against the same branch in parallel, so for now we just have a seperate node running just two tests (startup-abouthome-dirty, nytimes-load-poststartup).
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Product: Testing → Testing Graveyard
You need to log in before you can comment on or make changes to this bug.