Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: google/clusterfuzz
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: master
Choose a base ref
...
head repository: google/clusterfuzz
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: dev
Choose a head ref
Checking mergeability… Don’t worry, you can still create the pull request.
  • 3 commits
  • 5 files changed
  • 3 contributors

Commits on May 13, 2026

  1. Try to fix butler deploy by setting CLOUDSDK_PYTHON

    @ViniciustCosta @dylanjew
    ViniciustCosta authored and dylanjew committed May 13, 2026
    Configuration menu
    Copy the full SHA
    68016ff View commit details
    Browse the repository at this point in the history

  2. retrieve job info from env instead of datastore in uworkers

    @PauloVLB @dylanjew
    PauloVLB authored and dylanjew committed May 13, 2026
    Configuration menu
    Copy the full SHA
    d830ce5 View commit details
    Browse the repository at this point in the history

Commits on May 15, 2026

  1. Replace INTERVAL duration fields with DOUBLE duration_seconds 

    F1 doesn't support INTERVAL types natively (b/213368390). This PR
replaces the INTERVAL duration fields with DOUBLE duration_seconds.

### Rollout
I plan to just drop the existing cluster-fuzz.fuzzer_stats.daily_stats table after this is deployed and rerunning the job to backfill the data. Since there are no consumers of this data yet, this seems simpler than doing a dual write + alter table drop column, then changing the job load to stop including the old rows.

The concern I had is that a BigQuery load without the old
rows would fail, so dropping the table after this is deployed and then
backfilling seems like a simpler approach.

### Testing
I verified the SQL query by running it in BigQuery against the
cluster-fuzz.fuzzer_stats.daily_stats table.
    @dylanjew
    dylanjew committed May 15, 2026
    Configuration menu
    Copy the full SHA
    f1d0b12 View commit details
    Browse the repository at this point in the history
Loading