#29489: Set up automated local testing environment for Snowflake -----------------------------------+--------------------------- Reporter: cohosh | Owner: cohosh Type: task | Status: assigned Priority: Medium | Milestone: Component: Obfuscation/Snowflake | Version: Severity: Normal | Resolution: Keywords: | Actual Points: Parent ID: #29259 | Points: Reviewer: | Sponsor: Sponsor19 -----------------------------------+---------------------------
Comment (by cohosh): > Reproduce the proxy-go deadlocking bug #25688 It might be useful to spawn several clients in the docker container for testing and bug-reproduction purposes. At the moment, I am using the torrc-localhost file for the torrc configuration on the client side, but we can have only one client bound to each local socks port at a time, and tor processes cannot share a datadir. What I have done manually so far is copy the client executable and torrc file to different directories and added the SocksPort line to each new torrc file with a different port number per client instance. I'm thinking of expanding the script.sh script to specify a --num-clients option that will do this copying SockPort configuration automatically (we don't even really need different directories for each client, just different socks ports and datadir's). While I'm at it, I will probably include a --build option to the script that will only compile the code if needed. Since we are mounting the git repository from the host directly, this does not need to be done each time the container is started. -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/29489#comment:5> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online
_______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs