* fix(test): keep TestDoltServer_StartStop_UnixSocket's socket path short
t.TempDir() nests the test's name, which alone pushes the socket path past
the 104-byte sun_path guard under any TMPDIR longer than /tmp: the Bazel test
wrapper's per-process TMPDIR (114 bytes) and macOS's /var/folders/... both
silently skipped the test that main.yml's integration job runs. Put the
socket in a short os.MkdirTemp directory instead.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* fix(testutil): let SubprocessRunner build with a declared go command
SubprocessRunner.Build ran `go` from PATH. Under Bazel there is no Go
toolchain on PATH, so //internal/testutil/integration's
TestBuildErrorIsMaskedByChmod failed there. BEADS_TEST_GO_BINARY, resolved
like any other runfile, now names the go command; unset, it is still `go`.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* feat(bazel): integration-tag lane, --config=integration
main.yml's "Main Linux integration packages (N/6)" and "cmd/bd (N/8)" jobs
(and nightly's Full Test Suite) run every package with
-race -tags=integration,gms_pure_go, no -short and BEADS_TEST_SKIP=dolt.
Bazel never built the 55 `//go:build integration` files: gazelle drops a
file whose constraint names a tag it does not know.
- Root `gazelle:build_tags gms_pure_go,integration`: gazelle now lists the
integration files in srcs and their imports in deps, and generates
//internal/testutil/integration (integration files only). rules_go filters
those files out of every other build, so --config=ci runs what it ran.
- --config=integration sets the tag for the whole build, like `go test
-tags`, plus the jobs' race, BEADS_TEST_SKIP=dolt, -test.parallel=4 and a
1200s/19m timeout pair (rbe-west's action limit; the jobs pass 30m). The
same variants as PR core stay out (requires-docker, embedded, manual), so
`bazel test //... --config=integration` runs the union of the 14 shards.
A per-target gotags variant would not save the compile (gotags transitions
the whole dep graph) and would need a second, duplicated target per package
plus a tag to drop the plain one from this lane.
- //internal/testutil/integration:integration_test gets the pinned SDK's go
for SubprocessRunner's `go test -c`.
- TestBazelIntegrationLaneMatchesMainWorkflow pins test:integration to
main.yml's tags/race/BEADS_TEST_SKIP and gazelle's build_tags to a superset
of the tags; bazel.yml's `make bazel-sync` diff already fails when a file
gains the integration tag without a BUILD sync.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* build(bazel): sync scripts BUILD for upgrade_smoke_loop_test.go
make bazel-sync on current main adds the test file #6398 added.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* fix(bazel): derive the integration lane's tag exclusions from PR core's
After main added the dolt-server tag, test:integration's filter still
selected those targets, and 5 of them fail under BEADS_TEST_SKIP=dolt. The
filter now excludes dolt-server, and the policy test no longer pins one
string: bazelPRCoreExcludedTags (kept equal to the taxonomy entries that say
"excluded from --config=prcore/ci") is the list both lanes check, the
integration lane minus the tags it runs. Every --test_tag_filters in the
lane or a config expanding it must exclude them, and no -test.short,
-test.skip, -test.run or --test_filter may reach it.
New tag integration-only for //internal/testutil/fixtures:fixtures_test and
//internal/testutil/integration:integration_test, whose tests are all
`//go:build integration`: --config=prcore/ci excludes them instead of
running two empty targets; --config=integration runs them. The .bazelrc
notes that ci and integration share bazel-testlogs.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* docs(bazel): note shared testlogs and dolt_test's subprocess build
bazel.yml's equivalence step reads bazel-testlogs, which --config=integration
shares with --config=ci, so a job running both lanes must check each right
after its own run. //internal/storage/dolt:dolt_test's SubprocessRunner tests
need a real `go test -c` with a module cache; they stay skipped under the
lane's BEADS_TEST_SKIP=dolt, so the target gets no go SDK data.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Gas City Adopt-PR <adopt-pr@gascity.local>
Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>