Closed Bug 1218627 Opened 9 years ago Closed 8 years ago

Intermittent test_mozsettings.html | Geolocation didn't work after setting geolocation.enabled to true.

Categories

(Core :: DOM: Geolocation, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla52
Tracking Status
firefox50 --- wontfix
firefox51 --- wontfix
firefox52 --- fixed

People

(Reporter: philor, Assigned: mds)

References

Details

(Keywords: intermittent-failure)

Attachments

(1 file)

Thanks Phil. If the issue persists, please reopen this.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WORKSFORME
Impressively low-frequency intermittent, https://treeherder.mozilla.org/logviewer.html#?job_id=217344&repo=autoland
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Attachment #8768205 - Flags: review?(dougt)
Assignee: nobody → michelangelo
Attachment #8768205 - Flags: review?(dougt) → review+
Comment on attachment 8768205 [details]
Bug 1218627 - Removing MozSettings API from Geo (and fixing randomly failing tests).

https://reviewboard.mozilla.org/r/62510/#review59256

lgtm.
Pushed by cbook@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/ef8fcd144a50
Fixing randomly failing test(s) in Geo. r=dougt
Keywords: checkin-needed
https://hg.mozilla.org/mozilla-central/rev/ef8fcd144a50
Status: REOPENED → RESOLVED
Closed: 8 years ago8 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla50
Hi, please back out this patch as it has caused a regression of an important feature of B2G OS.

Removing this entire feature is clearly not necessary in order to fix this incredibly intermittent test failure.

I think long term we can work together to remove the entire settings API, but this requires a proper discussion with stakeholders. Please don't simply remove code without asking the people who are using it.
No longer blocks: 1285734
Status: RESOLVED → REOPENED
Flags: needinfo?(michelangelo)
Flags: needinfo?(dougt)
Resolution: FIXED → ---
No backout.

B2G OS is tier 3.  The announcement is https://lists.mozilla.org/pipermail/dev-fxos/2016-January/002410.html.

Tier 3 platforms have a maintainer (you?) or community (you?) which attempt to keep the platform working.  As the module owner, I have no intention of supporting the Settings API as it adds untested complexity to Geolocation.  I suggest you fork if you want to continue supporting B2G -- which I thought you already did at the end of may?

Happy to discuss further -- but this bug isn't the right place.
Status: REOPENED → RESOLVED
Closed: 8 years ago8 years ago
Flags: needinfo?(dougt)
Resolution: --- → FIXED
Flags: needinfo?(michelangelo)
It's great to see that we spend engineering time to fix intermittent failures that happen once every 9 months. I guess that means that this is one of our worst cases?

I'm gonna back this out, and let's see it that fails again before we have an acceptable solution for b2g.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Target Milestone: mozilla50 → ---
This was r+'ed and landed few months ago; later on it was backed out as for comment #12.

In light of [1], the patch can be landed. It has therefore been rebased; the original r+ from Doug stands.

[1] https://groups.google.com/forum/#!msg/mozilla.dev.fxos/FoAwifahNPY/Lppm0VHVBAAJ
Keywords: checkin-needed
Patch doesn't apply cleanly anymore. Please rebase.
Flags: needinfo?(michelangelo)
Keywords: checkin-needed
(In reply to Ryan VanderMeulen [:RyanVM] from comment #18)

> Patch doesn't apply cleanly anymore. Please rebase.

Rebased on top of b1d60f2f68c7. Thanks.
Flags: needinfo?(michelangelo)
Keywords: checkin-needed
Pushed by ryanvm@gmail.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/d03efada4985
Remove MozSettings API from Geo (and fix randomly failing tests). r=dougt
Keywords: checkin-needed
https://hg.mozilla.org/mozilla-central/rev/d03efada4985
Status: REOPENED → RESOLVED
Closed: 8 years ago8 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla52
Should we uplift this anywhere or can it ride the trains?
Flags: needinfo?(michelangelo)
(In reply to Ryan VanderMeulen [:RyanVM] from comment #24)

> Should we uplift this anywhere or can it ride the trains?

There's no urgency, it can ride with the trains, yes.:)
Thanks for asking, though.
Flags: needinfo?(michelangelo)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: