Closed Bug 1554225 Opened 6 years ago Closed 6 years ago

Push broken on nightly

Categories

(Core :: DOM: Push Subscriptions, defect)

defect
Not set
major

Tracking

()

VERIFIED FIXED
mozilla69
Tracking Status
firefox-esr60 --- unaffected
firefox67 --- unaffected
firefox68 --- unaffected
firefox69 blocking verified

People

(Reporter: eoger, Unassigned)

References

(Regression)

Details

(Keywords: regression, Whiteboard: [rca - Coding Error])

I've noticed I was not receiving any push notifications for Send Tab on Desktop Nightly.
STR: On a recent Nightly check for the dom.push.connection.enabled pref, it's false whereas it should be true by default.
I ran mozregression which gave me:

11:12.34 INFO: Last good revision: 55c360c47f31698fe123b0d2838d07d390048e0a
11:12.34 INFO: First bad revision: 1efcba0d56db1d3e12f0fecf3211af6d12a3a646
11:12.34 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=55c360c47f31698fe123b0d2838d07d390048e0a&tochange=1efcba0d56db1d3e12f0fecf3211af6d12a3a646

I have no idea why testing/ prefs are affecting Nightly though.

dom.push.connection.enabled is also false by default for me in Nightly. Marco, this might be what you were seeing, too.

I wonder why this didn't cause any perma fail. I assume we don't have any kind of test in tree which verifies that this preference should be set to true by default?

The code in Marionette which sets this is preference to false only gets run when Marionette is actually enabled. And by default this is not the case.

It's late here and I won't have the time to check that myself until Monday.

(In reply to Henrik Skupin (:whimboo) [⌚️UTC+2] from comment #2)

I wonder why this didn't cause any perma fail. I assume we don't have any kind of test in tree which verifies that this preference should be set to true by default?

We don't, all the push tests set it to true before running. 😞 Not doing that for any prefs that we expect to be set by default is a really good idea, though.

(In reply to Henrik Skupin (:whimboo) [⌚️UTC+2] from comment #2)

It's late here and I won't have the time to check that myself until Monday.

Thanks for looking into it!

This is clearly a bustage as caused by bug 1542244. The following file should never have been changed:
https://searchfox.org/mozilla-central/source/testing/marionette/prefs/marionette.js

I will request a backout.

Severity: normal → major
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla69
Status: RESOLVED → VERIFIED

This bug has been identified as part of a pilot on determining root causes of blocking and dot release drivers.

It needs a root-cause set for it. Please see the list at https://docs.google.com/document/d/1FFEGsmoU8T0N8R9kk-MXWptOPtXXXRRIe4vQo3_HgMw/.

Add the root cause as a whiteboard tag in the form [rca - <cause> ] and remove the rca-needed keyword.

If you have questions, please contact :tmaity.

Keywords: rca-needed
Keywords: rca-needed
Whiteboard: [rca - Coding Error]
Has Regression Range: --- → yes
You need to log in before you can comment on or make changes to this bug.