Closed Bug 1057772 Opened 11 years ago Closed 9 years ago

Figure out why the test from bug 1036214 doesn't pass on Android debug on Aurora33

Categories

(Core :: DOM: Core & HTML, defect)

ARM
Android
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: RyanVM, Unassigned)

Details

The test added by bug 1036214 had to be disabled on Android debug when it was uplifted to Aurora33 due to test failures shown in the link below: https://tbpl.mozilla.org/php/getParsedLog.php?id=46490075&tree=Mozilla-Aurora It passes on m-c and on other platforms. We should figure out why it's broken on Android for 33.
Flags: needinfo?(bobbyholley)
The failure is occurring when instantiating the test component (i.e. new TestInterfaceJS()). While curious, I think the chance that this is an actual bug we care about is rather low, and the chance that it's just an issue with the (relatively involved) test infrastructure is pretty high. As long as it's passing on trunk, my guess is that it's not high enough priority to investigate.
Flags: needinfo?(bobbyholley)
Well, is the test enabled at all on trunk on that platform? We had some issues with entire M* chunks being disabled on Android, and tests starting to fail when they moved across chunk boundaries...
Flags: needinfo?(bobbyholley)
(In reply to Boris Zbarsky [:bz] from comment #2) > Well, is the test enabled at all on trunk on that platform? We had some > issues with entire M* chunks being disabled on Android, and tests starting > to fail when they moved across chunk boundaries... Yes, it is: https://tbpl.mozilla.org/php/getParsedLog.php?id=47247998&tree=Mozilla-Central&full=1
Flags: needinfo?(bobbyholley)
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INCOMPLETE
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.