In bug 1026970 we excluded tp4m from the initial MOZ_DISABLE_NONLOCAL_CONNECTIONS landing, since we were waiting on bug 1050769. That's seen been fixed, so let's push to try and if all green, remove the exclusion here: https://hg.mozilla.org/build/talos/file/253f980ee0cb/talos/ttest.py#l284
Try run which will warn on external connections (not crash): https://tbpl.mozilla.org/?tree=Try&rev=33891e5cb4e9
So I'm still getting external connections on the latest try run: ai.yimg.jp awaps.yandex.ru b.scorecardresearch.com b4.yahoo.co.jp b9.yahoo.co.jp core.ringleaderdigital.com g-ecx.images-amazon.com hw.baidu.com kiks.yandex.ru mc.yandex.ru wap.baidu.com www.google-analytics.com www.gstatic.com z-ecx.images-amazon.com However this is exactly the same list as bug 1050161 comment 1 - so it's like we're still using the same (old) zip. I'll reopen bug 1050769.
New try run after re-deploy in bug 1050769: remote: https://tbpl.mozilla.org/?tree=Try&rev=863127ae067d
Is now green on try, post bug 1050769 re-deploy :-) https://tbpl.mozilla.org/?tree=Try&rev=863127ae067d
Attachment #8475250 - Flags: review?(jmaher)
Attachment #8475250 - Flags: review?(jmaher) → review+
Comment on attachment 8475250 [details] [diff] [review] Define MOZ_DISABLE_NONLOCAL_CONNECTIONS for talos tp4m remote: https://hg.mozilla.org/build/talos/rev/08350b6caf6c
Status: ASSIGNED → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla34
You need to log in before you can comment on or make changes to this bug.