Closed Bug 865556 Opened 12 years ago Closed 10 years ago

Get the Android 4.0 robocop-1 failure rate down to something tolerable

Categories

(Testing :: General, defect)

Product:
Testing
Component:
General
Platform:
ARM
Android
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INCOMPLETE

People

(Reporter: philor, Unassigned)

References

Details

Last week, when it came out of a long long time being hidden, it looked sort of okay. Last night, I backed a patch out for causing it to hang starting up testAwesomebar, six out of seven time. On my backout, it timed out starting up testAwesomebar, but by this morning it had switched to timing out earlier, during testBookmarksTab instead. The boy still ain't right, and I'm going to hide it again. A set of bad pandas? A patch that landed between when it looked good and now, that destabilized it? An infra change in the interim? No idea.
Blocks: 865557
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.