ci: run complementary BVT group on multi-CN compose - #419
Merged
Conversation
fengttt
added a commit
that referenced
this pull request
Aug 14, 2026
… compose-based pessimistic BVT Upstream (#419-#423) landed two things this branch must integrate with: - The SCA job gained its own trusted actions/cache pipeline (module cache from matrixorigin/matrixone's sca-go-module-cache.yaml producer, native prerequisites keyed on compiler identity plus full native-input hashes, cached static-check tools). That mechanism subsumes this branch's SCA seed step — including the toolchain-ABI fingerprint this branch deliberately deferred — so the SCA seed is dropped, the nightly ci-builder publishes amd64 only (the arm64 leg existed solely for SCA), and the multi-arch manifest job goes away. - The pessimistic standalone BVT was rebuilt on the compose topology (its native launch build kept exceeding the job timeout). The old native-binary artifact consumer no longer applies; both BVT jobs now consume the shared build identically, assembling the runtime image from the artifact via Dockerfile.prebuilt with the same guarded fallback to the full in-docker build. The UT job keeps both the upstream Shanghai-proxy canary and this branch's cache seed; they are independent. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this PR does
Replaces the active native
LAUNCH, PESSIMISTICBVT deployment with the same multi-CN Docker Compose topology already used by the complementary Proxy BVT job.The two active BVT jobs now differ only in their complementary case-group assignment and the case-driven resource argument:
compose_group.launch_group.The existing generation/group manifests and distinct coverage artifact names are preserved, while the coverage merge contract now identifies the second deployment as
compose-pessimistic.Why
In matrixorigin/matrixone#27077 run 31663214904, the multi-CN Compose job completed successfully in about 42 minutes, while the native Launch job spent the full 75-minute job budget in
Build MatrixOneand was cancelled before executing any BVT case. Reusing the proven Compose path removes that native cold-build bottleneck.Lifecycle and failure handling
always()independently of BVT and coverage results.GOCOVERDIR.Validation
actionlinton both changed workflowsgroup=0/1manifests through the coverage mergejqpredicategit diff --checkRelated: matrixorigin/matrixone#27077