https://treeherder.mozilla.org/logviewer.html#?job_id=107840176&repo=autoland [task 2017-06-17T00:07:35.794052Z] 00:07:35 INFO - 155 INFO TEST-START | dom/tests/mochitest/beacon/test_beaconPreflightWithCustomContentType.html [task 2017-06-17T00:07:49.744647Z] 00:07:49 INFO - Buffered messages logged at 00:07:33 [task 2017-06-17T00:07:49.744768Z] 00:07:49 INFO - 156 INFO TEST-PASS | dom/tests/mochitest/beacon/test_beaconPreflightWithCustomContentType.html | sending the beacon should start successfully [task 2017-06-17T00:07:49.746213Z] 00:07:49 INFO - Buffered messages finished [task 2017-06-17T00:07:49.746321Z] 00:07:49 INFO - 157 INFO TEST-UNEXPECTED-FAIL | dom/tests/mochitest/beacon/test_beaconPreflightWithCustomContentType.html | SendBeacon should have succeeded after preflight! - got "red", expected "green" [task 2017-06-17T00:07:49.747346Z] 00:07:49 INFO - SimpleTest.is@SimpleTest/SimpleTest.js:312:5 [task 2017-06-17T00:07:49.747462Z] 00:07:49 INFO - queryIfBeaconSucceeded/xhr.onload@dom/tests/mochitest/beacon/test_beaconPreflightWithCustomContentType.html:29:5
22 failures in the last 7 days (heavily weighted on debug): https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1373945 while this is in core::dom, I suspect this is related to the general android issues. :gbrown, you might want to be aware of this and track it.
I don't see any connection to any other active Android issues. I think this is just timing: there's a setInterval(2000) in the test, which isn't a lot of time on Android Debug. We could try increasing the interval, but we tried that for a very similar case in bug 1296845, without success. Probably best to just skip on Android.
Joel, could you help make it skip as comment 13 suggested?
Pushed by email@example.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/7b30671832a4 Skip test_beaconPreflightWithCustomContentType.html on Android, for intermittent failures; r=me,test-only
Whiteboard: [stockwell needswork:owner] → [stockwell disabled]
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.