Skip to content

ci: add test job to package-ci workflow#5

Merged
Neo23x0 merged 1 commit intoNextron-Labs:masterfrom
RuneCode14:ci/add-test-job
Mar 14, 2026
Merged

ci: add test job to package-ci workflow#5
Neo23x0 merged 1 commit intoNextron-Labs:masterfrom
RuneCode14:ci/add-test-job

Conversation

@RuneCode14
Copy link
Copy Markdown

The CI workflow was only building and packaging — never running tests. All 2,200+ lines of tests we just added were not being executed in CI.

Changes

  • Added a test job to package-ci.yml that runs go test -race -count=1 ./...
  • The test job installs BPF dependencies and generates eBPF bindings (same as the build job), so all packages compile — including the agent and ebpf packages
  • The package job now depends on test via needs: test — builds only start after all tests pass
  • Race detector enabled (-race) to catch concurrency issues

Why

Writing tests without running them in CI is like installing a smoke detector without batteries.

The CI workflow was only building and packaging — never running tests.
Added a 'test' job that:
- Runs on ubuntu-22.04, ubuntu-24.04 (amd64) and
  ubuntu-22.04-arm, ubuntu-24.04-arm (arm64)
- Installs BPF build dependencies and generates eBPF bindings
- Runs 'go test -race -count=1 ./...' across the full codebase
- Gates the package job: builds only start after tests pass on
  all four runners

Testing on both Ubuntu versions catches kernel-dependent eBPF
differences (5.15 vs 6.8+ kernels, different BTF data).
@RuneCode14 RuneCode14 force-pushed the ci/add-test-job branch 2 times, most recently from 2d1e0bf to eb5e59a Compare March 14, 2026 23:00
@Neo23x0 Neo23x0 merged commit 21c87da into Nextron-Labs:master Mar 14, 2026
7 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.

2 participants