novox/mesh-controller
Archived
9
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Plan a controller merge in the worker-of order in the three-kinds test
mesh/merge-gate pass: builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step; every machine composes with the change as it…
Details
mesh/repo-check pass: its merge-check.sh passed
Details
mesh/delivery delivered
Details

Browse Source 
The test's fixture had no worker-of edge and expected the builder first,
then the controller and the proxy together: the order before hq issue 206.
Since then the build seat's holder follows the controller that defines its
worker, and every controller merge plans controller, builder, proxy in
three tiers. The fixture now carries the edge and the test that order.
This commit is contained in:
jochen
2026-10-08 22:22:24 +02:00
parent add807f034
commit 758537dd4e
2 changed files with 12 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
cmd/mesh-controller/planner_rules_test.go
+2 -3
View File
@@ -259,9 +259,8 @@ func TestASharedRepositoryMovesWhatPackagesItAsItDoesToday(t *testing.T) {
paths []string
want string
}{
// The live three-tier plan of 2026-10-08 (issue 338). It is also the worker-of order (issue 206)
// that TestAMergeIsPlannedInTiersAlongTheThreeKindsOfDependency's controller case predates: that
// fixture has no worker-of edge and expects the builder first, then the controller and the proxy.
// The live three-tier plan of 2026-10-08 (issue 338), in the worker-of order (issue 206) that
// TestAMergeIsPlannedInTiersAlongTheThreeKindsOfDependency's controller case holds too.
{"a README of the controller's repository moves all three, in three tiers", "mesh-controller",
[]string{"README.md"}, "mesh-controller | build-agent | route-proxy"},
{"the controller's own code: the same", "mesh-controller",