It has been our policy [1] to discourage builds/tests run in automation
from relying on resources outside of the build network, to avoid
non-deterministic failures across the board and to reduce noise in
performance tests.
As of Saturday, this policy will be enforced by the RelEng firewall
being set to Deny-All by default [2][3]. Recent traffic has been
monitored and used to create a set of Allow rules and/or remove existing
offenders - so there should be few surprises.
However, this means that new tests/frameworks added to the tree will
need to be designed with the expectation that they will not be able to
access outside of the build network - otherwise they'll fail when pushed
to Try/<integration repository of choice>.
Best wishes,
Ed
[1]
https://wiki.mozilla.org/Sheriffing/Job_Visibility_Policy#8.29_Must_avoid_patterns_known_to_cause_non_deterministic_failures
[2] https://bugzilla.mozilla.org/show_bug.cgi?id=617414
[3] https://bugzilla.mozilla.org/show_bug.cgi?id=812342
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
