Telemetry Frequency incorrectly affects before and after fuzzing telemetry collection

Open Beginner friendly
#1,790 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
68/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
cpp
Domain
testing-qa

Research direction

Start in centipede/environment.cc at DumpCorpusTelemetryInThisShard and compare its telemetry_frequency handling with DumpRUsageTelemetryInThisShard. Confirm the flag behavior described in centipede/centipede_flags.inc, then ensure corpus telemetry is dumped for before- and after-fuzzing collection when telemetry_frequency is zero.

Written by the indexing model from the issue text.

Description

Per centipede_flags.inc, before-fuzzing and after-fuzzing telemetry data should always be dumped, regardless of the value of the telemetry_frequency flag. However, right now, this is only partially true. Corpus telemetry is not dumped if telemetry_frequency is zero, while RUsage telemetry is.

This occurs because DumpCorpusTelemetryInThisShard checks telemetry_frequency and requires it to be non-zero, while DumpRUsageTelemetryInThisShard does not make this check.

DumpCorpusTelemetryInThisShard should be updated to remove the requirement that telemetry_frequency is non-zero.

Dominant language
C++
Stars
1.1k
Forks
137
Avg merge
3d 6h
Merged PRs (30d)
22

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from google/fuzztest

All issues in google/fuzztest

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.