Skip to content

test(integration): fix stale RunUp call (Integration workflow red on main) - #271

Merged
zheli merged 1 commit into
mainfrom
fix/integration-test-runup
Jul 12, 2026
Merged

test(integration): fix stale RunUp call (Integration workflow red on main)#271
zheli merged 1 commit into
mainfrom
fix/integration-test-runup

Conversation

@srikanth-bitdynamics

Copy link
Copy Markdown
Collaborator

Problem

The Integration workflow fails to build on main:
internal/localnet/integration_test.go:68: too many arguments in call to RunUp.

RunUp was refactored to take a Progress (RunUp(ctx, prog, opts)), but the
build-tagged integration_test.go still calls the old
RunUp(ctx, os.Stdout, os.Stderr, opts). Normal go test ./... doesn't compile
//go:build integration files, so it rotted undetected.

Fix

Wrap stdout/stderr in NewTextProgress — exactly what the CLI passes to RunUp.
Verified: go vet -tags integration ./... and go build -tags integration ./...
now pass.

One of two independent CI breakages on main found while validating the
observability + remove work (the other is the download-artifact pin, #270).

RunUp was refactored to take a Progress (RunUp(ctx, prog, opts)), but the
build-tagged integration_test.go still passed (ctx, os.Stdout, os.Stderr, opts).
Normal `go test` doesn't compile integration-tagged files, so it rotted
undetected — the Integration workflow has been red on main with
'too many arguments in call to RunUp'. Wrap stdout/stderr in NewTextProgress,
matching the CLI's RunUp call.
@zheli
zheli merged commit ce00faa into main Jul 12, 2026
4 checks passed
@zheli
zheli deleted the fix/integration-test-runup branch July 12, 2026 21:03
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.

2 participants