Skip to content

fix(28): unbreak fast-suite CI (google-cloud dev deps + R2/satellite test guards)#97

Merged
helloiamvu merged 1 commit into
mainfrom
hotfix/fast-suite-test-deps
Jul 3, 2026
Merged

fix(28): unbreak fast-suite CI (google-cloud dev deps + R2/satellite test guards)#97
helloiamvu merged 1 commit into
mainfrom
hotfix/fast-suite-test-deps

Conversation

@helloiamvu

Copy link
Copy Markdown
Member

Hotfix for main — PR #96 was admin-merged before CI finished and reddened the fast-suite: the new services/earnings/jobs tests need Cloud Run deploy deps that uv sync --all-packages doesn't install (ModuleNotFoundError: google/boto3).

Fix (verified in a CI-mimicking venv: 3925 passed, 466 skipped, 0 failed):

  • Add google-cloud-pubsub + google-cloud-storage to the workspace dev group (same pattern as fastapi) so capture/STT/handoff job tests import the google.cloud namespace.
  • Do not add boto3 — it's the [satellite]-extra marker several satellite tests key their skip-guard on; adding it would make them falsely run and crash on absent s3fs/xarray.
  • Guard the serving R2-read tests + test_roster's resolution test on the extra (like test_cli_roster).
  • Fold in the batch.tf GOES-footprint note that missed Phase 28: deploy-runtime layer (Dockerfiles, deploy workflows, deploy IAM, /healthz, lifespan, backfill roster) #96's merge commit.

🤖 Generated with Claude Code

…ps; guard R2/satellite tests

PR #96 added services/earnings/jobs tests that need the Cloud Run deploy deps, but
the CI fast-suite runs `uv sync --all-packages` (no optional extras), so they
errored (ModuleNotFoundError: google / boto3) and reddened main. Root cause: those
deploy deps aren't installed in the base workspace.

Fixes (verified against the exact CI env — boto3 pruned, google.cloud present:
3925 passed, 466 skipped, 0 failed):
- Add google-cloud-pubsub + google-cloud-storage to the workspace dev group (same
  pattern as fastapi in Phase 27) so the capture/STT/handoff job tests import the
  `google.cloud` namespace (clients are still faked).
- Do NOT add boto3: it is the [satellite]-extra marker several satellite tests key
  their skip-guard on (test_satellite_leakage), so adding it would make those
  guards falsely fire and crash on the still-absent s3fs/xarray.
- Guard the serving R2-read tests (test_serving_r2_read) on boto3 — they exercise
  the S3-compat botocore error paths, so they run in the satellite/deploy lanes.
- Guard test_roster's station-resolution test (imports satellite/_backfill →
  _goes_s3 → boto3/s3fs/xarray) on the [satellite] extra, like test_cli_roster.
- Fold in the batch.tf GOES-footprint note that missed the merge commit (staging
  race).

Recovery from an admin-merge of #96 whose CI hadn't finished (my error) — this time
verified green in a CI-mimicking venv before pushing.
@github-actions

github-actions Bot commented Jul 3, 2026

Copy link
Copy Markdown

Parity ticket gate: PASSED

parity-ticket-check: PR does not touch parity-trigger surface; gate skipped.

See CROSS-SDK-SYNC.md §2 for the workflow.

@helloiamvu helloiamvu merged commit b57071d into main Jul 3, 2026
19 checks passed
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