On 10/14/2016 12:14 PM, Ross Berteig wrote:
....
I think this is the first build and test I've done since the Win10
Anniversary Update imposed itself on me, and certainly the first since
this week's patch Tuesday. Something made the Windows Firewall
fussier, and I had to reassure it during both test suite runs that
yes, it was ok to let fossil.exe do something. The prompt came a long
ways in to the suite, but I didn't check the prot file to see what
test had prompted it. If that behavior continues, it will make
launching a bunch of builds and walking away a lot less productive.
Advertising
The actual culprit was the new test_start_server function in tester.tcl,
which uses fossil server to run a server for a span of test cases to
test against. I noticed that fossil ui does not cause the firewall to
speak up, but fossil server does. This is because fossil ui explicitly
limits the server it runs to localhost, which is wise for a number of
reasons. We assume, that fossil server is intended to be seen more
widely, and do not make that restriction.
So the solution is for the test suite to prefer fossil server
--localhost which has the desired effect. I've checked in that change on
trunk, which works for me on my Windows test cases.
--
Ross Berteig r...@cheshireeng.com
Cheshire Engineering Corp. http://www.CheshireEng.com/
+1 626 303 1602
_______________________________________________
fossil-dev mailing list
fossil-dev@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/fossil-dev
