Skip to content

[Fuzz task steps duration] Change corpus sync duration metric - #5579

Open
brun0-matheus wants to merge 1 commit into
bruno.real-bad-build-time-metricfrom
bruno.change-sync-corpus-metric
Open

brun0-matheus wants to merge 1 commit into
bruno.real-bad-build-time-metricfrom
bruno.change-sync-corpus-metric

Conversation

@brun0-matheus

Copy link
Copy Markdown
Contributor

Bug: b/581822025
Builds upon PR #5555.

Overview

The SYNC_CORPUS_TIME metric was introduced in PR #5530, but it's better to make it use the FUZZ_TASK_STEPS_DURATION metric, to keep it consistent with the other steps tracked in this PR stack.

Since FUZZ_TASK_STEPS_DURATION only tracks the time in the fuzz_task main, we can drop the preprocessing corpus_sync measurement.

Changes

  • Remove SYNC_CORPUS_TIME metric in monitoring_metrics.py.
  • Remove TimeMetricTracker, since TimeStatTracker does the same thing but with additional features.
  • Add new columns in JobRun.steps_duration: corpus_download and corpus_upload.
  • Change unittests to check for FUZZ_TASK_STEPS_DURATION instead of SYNC_CORPUS_TIME, and remove unittests related to deleted code.

Tests

Unittests added. When the tests in the dev environment finish, I will update this comment with evidence.

@brun0-matheus brun0-matheus self-assigned this Nov 4, 2026
@brun0-matheus
brun0-matheus requested a review from a team as a code owner November 4, 2026 16:44
@brun0-matheus
brun0-matheus added this pull request to stack #5565 November 4, 2026 16:44
@brun0-matheus
brun0-matheus force-pushed the bruno.change-sync-corpus-metric branch from 391e5c3 to 7ccf6a1 Compare November 4, 2026 19:07

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant