Skip to content

ci: add minimal build+vet workflow + fix two test build errors#3

Merged
hanzo-dev merged 1 commit into
mainfrom
ci/add-build-vet-workflow
May 17, 2026
Merged

ci: add minimal build+vet workflow + fix two test build errors#3
hanzo-dev merged 1 commit into
mainfrom
ci/add-build-vet-workflow

Conversation

@hanzo-dev
Copy link
Copy Markdown
Member

Summary

  • Add .github/workflows/ci.yml so this new repo has a CI signal (build + vet on packages whose tests compile)
  • Fix unused context import in x/txs/operation_test.go
  • Extend testValidatorState stub in x/txs/executor/semantic_verifier_test.go to satisfy current luxfi/validators.State surface

Tests in x/txs/executor still panic at runtime (secp256k1fx.Initialize on nil codec registry) — pre-existing in absorbed code, separate fix.

Test plan

  • go build ./... clean
  • go vet ./... clean on the gated packages

- New .github/workflows/ci.yml runs `go build ./...` and `go vet` on the
  packages whose tests currently compile (skips p/block/* and
  x/txs/executor — those test stubs were absorbed from luxfi/proto and
  need rework to satisfy current luxfi/validators.State and
  github.com/luxfi/protocol/p/block/executor backend{} shape).
- Drop unused context import in x/txs/operation_test.go
- Extend semantic_verifier_test.go testValidatorState stub to satisfy
  the full luxfi/validators.State surface (add GetCurrentValidators,
  GetWarpValidatorSet, GetWarpValidatorSets; fix GetValidatorSet
  signature to take context + return validators.GetValidatorOutput).

Tests in x/txs/executor still panic at runtime (secp256k1fx.Initialize
on nil codec registry — pre-existing, separate fix). Build is green;
ship the workflow so we have a baseline.
@hanzo-dev hanzo-dev merged commit 23e31f9 into main May 17, 2026
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