Normandy initialize is called twice with --first-startup
Categories
(Firefox :: Normandy Client, defect, P1)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr68 | --- | unaffected |
firefox-esr78 | --- | wontfix |
firefox76 | --- | wontfix |
firefox77 | --- | wontfix |
firefox78 | --- | wontfix |
firefox79 | --- | fix-optional |
People
(Reporter: mythmon, Unassigned)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 obsolete file)
When Firefox is run with the --first-startup
flag, such as when a new version is installed, Normandy's initialization sequence is triggered twice. First by FirstStartup.jsm
, and second by BrowserGlue.jsm
.
This is definitely wrong, and has caused on specific problem that we know of. If a rollout is active, it will be graduated immediately, since the second initialization will see the results of the first.
Normandy's initialization sequence should be idempotent.
Reporter | ||
Comment 1•4 years ago
|
||
Reporter | ||
Updated•4 years ago
|
Updated•4 years ago
|
Pushed by mcooper@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/45c377f2f2f1 Normandy initialize should be idempotent r=rhelmer
Comment 3•4 years ago
|
||
bugherder |
Updated•4 years ago
|
Updated•4 years ago
|
Backout by ccoroiu@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/8278280311bf Backed out changeset 45c377f2f2f1 on request by dev due to regression of 1643499
Comment 6•4 years ago
|
||
Backout merged: https://hg.mozilla.org/mozilla-central/rev/8278280311bf
Reporter | ||
Comment 7•4 years ago
|
||
When re-implementing this, care should be taken to avoid the regression in bug 1643499 happening again.
Updated•4 years ago
|
Updated•4 years ago
|
Comment hidden (off-topic) |
Updated•2 years ago
|
Comment 9•2 years ago
|
||
ni? to investigate when back from PTO
Comment 10•2 years ago
|
||
Given this affects studies and Normandy is being deprecated, I'm going to classify this as WONTFIX.
Description
•