f84dbf5c66
The Forgejo runner doesn't expose /var/run/docker.sock, so anything relying on testcontainers-go panicked with "Cannot connect to the Docker daemon". This caused internal/testutils, tests/transactions and tests/integration to fail wholesale, plus internal/handlers to hit the 5min hard timeout while waiting for container startup. Approach (least invasive): - testutils.GetTestContainerDB short-circuits when VEZA_SKIP_INTEGRATION=1 is set, returning a sentinel error immediately instead of attempting three retries against a missing Docker socket. - Add testutils.SkipIfNoIntegration helper for granular per-test skips. - Add TestMain to internal/testutils, tests/transactions and tests/integration packages that os.Exit(0) when the env var is set, so the entire integration-only package is silently skipped in CI. - Wire the helper into the three setupTestDB* functions in tests/transactions/ for local runs (where TestMain doesn't fire when using -run on individual tests). Local nightly runs / dev workstations leave VEZA_SKIP_INTEGRATION unset and exercise the full suite against testcontainers as before.
21 lines
638 B
Go
21 lines
638 B
Go
package testutils
|
|
|
|
import (
|
|
"fmt"
|
|
"os"
|
|
"testing"
|
|
)
|
|
|
|
// TestMain skips the entire testutils test suite when integration prerequisites
|
|
// (Docker daemon for testcontainers) are unavailable. The testutils package's own
|
|
// tests exercise SetupTestDB and CleanupDatabaseWithOptions which require a real
|
|
// Postgres container, so there is nothing meaningful to run without it.
|
|
//
|
|
// CI sets VEZA_SKIP_INTEGRATION=1 on runners without /var/run/docker.sock.
|
|
func TestMain(m *testing.M) {
|
|
if os.Getenv("VEZA_SKIP_INTEGRATION") == "1" {
|
|
fmt.Println("testutils: skipping package (VEZA_SKIP_INTEGRATION=1)")
|
|
os.Exit(0)
|
|
}
|
|
os.Exit(m.Run())
|
|
}
|