You would think the three would be equivalent: 1. PerfConfigurator -a ts -e `which firefox` --datazilla-url /home/jhammel/foo.json -o foo.yaml talos -n -d foo.yaml --develop 2. PerfConfigurator -a ts -e `which firefox` --datazilla-url /home/jhammel/foo.json -o foo.yaml --develop talos -n -d foo.yaml 3. talos -a ts -e `which firefox` --datazilla-url /home/jhammel/foo.json -o foo.yaml --develop In fact, 2 and 3 do work. 1. does not. 1. does not correct the URLs for the test, so you end up launching: DEBUG: command line: /home/jhammel/firefox/firefox -profile /tmp/tmpcWktzF/profile startup_test/startup_test.html?begin= This gives: """ The proxy server is refusing connections Firefox is configured to use a proxy server that is refusing connections. Check the proxy settings to make sure that they are correct. Contact your network administrator to make sure the proxy server is working. """ This should be made to work.

This also applies to --cycles and probably maybe everything else that is stored in tests

no more perf configurator.