Closed Bug 1025959 Opened 6 years ago Closed 6 years ago

webapp updating needs to be disabled during tests, so as to not connect to controller.apk.firefox.com

Categories

(Firefox for Android :: Web Apps (PWAs), defect)

All
Android
defect
Not set

Tracking

()

RESOLVED FIXED
Firefox 33
Tracking Status
firefox31 --- fixed
firefox32 --- fixed
firefox33 --- fixed
firefox-esr24 --- unaffected
b2g-v1.3 --- fixed
b2g-v1.3T --- fixed
b2g-v1.4 --- fixed
b2g-v2.0 --- fixed
b2g-v2.1 --- fixed

People

(Reporter: froydnj, Assigned: froydnj)

References

Details

Attachments

(1 file)

From a try run with patches for bug 995417 applied:

06-16 08:02:17.321 D/GeckoWebapps( 2344): getAll
06-16 08:02:17.371 I/Gecko   ( 2344): Non-local network connections are disabled and a connection attempt to controller.apk.firefox.com was made.  You should only access hostnames available via the test networking proxy (if running mochitests) or from a test-specific httpd.js server (if running xpcshell tests).

Seems to be on a timer, so it's just a matter of luck as to whether we ping this host.
More pref setting...
Attachment #8440743 - Flags: review?(jmaher)
Comment on attachment 8440743 [details] [diff] [review]
disable checks for webapp updates during tests

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

thanks, should we do this for talos as well?
Attachment #8440743 - Flags: review?(jmaher) → review+
Yes, we should do this for talos.  I will take a look at backporting all the prefs once the main m-c bits are in if you haven't beat me to it.

https://hg.mozilla.org/integration/mozilla-inbound/rev/79f5a8bc4ee2
Assignee: nobody → nfroyd
https://hg.mozilla.org/mozilla-central/rev/79f5a8bc4ee2
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 33
nfroyd- if these are critical to talos we should land them soon, otherwise they make a great good first bug.  In fact we could modify bug 994302 to include the rest of the preferences.
You need to log in before you can comment on or make changes to this bug.