Link: https://github.com/SQLMesh/sqlmesh/actions/runs/32525879293/job/96916106498
AI Notes
Synopsis
time_machine freezes the process clock to 2023. Google service-account JWTs use that clock for iat/exp, so GCP rejects the token (invalid_grant / “reasonable timeframe”). The test never reaches real BigQuery auth with a valid token. Same pattern will break other cloud engines that mint time-based credentials.
Adjust
Failing now (on main):
tests/core/engine_adapter/integration/test_integration_bigquery.py
test_run_correlation_id_in_job_labels — remove @time_machine.travel("2023-01-08 …") and the inner 2023-01-09 travel; drive intervals with execution_time / start / end instead
Link: https://github.com/SQLMesh/sqlmesh/actions/runs/32525879293/job/96916106498
AI Notes
Synopsis
time_machinefreezes the process clock to 2023. Google service-account JWTs use that clock foriat/exp, so GCP rejects the token (invalid_grant/ “reasonable timeframe”). The test never reaches real BigQuery auth with a valid token. Same pattern will break other cloud engines that mint time-based credentials.Adjust
Failing now (on main):
tests/core/engine_adapter/integration/test_integration_bigquery.pytest_run_correlation_id_in_job_labels— remove@time_machine.travel("2023-01-08 …")and the inner2023-01-09travel; drive intervals withexecution_time/start/endinstead