Closed
Bug 1140454
Opened 9 years ago
Closed 9 years ago
"Green-up" Android 4.3 Debug emulator tests
Categories
(Testing :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: gbrown, Assigned: gbrown)
References
Details
+++ This bug was initially created as a clone of Bug #1140148 +++ Once we have Android 4.3 Opt tests running well (bug 1140148), we also want to run Android 4.3 *Debug*, in hopes of replacing the existing Android 4.0 Debug tests. This bug tracks test failures specific to Debug tests on the Android 4.3 emulator.
Assignee | ||
Updated•9 years ago
|
Keywords: leave-open
Assignee | ||
Comment 3•9 years ago
|
||
4.3 Debug mochitests are running now. 4.3 Debug xpcshell tests will follow soon. 4.3 Debug reftests are my next priority. Do we want 4.3 Debug robocop? We do not currently run 4.0 Debug robocop. On 4.3 Debug, there are various failures, which look timing related -- looks like a fair amount of effort required. Do we want 4.3 Debug cppunit tests? We do not currently run 4.0 Debug cppunit. There are a couple of 4.3 Debug failures, but these could probably be resolved quickly.
Flags: needinfo?(snorp)
(In reply to Geoff Brown [:gbrown] from comment #3) > 4.3 Debug mochitests are running now. > > 4.3 Debug xpcshell tests will follow soon. > > 4.3 Debug reftests are my next priority. > > Do we want 4.3 Debug robocop? We do not currently run 4.0 Debug robocop. On > 4.3 Debug, there are various failures, which look timing related -- looks > like a fair amount of effort required. If this was easy to get going, maybe, but if it's going to be a lot of work I'd say we should hold off for now. > > Do we want 4.3 Debug cppunit tests? We do not currently run 4.0 Debug > cppunit. There are a couple of 4.3 Debug failures, but these could probably > be resolved quickly. I think these should in theory be easy to fix up, so let's try to get them going.
Flags: needinfo?(snorp)
Assignee | ||
Comment 7•9 years ago
|
||
All Android 4.3 Debug tests are now running on trunk trees.
You need to log in
before you can comment on or make changes to this bug.
Description
•