Closed Bug 902160 Opened 7 years ago Closed 7 years ago

Update androidx86.json for x86 emu mochitests

Categories

(Testing :: Mochitest, defect)

x86
Android
defect
Not set

Tracking

(Not tracked)

RESOLVED FIXED
mozilla26

People

(Reporter: gbrown, Assigned: gbrown)

References

Details

Attachments

(1 file)

Follow-up to bug 875737. With the current x86 emulator, mochitests behave very similarly on x86 and arm. Only a few differences are needed between android.json and androidx86.json to get a clean run.
$ diff android.json androidx86.json
3a4
>  "MochiKit-1.4.2/tests/test_MochiKit-Async.html": "x86 only",
101a103,104
>  "content/media/test/test_can_play_type_mpeg.html": "x86 only",
>  "content/media/test/test_unseekable.html": "x86 only",
108a112
>  "docshell/test/navigation/test_not-opener.html", "x86 only",
Comment on attachment 786496 [details] [diff] [review]
re-syncs android.json and androidx86.json and adds 4 tests that fail only on x86

Review of attachment 786496 [details] [diff] [review]:
-----------------------------------------------------------------

could it be we are able to run even more tests on android x86 now!
Attachment #786496 - Flags: review?(jmaher) → review+
https://hg.mozilla.org/mozilla-central/rev/37f4b8b2dbe7
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla26
A follow-up was necessary to correct the comments:

https://hg.mozilla.org/integration/mozilla-inbound/rev/177dcf987033
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
https://hg.mozilla.org/mozilla-central/rev/177dcf987033
Status: REOPENED → RESOLVED
Closed: 7 years ago7 years ago
Resolution: --- → FIXED
And another follow-up was necessary because a misplaced comma was causing no end of confusion:

https://hg.mozilla.org/integration/mozilla-inbound/rev/2a179cae2cfc
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
https://hg.mozilla.org/mozilla-central/rev/2a179cae2cfc
Status: REOPENED → RESOLVED
Closed: 7 years ago7 years ago
Resolution: --- → FIXED
Blocks: 936226
You need to log in before you can comment on or make changes to this bug.