Repository navigation
Conversation
…per job The wpt-consumer job logs a WARNING for every test that uses a moved web-features key, for every WPT run it processes. Every run is scored against the same WEB_FEATURES manifest, so the same lines repeat thousands of times per execution. Today WPT still tags 1,069 tests with `masonry` (moved to `grid-lanes`), which produces ~12M identical lines per execution. Keep the existing log line exactly as it is, but only emit it for the first 5 migrations in a job execution, and log the total count once when the job finishes. The migration itself, the conflict error, scoring and the data written to Spanner are unchanged. Testing: added TestMigrateWebFeaturesToMovedFeaturesLogsFirstMigrationsOnly. `go vet ./...` and `go test ./...` pass for the wpt_consumer module.
neilv-g
force-pushed
the
fix/wpt-consumer-log-moved-feature-once
branch
from
November 20, 2026 13:52
7bf4be6 to
b13c65a
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The wpt-consumer job logs a WARNING for every test that uses a moved web-features key, for every WPT run it processes. WPT still tags 1,069 tests with
masonry, which web-features has moved togrid-lanes. Each execution re-scores all ~11.1k WPT runs from the last 30 days against the same WEB_FEATURES manifest, so it logs the same 1,069 lines about 11k times: ~12M identical lines per execution and ~47M per day, in both staging and prod.Cost
That's
$1,230/month ($15k/year) for one repeated warning.Change
Impact
16 GiB prod), so Cloud Logging cost for these projects drops from **$1,230/month to ~$0**.Related: web-platform-tests/wpt#65511 updates the WPT metadata from
masonrytogrid-lanes, which removes the need for this migration entirely.Testing
Added
TestMigrateWebFeaturesToMovedFeaturesLogsFirstMigrationsOnly(7 migrations: all 7 are counted, only 5 are logged).go vet ./...andgo test ./...pass for the wpt_consumer module.