New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 633332 link

Starred by 1 user
Status: Fixed
Owner:
qyears...@chromium.org
Closed: Aug 2016
Cc:
█ tanin@chromium.org
st...@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug

Blocking:
issue 616183



Sign in to add a comment

Telemetry fuzzer does not work

Project Member Reported by infe...@chromium.org, Aug 1 2016 
https://cluster-fuzz.appspot.com/fuzzerlog?fuzzer=qyearsley_telemetry

clusterfuzz-linux-0490: Return code(0)
python /mnt/scratch0/clusterfuzz/slave-bot/inputs/fuzzers/qyearsley_telemetry/run.py --input_dir=/mnt/scratch0/clusterfuzz/slave-bot/inputs/fuzzers/qyearsley_telemetry/telemetry_data --output_dir=/mnt/scratch0/clusterfuzz/slave-bot/inputs/fuzzer-testcases --no_of_files=20
DEBUG:root:Running $I/fuzzers/qyearsley_telemetry/telemetry_data/telemetry/run_benchmark list --browser=system --json-output-file=$I/fuzzer-testcases/benchmark-list.json.
DEBUG:root:Reading benchmark list JSON file $I/fuzzer-testcases/benchmark-list.json.
ERROR:root:No benchmarks obtained from run_benchmark.

Comment 1 by qyears...@chromium.org, Aug 1 2016 

This fuzzer is not actually being used for anything - it can be deleted now.

Note, setting it up was an experiment to see whether that would be a good approach to basically integration-testing Telemetry and Chrome and making sure that new versions of Chrome don't have bugs that cause instability in the performance tests.

Comment 2 by aarya@google.com, Aug 1 2016

Status: Fixed (was: Assigned)
Ok we have it in https://chrome-internal.googlesource.com/chrome/tools/clusterfuzz-data/+/master/fuzzers/telemetry_fuzzer/ already, deleted fuzzer.

Comment 3 by qyears...@chromium.org, Aug 1 2016 

Thanks!
►

Sign in to add a comment