Closed GoogleCodeExporter closed 9 years ago
What steps will reproduce the problem? 1. checkout revision 854 2. execute the commandline like this : ./namebench.py --no_gui --enable-censorship-checks --runs=3 -- output=~/public_html/namebench.html 208.67.222.222 208.67.220.220 195.241.77.55 195.241.77.58 194.109.6.66 194.109.9.99 3. Fail ! This is the error message : ./namebench.py --no_gui --enable-censorship-checks --runs=3 -- output=~/public_html/namebench.html 208.67.222.222 208.67.220.220 195.241.77.55 195.241.77.58 194.109.6.66 194.109.9.99 namebench 1.3-alpha-10 - best history source (automatic) on 2010-05-17 15:48:04.478859 threads=40/2 queries=250 runs=3 timeout=3.5 health_timeout=3.75 servers=11 --------------------------------------------------------------------------- --- - Reading Top 2,000 Websites (Alexa): data/alexa-top-2000-domains.txt (0.7MB) - Reading Cache Latency Test (100% hit): data/cache-hit.txt (0.1MB) - Reading Cache Latency Test (100% miss): data/cache-miss.txt (0.1MB) - Reading Cache Latency Test (50% hit, 50% miss): data/cache-mix.txt (0.1MB) - Skipping /home/jvhaarst/.config/google-chrome/Default/History (234d old) - Generating tests from Cache Latency Test (50% hit, 50% miss) (5000 records, selecting 250 automatic) - Selecting 250 out of 250 sanitized records (automatic mode). Traceback (most recent call last): File "./namebench.py", line 78, in <module> namebench.Execute() File "/home/jvhaarst/bin/scripts/namebench-read- only/libnamebench/cli.py", line 121, in Execute self.PrepareTestRecords() File "/home/jvhaarst/bin/scripts/namebench-read- only/libnamebench/base_ui.py", line 90, in PrepareTestRecords select_mode=self.options.select_mode) File "/home/jvhaarst/bin/scripts/namebench-read- only/libnamebench/data_sources.py", line 238, in GetTestsFromSource raise ValueError("No such final selection mode: %s" % select_mode) ValueError: No such final selection mode: automatic
Original issue reported on code.google.com by jvhaa...@gmail.com on 17 May 2010 at 1:52
jvhaa...@gmail.com
Fixed in r869
Original comment by helixblue on 19 May 2010 at 8:03
helixblue
Original issue reported on code.google.com by
jvhaa...@gmail.com
on 17 May 2010 at 1:52