Skip to content

[ci-mgmt verification] Test full Go cache workflows - #6620

Closed
corymhall wants to merge 1 commit into
masterfrom
ci/full-go-cache-verification
Closed

[ci-mgmt verification] Test full Go cache workflows#6620
corymhall wants to merge 1 commit into
masterfrom
ci/full-go-cache-verification

Conversation

@corymhall

@corymhall corymhall commented Aug 24, 2026

Copy link
Copy Markdown
Member

Summary

  • Problem: ci-mgmt test-provider fixtures validate generated YAML but do not execute the generated workflows.
  • Change: opt this branch into the candidate fullGoCache configuration and regenerate the Pulumi AWS workflows from ci-mgmt commit 1d89ba650.
  • Related issue/PR: temporary verification for the ci-mgmt full Go cache change; this PR is not intended to merge.

Change Type

  • Provider logic only (provider/)
  • Schema or mapping change (may require SDK regeneration)
  • Upstream or patch pipeline change (upstream/, patches/, scripts/upstream.sh)
  • CI workflow source change (.ci-mgmt.yaml)

Carried Upstream Patch

Not applicable.

Validation Evidence

  • make lint — not applicable; provider code is unchanged
  • make test_provider — not run locally; this PR exists to exercise provider CI
  • If schema-affecting: make schema — not applicable
  • If schema-affecting: make build_sdks — not applicable
  • If CI source changed: generated with the candidate provider-ci binary from ci-mgmt commit 1d89ba650
  • ci-mgmt's pinned actionlint passed for all changed generated workflows

Command output snippets

candidate provider-ci generation: passed
actionlint on changed generated workflows: passed
composite action YAML parsing: passed

A whole-repository actionlint run is currently blocked by the unchanged top-level description key in .github/workflows/aws-upstream-tests.yml.

Risk

  • Blast radius: GitHub Actions cache restore and save behavior in generated provider, SDK, schema, test, coverage, and release-verification jobs.
  • Edge cases: pull-request CI exercises the PR workflows but does not exercise push- or tag-only release paths.

Rollback

  • Revert plan: close this temporary PR after its checks, including Sentinel, finish.
  • Follow-up cleanup: delete the verification branch after recording the check results in the ci-mgmt PR.

@github-actions

Copy link
Copy Markdown
Contributor

Does the PR have any schema changes?

Generated by schema-tools v0.8.1.

Looking good! No breaking changes found.
No new resources/functions/types.

Maintainer note: consult the runbook for dealing with any breaking changes.

@codecov

codecov Bot commented Aug 24, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 15.83%. Comparing base (90c2617) to head (8862466).
⚠️ Report is 2 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #6620      +/-   ##
==========================================
- Coverage   15.83%   15.83%   -0.01%     
==========================================
  Files         377      377              
  Lines       92888    92895       +7     
==========================================
- Hits        14712    14706       -6     
- Misses      78154    78167      +13     
  Partials       22       22              

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Summary:
- opt pulumi-aws into the candidate full Go cache configuration
- regenerate workflows with the ci-mgmt feature branch

Rationale:
- exercise the candidate cache strategy in a real provider CI run before
  the ci-mgmt change is merged

Tests:
- candidate provider-ci generation
- actionlint on changed generated workflows
@corymhall
corymhall force-pushed the ci/full-go-cache-verification branch from ce96082 to 8862466 Compare August 25, 2026 09:16
@corymhall

Copy link
Copy Markdown
Member Author

Warm-cache verification completed successfully in run 32831022645.

Measurement Initial run Corrected warm run
Total workflow 70m15s 45m34s
Prerequisites 18m23s 6m30s
Linux provider 23m46s 6m46s
Windows provider 23m06s 4m49s
Provider tests 16m15s 7m04s
Slowest integration shard 27m19s 24m03s

The corrected run had no Go module-cache extraction failures. All nonzero test shards used restore-only mode, and only shard 0 saved the integration-test cache. All required checks, including Sentinel, passed.

@corymhall corymhall closed this Aug 25, 2026
@corymhall
corymhall deleted the ci/full-go-cache-verification branch August 25, 2026 10:02
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