Closed
Bug 840919
Opened 11 years ago
Closed 11 years ago
Running unittest on ix-mn-w864-002 triggers Windows Firewall Alert for python.exe
Categories
(Infrastructure & Operations Graveyard :: CIDuty, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: cbook, Unassigned)
References
Details
Attachments
(2 files)
see Screenshot, a Firewall alert for python.exe was popping up when running tests on 864-002 So i guess we have to whitlist python also on the w864 maschines Dustin: So far i haven't clicked anything in this dialog to let you guys play - also seems to work anyway so far
Reporter | ||
Updated•11 years ago
|
OS: Mac OS X → Windows 8
Reporter | ||
Updated•11 years ago
|
Summary: Running unittest on ix-mn-w864-002 triggers Windows Firewall Alert → Running unittest on ix-mn-w864-002 triggers Windows Firewall Alert for python.exe
Comment 1•11 years ago
|
||
That's a different Python than we had added an exception for before. But it shouldn't be too hard.
Comment 2•11 years ago
|
||
We can add a new Python path, but that virtualenv is under the wrong parent directory. It should be under C:\slave. I've added that to bug 780050.
Reporter | ||
Comment 3•11 years ago
|
||
talked to armen on irc 06:15 < armenzg> Tomcat: http://hg.mozilla.org/build/mozharness/file/default/configs/unittests/win_unittest.py#l23 06:16 < armenzg> Tomcat: it might need some tweaking in here http://hg.mozilla.org/build/mozharness/file/f8b96235fb89/scripts/desktop_unittest.py#l154 06:17 < armenzg> turn "virtualenv_path" into a relative path
Comment 4•11 years ago
|
||
FTR, I'm not excited with paths being excepted. Those binaries come from extracting the test packages. As soon as developers decide to change how things get packaged the trees will go red. If you have a more general way to add the exceptions that would be great. If adding new exceptions is piece of cake and can be deployed easily I will be less concerned.
Comment 5•11 years ago
|
||
We can update the paths via GPO, so not a huge big deal.
With the introduction of the domain for testers adding new exceptions should be as easy as cut and paste. I can look at alternate methods that aren't as path reliant but it should be easy to add exceptions going forward.
Comment 7•11 years ago
|
||
(In reply to Q from comment #6) > With the introduction of the domain for testers adding new exceptions should > be as easy as cut and paste. I can look at alternate methods that aren't as > path reliant but it should be easy to add exceptions going forward. This is very helpful to know. No need to look for an alternative. Thanks!
Added GPO Tester_Firewall_Exceptions to the releng.ad.mozilla.com domain. It is linked to the "Tester" ous under machines. The relevant bug numbers are in the descriptions. Attached https://bugzilla.mozilla.org/attachment.cgi?id=714243 which is a policy result report so all rules are visible.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
Updated•6 years ago
|
Product: Release Engineering → Infrastructure & Operations
Updated•4 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•