Closed Bug 1523425 Opened 5 years ago Closed 3 years ago

Problems running mochitest with hostutils 66

Categories

(Firefox for Android Graveyard :: Testing, defect, P3)

Firefox 64
defect

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: snorp, Unassigned)

References

Details

mach helpfully offered to upgrade me to hostutils 66, but this has led to some problems running mochitests against GeckoView. In particular, it looks like tests that need to hit 'example.com' encounter a proxy error. One such test is layout/style/test/test_bug1443344-1.html, which works under hostutils 61 but not 66.

Summary: Problems with hostutils 66 → Problems running mochitest with hostutils 66

This is strange in that host-utils were updated to 66 in bug 1514075 - over a month ago - and have been running fennec mochitests just fine ever since.

Blocks: 1514075

I can confirm that this fails for me with host-utils 66, on ubuntu 18.04:

./mach mochitest layout/style/test/test_bug1443344-1.html --app=org.mozilla.geckoview.test

it fails with "370 seconds with no output". I see logcat like:

01-31 20:28:14.981 2989 3004 D GeckoViewContent[C]: handleEvent: DOMTitleChanged
01-31 20:28:14.982 2989 3004 D GeckoViewContent[C]: handleEvent: pageshow
01-31 20:28:14.990 2989 3004 D GeckoViewNavigation[C]: shouldLoadURI https://example.com/tests?autorun=1&closeWhenDone=1&logFile=%2Fsdcard%2Ftests%2Flogs%2Fmochitest.log&fileLevel=INFO&consoleLevel=INFO&hideResultsTable=1&manifestFile=tests.json&dumpOutputDirectory=%2Fsdcard%2Ftests
01-31 20:28:15.007 2989 3004 D GeckoViewNavigation[C]: handleLoadError: uri=https://example.com/tests?autorun=1&closeWhenDone=1&logFile=%2Fsdcard%2Ftests%2Flogs%2Fmochitest.log&fileLevel=INFO&consoleLevel=INFO&hideResultsTable=1&manifestFile=tests.json&dumpOutputDirectory=%2Fsdcard%2Ftests uri2=https://example.com/tests?autorun=1&closeWhenDone=1&logFile=%2Fsdcard%2Ftests%2Flogs%2Fmochitest.log&fileLevel=INFO&consoleLevel=INFO&hideResultsTable=1&manifestFile=tests.json&dumpOutputDirectory=%2Fsdcard%2Ftests error=2152398920
01-31 20:28:15.009 2989 3004 D GeckoViewNavigation[C]: shouldLoadURI data:text/html,<!DOCTYPE html><head><title>Error</title></head><body>Error!</body></html>
01-31 20:28:15.010 2989 3004 D GeckoViewSelectionAction[C]: handleEvent: visibilitychange
01-31 20:28:15.010 2989 3004 D GeckoViewContent[C]: handleEvent: pagehide
01-31 20:28:15.010 2989 3004 D GeckoViewAutoFill: Clearing auto-fill
01-31 20:28:15.022 2989 3004 E Web Content: [JavaScript Error: "The character encoding of the HTML document was not declared. The document will render with garbled text in some browser configurations if the document contains characters from outside the US-ASCII range. The character encoding of the page must be declared in the document or in the transfer protocol." {file: "data:text/html,<!DOCTYPE html><head><title>Error</title></head><body>Error!</body></html>" line: 0}]
01-31 20:28:15.025 2989 3004 D GeckoViewContent[C]: handleEvent: DOMTitleChanged
01-31 20:28:50.144 1612 1625 I GnssLocationProvider: WakeLock acquired by handleInjectNtpTime()

I backed out bug 1514075 locally, rm -r ~/.mozbuild/android-device/host*, and re-ran the mochitest command -- it set up host-utils 61 and the test succeeded: snorp's observation confirmed.

Priority: -- → P3
See Also: → 1544089
We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → INCOMPLETE
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.