Closed
Bug 1479857
Opened 5 years ago
Closed 5 years ago
Add a preference (default on) for autoconfig sanboxing for first release
Categories
(Core :: AutoConfig (Mission Control Desktop), defect)
Tracking
()
VERIFIED
FIXED
mozilla63
People
(Reporter: shell, Assigned: mkaply)
References
Details
Attachments
(4 files)
3.95 KB,
patch
|
Details | Diff | Splinter Review | |
46 bytes,
text/x-phabricator-request
|
kmag
:
review+
lizzard
:
approval-mozilla-beta+
|
Details | Review |
914 bytes,
patch
|
Details | Diff | Splinter Review | |
46 bytes,
text/x-phabricator-request
|
RyanVM
:
review+
|
Details | Review |
Since this is is a release only feature. All other builds (beta, dev edition, nightly, esr) will not sandbox Autoconfig. Which means we have not had this ride "the trains". The way it stands now, once it's done, it can't be turned off. We should use a pref to turn it on for a release or two just in case (similar to what we did with extension signing). Putting this behind a pref, default on is the low risk way to get land sandboxing autoconfig in 62. * after a couple of Releases nothing major has happened, we can remove the pref. * If something goes wrong, it won't require a dot release to flip the pref to disable the sandboxing.
Assignee | ||
Comment 1•5 years ago
|
||
Simple change for the default and then display a deprecation message if parsing fails. We're like to get an enterprise release notes page we can link to.
Assignee | ||
Comment 2•5 years ago
|
||
Comment 3•5 years ago
|
||
Comment on attachment 8998016 [details] Bug 1479857 - Use pref for Autoconfig on release, off by default Kris Maglione [:kmag] has approved the revision. https://phabricator.services.mozilla.com/D2801
Attachment #8998016 -
Flags: review+
Reporter | ||
Updated•5 years ago
|
Summary: Add a preference (default on) for autoconfig sanboxing for first 2 releases → Add a preference (default off) for autoconfig sanboxing for first release
Assignee | ||
Updated•5 years ago
|
Status: NEW → ASSIGNED
Marking as a blocker so we will make sure to land this on beta before release.
status-firefox62:
--- → affected
status-firefox63:
--- → affected
tracking-firefox62:
--- → blocking
Pushed by mozilla@kaply.com: https://hg.mozilla.org/integration/autoland/rev/68d89e639065 Use pref for Autoconfig on release, off by default r=kmag
Comment 7•5 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/68d89e639065
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla63
Assignee | ||
Comment 8•5 years ago
|
||
Comment on attachment 8998016 [details] Bug 1479857 - Use pref for Autoconfig on release, off by default Approval Request Comment [Feature/Bug causing the regression]: Use a pref to turn autoconfig off in beta/release [User impact if declined]: None [Is this code covered by automated tests?]: Yes [Has the fix been verified in Nightly?]: No. This is a beta change and QA is ready to verify. [Needs manual test from QE? If yes, steps to reproduce]: Yes, they have the information already (as part of test plan) [List of other uplifts needed for the feature/fix]: None [Is the change risky?]: Very low [Why is the change risky/not risky?]: Adds pref around already turned off feature. [String changes made/needed]:
Attachment #8998016 -
Flags: approval-mozilla-beta?
Updated•5 years ago
|
Severity: normal → major
Flags: qe-verify+
Comment on attachment 8998016 [details] Bug 1479857 - Use pref for Autoconfig on release, off by default Let's verify in beta; should land for this week's beta 19 build.
Attachment #8998016 -
Flags: approval-mozilla-beta? → approval-mozilla-beta+
![]() |
||
Comment 10•5 years ago
|
||
bugherderuplift |
https://hg.mozilla.org/releases/mozilla-beta/rev/0650cf336ae5
Comment 11•5 years ago
|
||
Backed out changeset 0650cf336ae5 (bug 1479857) for suspicion of causing talos tp6 and h2 failures. Backout: https://hg.mozilla.org/releases/mozilla-beta/rev/db5f926d5cdc05d01edcdf2d264fd50ca4ec6720 Push with failures: https://treeherder.mozilla.org/#/jobs?repo=mozilla-beta&revision=e8db9f7d2225366699c4c2c73d1d4ab465700253&filter-resultStatus=testfailed&filter-resultStatus=busted&filter-resultStatus=exception&selectedJob=194054391 Failure log: https://treeherder.mozilla.org/logviewer.html#?job_id=194054391&repo=mozilla-beta&lineNumber=1024
Flags: needinfo?(mozilla)
Assignee | ||
Comment 12•5 years ago
|
||
Was this definitely the reason for the failure? I don't understand how this could cause any of these failure. This code does nothing if there is no autoconfig file.
Flags: needinfo?(mozilla)
![]() |
||
Comment 13•5 years ago
|
||
Yes, the failures went away with the backout: https://treeherder.mozilla.org/#/jobs?repo=mozilla-beta&filter-resultStatus=testfailed&filter-resultStatus=busted&filter-resultStatus=exception&filter-resultStatus=retry&filter-resultStatus=usercancel&filter-resultStatus=runnable&filter-resultStatus=success&tochange=db5f926d5cdc05d01edcdf2d264fd50ca4ec6720&filter-searchStr=tp6&fromchange=e911e6f9571b0a31d819bf2a1aa019d166210ab4
![]() |
||
Comment 14•5 years ago
|
||
This relanded: https://hg.mozilla.org/releases/mozilla-beta/rev/b1c0bbcc4195b059ec7dc9e1219b63a08a78c5af And got backed out again for the same issue: https://hg.mozilla.org/releases/mozilla-beta/rev/7aca2ef5be9ca8d696db98dd6fd915ebaf69b707
Flags: needinfo?(mozilla)
Assignee | ||
Comment 15•5 years ago
|
||
That's really confusing. It didn't happen in a try build. https://treeherder.mozilla.org/#/jobs?repo=try&revision=ad72156639084ad03ffe5ac9d25f6fe368e46f52 I'll run some local tests.
Flags: needinfo?(mozilla)
Comment 16•5 years ago
|
||
Wow, Talos depends on non-sandboxed autoconfig: https://dxr.mozilla.org/mozilla-central/rev/4e56a2f51ad739ca52046723448f3129a58f1666/testing/talos/talos/mitmproxy/mitmproxy.py#59 https://dxr.mozilla.org/mozilla-central/rev/4e56a2f51ad739ca52046723448f3129a58f1666/testing/talos/talos/mitmproxy/mitmproxy.py#28 So it will not happen on Nightly nor local builds.
Assignee | ||
Comment 17•5 years ago
|
||
> Wow, Talos depends on non-sandboxed autoconfig:
Thank you for finding this!
It's a good thing we found this now. This would have broke when we moved to release and we would have had no idea why.
For now, I'm going to add the sandbox pref, but we have to find a solution to this before we remove the pref.
Assignee | ||
Comment 18•5 years ago
|
||
This is the talos fix.
![]() |
||
Comment 19•5 years ago
|
||
bugherderuplift |
https://hg.mozilla.org/releases/mozilla-beta/rev/4df089dd0c1a
Comment 20•5 years ago
|
||
Hi,the patch needs to land else it will fail when the code moves to beta. Central as Beta: https://treeherder.mozilla.org/#/jobs?repo=try&revision=587dd308797a67580077316ce6da6be6a9afbff9&filter-resultStatus=testfailed&filter-resultStatus=busted&filter-resultStatus=exception&filter-resultStatus=usercancel&filter-resultStatus=runnable&selectedJob=194299043&filter-searchStr=tp6
Flags: needinfo?(mozilla)
Comment hidden (Intermittent Failures Robot) |
Assignee | ||
Comment 22•5 years ago
|
||
Comment 23•5 years ago
|
||
Pushed by rvandermeulen@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/0d5e2c4f446b Enable Autoconfig sandbox for Talos. r=RyanVM
Comment 24•5 years ago
|
||
Comment on attachment 9002840 [details] Bug 1479857 - Enable Autoconfig sandbox for Talos. Ryan VanderMeulen [:RyanVM] has approved the revision.
Attachment #9002840 -
Flags: review+
Comment 25•5 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/0d5e2c4f446b
Comment hidden (Intermittent Failures Robot) |
Comment 28•5 years ago
|
||
This bug was covered by the overall manual testing efforts invested in the Sandbox AutoConfig feature. The uplift didn't break any existing or implemented functionality. Marking this as verified fixed using Fx 62.0b20 on Windows 10 x64 and macOS 10.13.4.
Reporter | ||
Updated•5 years ago
|
Summary: Add a preference (default off) for autoconfig sanboxing for first release → Add a preference (default on) for autoconfig sanboxing for first release
You need to log in
before you can comment on or make changes to this bug.
Description
•