The chain lives on the bus alone: the store's tables of builds, rollouts and assignments are dropped (design 47 milestone 5, delivery 2: issues 1094, 1108, 1109, 1110, 1096, 1111)
#381
Merged
mesh-toolsmerged 13 commits from feat/chain-on-the-bus-d2 into main2026-10-18 12:30:43 +00:00
Milestone 5 of design 47, delivery 2. Delivery 1 (mesh-controller #379, mesh-catalog #357) put builds, rollouts and assignments on the bus and moved the rows; the fix of issue 1121 (#380, ADR 0427) laid builds out under their module. This delivery makes the bus the only source (ADR 0408 §2, §8).
It removes data: migration 0105 drops the store's tables of builds, rollouts with their tiers and assignments, and chain_moved. It refuses, in the same transaction and before any drop, while a pending assignment is waiting, applying, or raised and unanswered. Your Approve of this merge is your word on dropping them; every row was copied onto the bus by delivery 1 and is read back from there.
Issues 1094, 1108, 1109, 1110, 1096, 1111 (node.sent_builds copied onto the assignments' keys once and kept, a send empties its node's column; no table of the chain left after a live delivery; integration test of it).
Merged onto #380: the build layout runs at start under a layout.done marker, never overwrites a pointer and skips records already laid out (nothing reads the chain before the marker exists).
Reviewed-by: reviewer-1121@shanks at 7f074d9c94 (the merge onto #380; delivery 2 itself approved in round 3 at 4eeba8fb203255297c47b33b1315d8722c67476c; head 0b4cd46b only merges main, identical tree)
Milestone 5 of design 47, delivery 2. Delivery 1 (mesh-controller #379, mesh-catalog #357) put builds, rollouts and assignments on the bus and moved the rows; the fix of issue 1121 (#380, ADR 0427) laid builds out under their module. This delivery makes the bus the only source (ADR 0408 §2, §8).
**It removes data: migration 0105 drops the store's tables of builds, rollouts with their tiers and assignments, and chain_moved.** It refuses, in the same transaction and before any drop, while a pending assignment is waiting, applying, or raised and unanswered. Your Approve of this merge is your word on dropping them; every row was copied onto the bus by delivery 1 and is read back from there.
- Issues 1094, 1108, 1109, 1110, 1096, 1111 (node.sent_builds copied onto the assignments' keys once and kept, a send empties its node's column; no table of the chain left after a live delivery; integration test of it).
- Merged onto #380: the build layout runs at start under a `layout.done` marker, never overwrites a pointer and skips records already laid out (nothing reads the chain before the marker exists).
Issues: 1094, 1108, 1109, 1110, 1096, 1111; design 47 milestone 5 (981).
Reviewed-by: reviewer-1121@shanks at 7f074d9c94c6583468991f337fac4ac67a72493e (the merge onto #380; delivery 2 itself approved in round 3 at 4eeba8fb203255297c47b33b1315d8722c67476c; head 0b4cd46b only merges main, identical tree)
A wait for a build is the value of <node>.<module> with state pending and a pending object (id p-<unix nanoseconds>, a string), so every reader that skips a value with a state skips it, and the controller's own lists skip it through Stands. The transitions are compare-and-set on the key's revision (claim, release, settle, repoint, mark); assigning over a wait carries it into the value that stands, applied when it was waiting; a plan pass never overwrites it; one open wait per machine and module, and a key that holds the module refuses a new one. The table is no longer read or written, ForgetEndedPending is gone (no key is removed), and a wait of a machine the store dropped is none. Callers change type only; their conditions are the next issue.
A wait that ended unmade and whose condition nobody answered is carried by the wait that replaces it, so the operator is never left without the condition for a module still not on its machine, and taking it back, its condition and the orphan sweep read it there. The condition id stays node.module.<id> with the string id. clearOrphaned says a taken-back wait too. TestAnAssignmentWaitingForItsBuildIsOneKeyOfTheAssignmentsBucket enters through the assign verb and reads the key before and after the build's outcome.
SentBuilds answers from the keys of the node's assignments that name a commit, known when the node was sent anything and no key says its commit unknown. A send that names its builds writes the commit, build and rollout on each carried module's key (a module nothing assigns gets a standing key marked pulled-in, never a state) and clears what every other key of the node named; a send by hand writes sent-unknown, a time, on every key and clears their commits. A failed write of these fails the record of the send. node.sent_builds is no longer written. The plan pass ends a pulled-in key only when no send carries it.
Every method of builds, build requests, rollouts, merges and assignments reads and writes the chain alone: the else branches that read the tables, the movers and MoveChain with their tests, chain_moved reads, ChainReads and the flags that switched a kind, the store's assignments mirror (KeepAssignmentPlans needs none of it: it uses only the AssignmentMirrored type, mirrors.go, and AssignmentValues, provisioning.go) and its tick, the move code of the controller's start, and ForTest's chain_moved row. The listed store tests of the move go with their functions; the tests of the readers, requests, assignments and plans that lived beside them stay in chain_store_test.go. Tests that replayed old data migrations over the build, assignment and pin tables are removed with the tables. The static test that no plan is written but through SavePlansMoving now reads the plan's chain path.
The migration raises first unless chain_moved names builds, rollouts and assignments for every kind that holds rows, and unless pending_assignment holds no open or unanswered row; then it drops build_request, build, batched_merge, release_plan, pending_assignment, assignment, raise_assignment_generation(), node.sent_builds and chain_moved. build_gate stays.
Delivery 1 wrote no commit on the key of a pulled-in module, so after the upgrade those modules fell out of SentBuilds. At the start of the lease holder a copy fills every key that names no commit (creating a standing pulled-in key where none stands), overwrites nothing, empties each column it copied, and raises an urgent condition while it fails. Migration 0105 no longer drops node.sent_builds (issue 1112 does).
A found ended or pending key is skipped and a pulled-in key is created only where no key exists. RecordSentWith and RecordSentUnder set sent_builds = null in their own update of the node row, so a machine delivery 2 has sent is never copied afterwards. These two updates and the copy's own null are the only writes to the column.
Delivery 2 deleted the move and chain_moved, so the layout of the builds under their modules is made by the controller's start (LayBuildsOut), recorded by the key layout.done in the builds bucket, retried every half minute with an urgent condition while it fails; the chain on the bus is refused until it exists. Its source readers use the module and pointer reads.
The live start recorded its layout in chain_moved, so the marker is missing and the layout runs once more over the old keys. It wrote newest, worked, held, commit and source over the pointers of every build made since. Pointers are now made only where missing, and a record already under its new key is not read again.
mesh/merge-gate head 0b4cd46b3f04 merged into trunk da6d038e07c0 — error: builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step; the m…
mesh/repo-check head 0b4cd46b3f04 merged into trunk da6d038e07c0 — fail: its merge-check.sh failed: --- FAIL: TestAnAssignmentThatBlocksAnotherMachineSaysW…
Deliverynovox/mesh-controller@68db18bdfc1b — delivered since 2026-10-18T12:45:04Z
Delivery plan — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
tier 0: mesh-controller
tier 1: build-agent
ace: receives build-agent
g14: receives build-agent
novox: receives mesh-controller, build-agent
shanks: receives build-agent
build-agent keeps data (ADR 0233): what it holds is backed up before it moves
grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before build-agent is judged on its first machine
Machines
mesh-controller on every machine running it: sent
build-agent on every machine running it: sent
Transitions
2026-10-18 12:22 (new) → proposed (announced): novox/mesh-controller#381's head announced
2026-10-18 12:29 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-18 12:29 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-18 12:30 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-18 12:30 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path — not a failed walk that carried a later commit for it, after which it waits for a walk of its own commit
2026-10-18 12:45 delivering → delivered (done): its walk is done, carrying its own commit: every machine of its deploy plan passed, or was left as its policy says
The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.
<!-- mesh-delivery:view -->
**Delivery** `novox/mesh-controller@68db18bdfc1b` — **delivered** since 2026-10-18T12:45:04Z
**Delivery plan** — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
- tier 0: mesh-controller
- tier 1: build-agent
- ace: receives build-agent
- g14: receives build-agent
- novox: receives mesh-controller, build-agent
- shanks: receives build-agent
- build-agent keeps data (ADR 0233): what it holds is backed up before it moves
- grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before build-agent is judged on its first machine
**Machines**
- mesh-controller on every machine running it: sent
- build-agent on every machine running it: sent
**Transitions**
- 2026-10-18 12:22 (new) → proposed (announced): novox/mesh-controller#381's head announced
- 2026-10-18 12:29 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
- 2026-10-18 12:29 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-18 12:30 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-18 12:30 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path — not a failed walk that carried a later commit for it, after which it waits for a walk of its own commit
- 2026-10-18 12:45 delivering → delivered (done): its walk is done, carrying its own commit: every machine of its deploy plan passed, or was left as its policy says
The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
Merge check at 0b4cd46b
Judged: head 0b4cd46b3f04 merged into trunk da6d038e07c0; read beside it: mesh-catalog 7f77ce663a9e, mesh-controller-main da6d038e07c0, mesh-host 6469e8238443, mesh-tools 7412c5b6c9c5
mesh/merge-gate: ERROR — the mesh as it is could not be raised, so the change cannot be judged against it (4 of 4 machines compose on the mesh and not in the gate); the first: a machine (f35) composes on the mesh and not as the gate raised it from the snapshot: the private network cannot be computed: whether f35 answers "mesh-addressing" cannot be read: this kind of record lives on the bus, and this process has not opened the bus: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus (modules: mesh-controller)
mesh/repo-check: FAIL — its merge-check.sh failed: --- FAIL: TestAnAssignmentThatBlocksAnotherMachineSaysWhichAndWhy (0.34s); and TestConvergingIsRefusedOnAPreviewThatWouldBeStale, TestTheFlipHoldsTheNodeWhileItSends, TestAPlanCutFromAMergeOfABackedUpModuleAsksItsBackupAndNotItsTierUntilItIsDone, TestAFailedWalkWalksItsEarlierMergesAlone, TestARepositoryMadeAgainUnderItsNameIsNotTheModulesSource and 395 more
Delivery plan — builds mesh-controller → novox; no bus step
Run by the build seat on ace as build-1792323739962081324 (builds --log build-1792323739962081324).
vault_secrets_integration_test.go:23: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAcceptForAMovedTrustedModuleAnnouncesBeforeTheVaultIsAsked (0.26s)
vault_switch_test.go:340: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAWalkRestartedByARebuildIsSaidStarted (0.24s)
walk_said_integration_test.go:210: the builds are not laid out under their modules yet; the controller's start does it and says so
FAIL
FAIL github.com/novox/mesh-controller/cmd/mesh-controller 15s (shard 8 of 8: 139 tests)
ok github.com/novox/mesh-controller/internal/inventory 16s (shard 1 of 4: 89 tests)
builds: the pointer alpha.newest was missing or wrong (a lookup of alpha.commit.c4) and is repaired from the records of alpha
builds: the pointer alpha.worked was missing or wrong (a lookup of alpha.commit.c4) and is repaired from the records of alpha
builds: the pointer alpha.held was missing or wrong (a lookup of alpha.commit.c4) and is repaired from the records of alpha
builds: the pointer alpha.commit.c4 was missing or wrong (a lookup of alpha.commit.c4) and is repaired from the records of alpha
builds: the pointer alpha.source.v1-s4 was missing or wrong (a lookup of alpha.commit.c4) and is repaired from the records of alpha
builds: the pointer alpha.commit.c2 was missing or wrong (a lookup of alpha.commit.c2) and is repaired from the records of alpha
--- FAIL: TestAPendingAssignmentIsAKeyOfTheAssignmentsBucket (0.16s)
chain_pending_test.go:57: known map[p-1792323830140566939:true p-1792323830146532820:true]: the key holds the newer one now
FAIL
FAIL github.com/novox/mesh-controller/internal/inventory 12s (shard 2 of 4: 89 tests)
--- FAIL: TestThePlansAreKeptInTheAssignmentsValuesAndNothingElseOfThemMoves (0.17s)
chain_store_test.go:314: dunst's value is {Node:anchor Module:dunst Assigned:2026-10-18 11:43:50.485416876 +0000 UTC RequiredBy: Provisioning:[123 34 116 101 109 112 108 97 116 101 115 34 58 123 34 115 111 117 114 99 101 34 58 34 104 116 116 112 58 47 47 115 116 111 114 101 58 53 48 48 48 47 118 50 47 100 117 110 115 116 47 102 105 108 101 115 47 98 108 111 98 115 47 115 104 97 50 53 54 58 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 34 44 34 100 105 103 101 115 116 34 58 34 115 104 97 50 53 54 58 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 34 125 44 34 102 105 108 101 115 34 58 91 123 34 105 100 34 58 34 99 111 110 102 105 103 117 114 97 116 105 111 110 34 44 34 112 97 116 104 34 58 34 47 104 111 109 101 47 111 112 47 46 99 111 110 102 105 103 47 100 117 110 115 116 47 100 117 110 115 116 114 99 34 44 34 116 101 109 112 108 97 116 101 34 58 34 100 117 110 115 116 114 99 34 44 34 111 119 110 101 114 45 97 116 45 114 117 110 116 105 109 101 34 58 34 111 119 110 101 100 34 44 34 116 97 107 101 115 34 58 34 114 101 108 111 97 100 45 111 110 34 125 93 125] Build: Artifact: Package:<nil> Commit: Rollout: Since:0001-01-01 00:00:00 +0000 UTC Ended:0001-01-01 00:00:00 +0000 UTC State: Pending:<nil> PulledIn:false SentUnknown:2026-10-18 11:43:50.492705524 +0000 UTC}
FAIL
FAIL github.com/novox/mesh-controller/internal/inventory 13s (shard 3 of 4: 88 tests)
ok github.com/novox/mesh-controller/internal/inventory 15s (shard 4 of 4: 88 tests)
ok github.com/novox/mesh-controller/internal/builder 14s (shard 1 of 4: 54 tests)
ok github.com/novox/mesh-controller/internal/builder 16s (shard 2 of 4: 53 tests)
ok github.com/novox/mesh-controller/internal/builder 24s (shard 3 of 4: 53 tests)
ok github.com/novox/mesh-controller/internal/builder 15s (shard 4 of 4: 53 tests)
ok github.com/novox/mesh-controller/internal/link 22s (shard 1 of 4: 50 tests)
ok github.com/novox/mesh-controller/internal/link 15s (shard 2 of 4: 50 tests)
ok github.com/novox/mesh-controller/internal/link 17s (shard 3 of 4: 49 tests)
ok github.com/novox/mesh-controller/internal/link 23s (shard 4 of 4: 49 tests)
integration level (the whole suite, tag integration): 3404 tests (6 skipped outside the shards), 62 s
nested module modules/build-agent:
ok build-agent 1.012s
nested module modules/route-proxy:
ok route-proxy/cmd/route-provider 1.011s
nested modules: 3 s
store tests, each run against the store:
./cmd/mesh-controller --- FAIL: TestAStopWithoutAMergeWalksTheOthersAgain (0.14s)
./cmd/mesh-controller --- FAIL: TestAStopWithoutAMergeEndsTheMergesThatContainIt (0.14s)
./cmd/mesh-controller --- FAIL: TestAStopWalksTheOthersAgainInTheOpenBatch (0.14s)
./cmd/mesh-controller --- FAIL: TestAStopNamesWhatStaysOnTheMachinesAndWhatStillCarriesIt (0.12s)
./cmd/mesh-controller --- FAIL: TestAStopWithoutAMergeLeavesItOutOfABatch (0.13s)
./cmd/mesh-controller --- FAIL: TestSavingPlansAndMovingMergesIsOneAct (0.16s)
./cmd/mesh-controller --- FAIL: TestAPlanFollowedFromTheStoreAnswersWhenItMoves (0.23s)
./cmd/mesh-controller --- FAIL: TestIssue969TheGateRaisesEachMachineAsItsEngineStatedItself (0.19s)
./cmd/mesh-controller --- FAIL: TestNodeShowAndStatusReadTheLastSendFromTheStore (0.20s)
./cmd/mesh-controller --- PASS: TestTheConditionsVerbReadsTheLooksTheBucketNoLongerHolds (0.13s)
./cmd/mesh-controller --- FAIL: TestAWalkLetGoAndStoppedByVerbsIsSaidStartedAndEnded (0.19s)
./cmd/mesh-controller --- FAIL: TestAWalkStoppedOrClosedByAPersonIsSaidEndedStopped (0.21s)
./cmd/mesh-controller --- FAIL: TestAWalkRetriedByAPersonIsSaidStartedAgain (0.17s)
./cmd/mesh-controller --- FAIL: TestABacklogReleasedByAPersonIsSaidStarted (0.17s)
./cmd/mesh-controller --- FAIL: TestAWalkEndedByCancelOrClearIsSaidEnded (0.21s)
./cmd/mesh-controller --- FAIL: TestAWalkRestartedByARebuildIsSaidStarted (0.18s)
./cmd/mesh-controller --- FAIL: TestAWalkStoppedByHandAndRetriedEndsFailedWhenItFailsAgain (0.26s)
./cmd/mesh-controller --- FAIL: TestReplay237 (0.19s)
./cmd/mesh-controller --- FAIL: TestAnUnassignThatLeavesItsNodeUnresolvedSaysSoOnceInItsAnswer (0.19s)
./cmd/mesh-controller --- FAIL: TestAnUnassignThatLeavesItsNodeResolvedSaysNothingOfIt (0.25s)
./cmd/mesh-controller --- FAIL: TestAnAssignThatLeavesItsNodeUnresolvedSaysOnlyThePlansRefusal (0.24s)
./cmd/mesh-controller --- FAIL: TestADirectoryOwnersKeyIsRefusedThroughAVerb (0.20s)
./cmd/mesh-controller --- FAIL: TestTheSendMakesNoValueForAnOutsideSecretNobodyGave (0.23s)
./cmd/mesh-controller --- FAIL: TestAQuestionComposesWithoutAnOutsideSecretNobodyGave (0.29s)
./cmd/mesh-controller --- FAIL: TestReplay201 (0.18s)
./cmd/mesh-controller --- FAIL: TestARollbackWhoseSendWasRefusedIsCompletedByTheNextSend (0.15s)
./cmd/mesh-controller --- FAIL: TestAGateJudgesTheOtherMovesBesideAKeptCore (0.14s)
./cmd/mesh-controller --- FAIL: TestReplay401 (0.23s)
./cmd/mesh-controller --- FAIL: TestReplay201ThePlansSend (0.18s)
./cmd/mesh-controller --- FAIL: TestPlanAndNodeListAnOptionalRequirementLeftUnbound (0.18s)
./cmd/mesh-controller --- FAIL: TestReplay340 (0.18s)
./cmd/mesh-controller --- FAIL: TestOnlyATrustedFilesNamedKeyIsRefusedThroughAVerb (0.20s)
./cmd/mesh-controller --- FAIL: TestReplay349 (0.26s)
./cmd/mesh-controller --- FAIL: TestReplay348AFaultFromBeforeTheSendFailsNoGate (0.28s)
./cmd/mesh-controller --- FAIL: TestReplay239AModuleNameIsNotTakenOverByAnotherRepository (0.22s)
./cmd/mesh-controller --- FAIL: TestAWalkThatMovedNothingSaysWhichModulesMatchedWhatRuns (0.14s)
./cmd/mesh-controller --- FAIL: TestAWalkWhoseEveryBuildCameOutTheSameIsDone (0.17s)
./cmd/mesh-controller --- PASS: TestReplay614ANewSDKPlansTheToolchainAndThenItsBundles (0.13s)
./cmd/mesh-controller --- FAIL: TestOneAcceptForAProviderIsPlacedForEveryConsumer (0.21s)
./cmd/mesh-controller --- FAIL: TestReplay164 (0.21s)
./cmd/mesh-controller --- FAIL: TestAnApprovedLayerOpensTheWalkThatSendsIt (0.16s)
./cmd/mesh-controller --- FAIL: TestASettingsWalkSendsOneMachineAtATimeEachJudged (0.19s)
./cmd/mesh-controller --- FAIL: TestAFailedSettingsWalkStopsAndHoldsNothingBack (0.17s)
./cmd/mesh-controller --- FAIL: TestASettingsWalkSendsTheLayerAloneEveryBuildKept (0.17s)
./cmd/mesh-controller --- FAIL: TestASettingsWalkStopsBeforeADataMoveAndPassesOverAMachineAway (0.19s)
./cmd/mesh-controller --- FAIL: TestACrossingSendSupersedesASettingsGate (0.17s)
./cmd/mesh-controller --- FAIL: TestASettingsWalkFailsOnARefusalThatCannotClear (0.17s)
./cmd/mesh-controller --- FAIL: TestAProviderElsewhereServesItsOwnComposedName (0.20s)
./cmd/mesh-controller --- FAIL: TestAReusedCheckBuildIsRegisteredByItsDigestAndGatedAsABuiltOne (0.12s)
./cmd/mesh-controller --- FAIL: TestTheMergeGateJudgesEachManifestAgainstTheListOfTheTree (0.24s)
./cmd/mesh-controller --- FAIL: TestRegistrationPublishesTheNewestTrunkListAndJudgesEveryModuleAgainstIt (0.25s)
./cmd/mesh-controller --- FAIL: TestADeclarationIsTheSameAfterPlacementMoves (0.27s)
./cmd/mesh-controller --- FAIL: TestAReleaseSendsTheRestAtOnceAfterTheFirstPasses (0.18s)
./cmd/mesh-controller --- FAIL: TestARestMachineThatFailsIsPutBackAloneAndTheOthersAreJudgedOn (0.20s)
./cmd/mesh-controller --- FAIL: TestAWalkTakesOverTheReadingsOfAGateJudgingTheSameBuildThere (0.19s)
./cmd/mesh-controller --- FAIL: TestAFirstSendMadeAndNotKeptIsNotSentAgain (0.19s)
./cmd/mesh-controller --- FAIL: TestAReleaseSendKeptAndMadeIsNotMadeAgain (0.19s)
./cmd/mesh-controller --- FAIL: TestAFirstMachineThatFailsStillStopsTheWalk (0.16s)
./cmd/mesh-controller --- FAIL: TestTheControlNodeIsSentLastInAStep (0.16s)
./cmd/mesh-controller --- FAIL: TestARestMachineSilentPastItsBoundIsLeftAndSaid (0.17s)
./cmd/mesh-controller --- FAIL: TestANoMoveTierWaitsForNoNewReport (0.15s)
./cmd/mesh-controller --- FAIL: TestOneProviderDownAndThreeConsumersFailingAreOneCondition (0.20s)
./cmd/mesh-controller --- FAIL: TestAConsumerFailingBesideAHealthyProviderIsItsOwn (0.32s)
./cmd/mesh-controller --- FAIL: TestTheProvisionerClientsAccountIsIssuedForItsServiceAndNeverInvented (0.41s)
./cmd/mesh-controller --- FAIL: TestAcceptOfAnOwnSecretTakesThePathOfItsModulesForm (0.16s)
./cmd/mesh-controller --- FAIL: TestAcceptForAProviderTakesThePathOfTheProvidersModule (0.16s)
./cmd/mesh-controller --- FAIL: TestAcceptForAMovedTrustedModuleAnnouncesBeforeTheVaultIsAsked (0.16s)
./cmd/mesh-controller --- FAIL: TestAcceptForAMovedModuleRecordsAHandActAndNeverTheValue (0.18s)
./cmd/mesh-controller --- FAIL: TestAcceptOfAnOutsideOfferTakesThePathOfTheProvidersModule (0.15s)
./cmd/mesh-controller --- FAIL: TestAnAskAtTheDeskTakesThePathOfItsModulesForm (0.23s)
./cmd/mesh-controller --- FAIL: TestAnIssuedValueTakesThePathOfItsProvidersModule (0.25s)
./cmd/mesh-controller --- FAIL: TestARotationTakesThePathOfItsModulesForm (0.24s)
./cmd/mesh-controller --- FAIL: TestADeclarationIsTheSameWhileTheWordsAreStillInTheLayers (0.23s)
./cmd/mesh-controller --- FAIL: TestADeclarationIsTheSameAfterTheMoveOfPlacement (0.26s)
./cmd/mesh-controller --- FAIL: TestTheSendSealsNoSecretOfAModuleHandedThere (0.18s)
./cmd/mesh-controller --- FAIL: TestAModulesSecretsAreTheVaultsOnceItIsMarkedMoved (0.18s)
./cmd/mesh-controller --- FAIL: TestEveryMachineIsToldTheSameAfterTheMoveOfConfig (0.13s)
./cmd/mesh-controller --- FAIL: TestTheMoveOfConfigRefusesWhatWouldChangeAMachine (0.13s)
./cmd/mesh-controller --- FAIL: TestTheSettingsVerbForwardsToConfigOnceTheValuesMoved (0.19s)
./cmd/mesh-controller --- FAIL: TestTheSendCarriesTheVaultsBoxForACoreCredentialAndKeepsIt (0.23s)
./cmd/mesh-controller --- FAIL: TestASilentVaultHoldsTheKeptBoxAndSaysSo (0.24s)
./cmd/mesh-controller --- FAIL: TestACoreModuleFirstPlacedWhileTheVaultIsSilentIsSealedByTheController (0.23s)
./cmd/mesh-controller --- FAIL: TestAnEngineBelowTheContractIsSentTheControllersSealAsBefore (0.23s)
./cmd/mesh-controller --- FAIL: TestModuleIssueHandsACoveredAccountToTheVaultAndOnlyThat (0.20s)
./cmd/mesh-controller --- FAIL: TestModuleIssueFailsWhenTheVaultDoesNotTakeACoveredAccount (0.18s)
./cmd/mesh-controller --- FAIL: TestModuleIssueBeforeTheVaultIsInstalledKeepsTheValueAndHandsNothing (0.23s)
./cmd/mesh-controller --- FAIL: TestARecordedModulesBundleOnlyMoveRollsOutInItsWalk (0.37s)
./cmd/mesh-controller --- FAIL: TestARecordedModulesMoveThatRecreatesAContainerWaits (0.75s)
./cmd/mesh-controller --- FAIL: TestARecordedModulesMoveThatTouchesDataOrAProviderWaits (1.03s)
./cmd/mesh-controller --- FAIL: TestAPersonsRecordAndTheBusHoldEveryMove (0.46s)
./cmd/mesh-controller --- FAIL: TestARecordedMoveThatCannotBeJudgedWaits (0.19s)
./cmd/mesh-controller --- FAIL: TestReplay867 (0.20s)
./cmd/mesh-controller --- FAIL: TestReplay867Recheck (0.19s)
./cmd/mesh-controller --- FAIL: TestTheRecheckVerbAsksMeshDeliveryOnABusOfItsOwn (0.24s)
./cmd/mesh-controller --- FAIL: TestAssigningTheClientIssuesItsAccount (0.54s)
./cmd/mesh-controller --- FAIL: TestAnUnrelatedBatchWalksBesideAnOpenWalk (0.22s)
./cmd/mesh-controller --- FAIL: TestARelatedBatchWaitsBehindTheOpenWalk (0.13s)
./cmd/mesh-controller --- FAIL: TestAnOwnPathBatchNeverWalksBeside (0.12s)
./cmd/mesh-controller --- FAIL: TestMergesHeardWhileAnotherHolderHasThePlansAreRecordedAndCarried (0.22s)
./cmd/mesh-controller --- FAIL: TestABatchWindowClosesByTheExpiryOfItsKey (0.18s)
./cmd/mesh-controller --- FAIL: TestEveryMoveAMergeAndTheCutMakeOfAPlanIsSaid (0.35s)
./cmd/mesh-controller --- FAIL: TestARolloutAdvancesOnEventsAndAReplacedControllerResumesIt (0.17s)
./cmd/mesh-controller --- FAIL: TestAWalkLetGoByTheDeliverVerbIsAskedWithNoOtherEvent (0.17s)
./cmd/mesh-controller --- FAIL: TestTwoMergesWithinAMinuteLeaveEachOpenPullRequestOneQueuedCheck (0.12s)
./cmd/mesh-controller --- FAIL: TestADeliveryGroupMovingAModuleMachinesRunPassesTheGate (0.15s)
./cmd/mesh-controller --- FAIL: TestAModuleMovesOnTheOperatorsApproveOfTheMergeThatMovedIt (0.12s)
./cmd/mesh-controller --- FAIL: TestAModuleBuiltFromANewRepositoryIsRegisteredOnlyOnTheOperatorsApproveOnTheBus (0.32s)
./cmd/mesh-controller --- FAIL: TestAMergeWhosePlanCannotBeSavedIsHeldAndRecordedWhenHandedOverAgain (0.15s)
./cmd/mesh-controller --- FAIL: TestOneReadOfAnAssignmentNamesItsCommitBuildAndRolloutAndOneReadOfTheRolloutListsItsAssignments (0.13s)
./cmd/mesh-controller --- FAIL: TestASendOfWhatAMachineRunsAlreadyChangesNoLinkOfItsAssignment (0.12s)
./cmd/mesh-controller --- FAIL: TestAnAssignmentWaitingForItsBuildIsOneKeyOfTheAssignmentsBucket (0.12s)
./cmd/mesh-controller --- FAIL: TestNoTableOfTheControllersStoreHoldsBuildsRolloutsOrAssignments (0.12s)
./cmd/mesh-controller FAIL: go test exited 1
./internal/inventory --- PASS: TestTheLastSendSaysWhatTheMachineAnswered (0.08s)
./internal/inventory --- PASS: TestAReportIsTheLastSendsAnswerOnlyWhenItIsAboutThatSend (0.08s)
./internal/inventory --- PASS: TestAnIssuedValueIsSealedToEveryHolderOnceAndNotAgain (0.17s)
./internal/inventory --- PASS: TestAnIssuedValueIsSealedAgainAfterAKeyChangeOrAnAcceptance (0.15s)
./internal/inventory --- PASS: TestAConditionsLooksAreKeptBesideTheBucket (0.12s)
./internal/inventory --- PASS: TestAPlanIdHoldingAQuoteIsReadAsAPlainId (0.08s)
./internal/inventory --- PASS: TestAWalksStartIsKeptAndARefusedSaveLeavesItUnsaid (0.06s)
./internal/inventory --- PASS: TestAWalksRestIsReadFromEachMachinesOwnSend (0.07s)
./internal/inventory --- PASS: TestAStoredBuildWithASilentMergeableFileIsStillReadAndComposed (0.06s)
./internal/inventory --- PASS: TestACredentialIssuedOutsideIsNeverMade (0.14s)
./internal/inventory --- PASS: TestOneAcceptForAProviderIsSealedToEveryConsumer (0.14s)
./internal/inventory --- PASS: TestASharedOwnSecretIssuedOutsideIsNeverMade (0.13s)
./internal/inventory --- PASS: TestAModuleInTheConfigFormIsMirroredWithItsWholeDeclaration (0.07s)
./internal/inventory --- PASS: TestAReportOfABusyContainerIsKeptAndReadBack (0.08s)
./internal/inventory --- PASS: TestANewerBuildsListReplacesTheKeptOneAndAnOlderOneHeardLaterDoesNot (0.09s)
./internal/inventory --- PASS: TestPlacementMovesOutOfTheSettingsLayers (0.40s)
./internal/inventory --- PASS: TestASettingRoutesPlacementBesideTheLayer (0.09s)
./internal/inventory --- PASS: TestTheProvisionerClientsMachineHasAnAccountOfItsOwn (0.12s)
./internal/inventory --- PASS: TestTheFourWordsAreKeptBesideTheLayer (0.09s)
./internal/inventory --- PASS: TestALayerStillHoldingTheWordsReadsThemAsPlacement (0.08s)
./internal/inventory --- PASS: TestTheMoveOfPlacementMovesWhatTheLayersStillHold (0.10s)
./internal/inventory --- PASS: TestTheMoveReadsEveryRowSealedToAMachineAsItIs (0.09s)
./internal/inventory --- PASS: TestASendKeepsThePlansItHandedAndTheMirrorCarriesThem (0.08s)
./internal/inventory --- PASS: TestTheLayersAreReadUntilTheMoveOfConfigHasRun (0.09s)
./internal/inventory --- PASS: TestAModuleReadsMeshConfigOnlyWhereItsValuesAre (0.08s)
./internal/inventory --- PASS: TestTheEndOfTheMoveRefusesALayerChangedSinceItWasRead (0.14s)
./internal/inventory --- PASS: TestACoreCredentialsVaultBoxIsKeptPerMachineAndReplaced (0.10s)
./internal/inventory --- PASS: TestWhatRunsIsTheRegisteredBuildNotANewerOnePutBack (0.07s)
./internal/inventory --- PASS: TestBuildsOnTheBusAreReadBackByEveryReader (0.07s)
./internal/inventory --- PASS: TestARequestIsTheBuildInStateAskedAndItsOutcomeTakesItsPlace (0.06s)
./internal/inventory --- PASS: TestAnAssignmentIsAKeyOfTheBucketAndAnUnassignmentEndsIt (0.10s)
./internal/inventory --- FAIL: TestThePlansAreKeptInTheAssignmentsValuesAndNothingElseOfThemMoves (0.09s)
./internal/inventory --- FAIL: TestAPendingAssignmentIsAKeyOfTheAssignmentsBucket (0.07s)
./internal/inventory --- PASS: TestARecordedPendingIsSkippedByAssignedAndTheJoins (0.07s)
./internal/inventory --- PASS: TestTwoClaimsOfOnePendingMakeOneAndTheOtherSeesFalse (0.08s)
./internal/inventory --- PASS: TestAssignOverAPendingKeepsItsRecordAsApplied (0.07s)
./internal/inventory --- PASS: TestAPendingIsMarkedOnceAndGoesWithItsMachine (0.08s)
./internal/inventory --- PASS: TestAReplacedWaitNeverLeavesTheOperatorWithoutItsCondition (0.06s)
./internal/inventory --- PASS: TestSentBuildsAnswersFromTheAssignmentsKeysOfTheNode (0.08s)
./internal/inventory --- PASS: TestASendReplacesTheWholeMapOfTheNodeAndAHandSendMakesItUnknown (0.08s)
./internal/inventory --- PASS: TestAFailedWriteOfTheLinksFailsTheRecordOfTheSend (0.07s)
./internal/inventory --- PASS: TestMigration0105RefusesAStoreWhoseRowsWereNotMovedAndDropsTheTablesOfAMovedOne (0.38s)
./internal/inventory --- PASS: TestMigration0105PassesAStoreThatNeverHeldARow (0.09s)
./internal/inventory --- PASS: TestTheColumnOfASentMachineIsCopiedOntoItsKeysAndEmptied (0.07s)
./internal/inventory --- PASS: TestASendEmptiesTheColumnSoALaterCopyLeavesAClearedKeyBare (0.09s)
./internal/inventory FAIL: go test exited 1
./internal/recordmirror --- PASS: TestNatsAnAssignmentAndARegistrationEachChangeOneKeyAndRaiseOneEvent (2.20s)
./internal/recordmirror --- PASS: TestNatsTheListOfPredefinedKeysKeptChangesTheMirrorsOneKey (1.49s)
114 store test(s) listed in testdata/store-tests did not run and pass against the store
--- what failed, picked from the whole of its output (the whole is in the build's log)
--- FAIL: TestAnAssignmentThatBlocksAnotherMachineSaysWhichAndWhy (0.34s)
acts_test.go:27: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestConvergingIsRefusedOnAPreviewThatWouldBeStale (0.34s)
adopting_test.go:134: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestTheFlipHoldsTheNodeWhileItSends (0.31s)
adopting_test.go:502: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAPlanCutFromAMergeOfABackedUpModuleAsksItsBackupAndNotItsTierUntilItIsDone (0.25s)
backups_before_send_integration_test.go:226: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAFailedWalkWalksItsEarlierMergesAlone (0.31s)
batches_integration_test.go:341: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestARepositoryMadeAgainUnderItsNameIsNotTheModulesSource (0.30s)
build_source_integration_test.go:214: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestASendAssertsWhatWasAssignedAfterStart (0.31s)
busobjects_test.go:84: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestNoTableOfTheControllersStoreHoldsBuildsRolloutsOrAssignments (0.29s)
chain_no_table_integration_test.go:18: the builds are not laid out under their modules yet; the controller's start does it and says so
the checks' builds of 1 pull request(s) could not be read, so the walk builds: no bus
--- FAIL: TestTwoMergesWithinAMinuteLeaveEachOpenPullRequestOneQueuedCheck (0.28s)
checks_queue_test.go:25: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestTheMoveOfConfigRefusesWhatWouldChangeAMachine (0.30s)
config_moved_integration_test.go:262: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAnEngineBelowTheContractIsSentTheControllersSealAsBefore (0.28s)
core_box_integration_test.go:121: the builds are not laid out under their modules yet; the controller's start does it and says so
novox/mesh-catalog changed more files than were listed: the manifests of its modules (modules/a/module.json) are read as changed
novox/mesh-catalog changed more files than were listed: the manifests of its modules (modules/a/module.json) are read as changed
--- FAIL: TestAMachineWhoseDeclarationDoesNotComposeIsSaid (0.27s)
doctor_integration_test.go:127: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestABuildThatFailsItsGateIsRolledBackOnItsFirstMachineAndGoesNoFurther (0.28s)
gate_integration_test.go:142: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestNatsH3AssertsAMissingConsumerAgainAndBrakesAfterItsBudget (0.28s)
healers_integration_test.go:253: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestANamedPushStillSendsAConsequenceNothingHolds (0.26s)
held_back_integration_test.go:130: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestSavingPlansAndMovingMergesIsOneAct (0.25s)
issue459_integration_test.go:268: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestNodeShowAndStatusReadTheLastSendFromTheStore (0.27s)
last_send_integration_test.go:14: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAMachineSilentPastItsBoundIsLeftAndSaidAtOnce (0.27s)
lean_walk_integration_test.go:95: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestARelatedMergeJoinsTheBatchAndWaitsForTheWindow (1.08s)
--- FAIL: TestARelatedMergeJoinsTheBatchAndWaitsForTheWindow/same_repository (0.25s)
lone_merge_test.go:41: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestARelatedMergeJoinsTheBatchAndWaitsForTheWindow/a_module_in_common (0.32s)
lone_merge_test.go:41: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestARelatedMergeJoinsTheBatchAndWaitsForTheWindow/an_edge_of_the_graph (0.25s)
lone_merge_test.go:41: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestARelatedMergeJoinsTheBatchAndWaitsForTheWindow/the_same_group_head (0.26s)
lone_merge_test.go:41: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestALoneMergeRelatedToAWalkTheCutFoldsJoinsTheBatch (0.24s)
lone_merge_test.go:314: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAFailedUnitIsTheModulesConditionAndTheMachinesOwnAreOneFinding (0.28s)
machine_units_integration_test.go:15: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAManifestTheRunningControllerCannotReadFailsThePullRequest (0.30s)
merge_gate_integration_test.go:124: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestTheResolverIsToldEveryMachineOnTheNetworkAndToldAgainWhenOneLeaves (0.26s)
network_test.go:260: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAskingAboutAMachineTheMeshHasNeverHeardOfIsRefused (0.26s)
nodes_test.go:98: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAnUnassignThatLeavesItsNodeResolvedSaysNothingOfIt (0.27s)
one_resolution_integration_test.go:38: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAStatusReadSettlesNothing (0.25s)
pending_integration_test.go:115: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAnUnknownModuleIsRefusedWithTheClosestNames (0.26s)
pending_integration_test.go:388: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestABuildNoLongerWaitedForIsStillInFlight (0.25s)
pending_integration_test.go:709: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAssigningTheClientIssuesItsAccount (0.28s)
provisioner_account_integration_test.go:55: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAPlanStoppedAtItsFirstMachineIsRetried (0.29s)
queue_integration_test.go:336: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestReplay348AFaultFromBeforeTheSendFailsNoGate (0.22s)
replay348_test.go:27: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestReplay273AConsumerBesideItsStoreStaysBoundToIt (0.24s)
replays_integration_test.go:50: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAReleaseSendsTheRestAtOnceAfterTheFirstPasses (0.27s)
rest_at_once_integration_test.go:40: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAnUnhealthyOwnRuntimeRaisesTheModulesUsualCondition (0.24s)
runtime_health_test.go:17: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestADefinitionMovingUnderAStoredSettingLeavesThatModuleOutNotTheMachine (0.21s)
sendable_integration_test.go:302: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestPreferencesListedFromTheStores (0.26s)
settings_effective_integration_test.go:13: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestASettingsWalkStopsBeforeADataMoveAndPassesOverAMachineAway (0.27s)
settings_walk_integration_test.go:315: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestTheAgentsManagedSettingsAreRefusedThroughAVerb (0.22s)
terminal_settings_test.go:223: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestATierPutsABrokenModuleBackAtOnce (0.49s)
--- FAIL: TestATierPutsABrokenModuleBackAtOnce/gate_kept_on_node-tools (0.21s)
tier_send_integration_test.go:325: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestATierPutsABrokenModuleBackAtOnce/gate_kept_on_app1 (0.28s)
tier_send_integration_test.go:325: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAHeldModuleIsFoundFromWhatTheMachineReported (0.23s)
untaken_integration_test.go:27: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAcceptForAMovedModuleRecordsAHandActAndNeverTheValue (0.24s)
vault_switch_test.go:386: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAWalkStoppedByHandAndRetriedEndsFailedWhenItFailsAgain (0.23s)
walk_said_integration_test.go:233: the builds are not laid out under their modules yet; the controller's start does it and says so
FAIL github.com/novox/mesh-controller/cmd/mesh-controller 15s (shard 1 of 8: 140 tests)
--- FAIL: TestAConsumerAssignedBeforeItsProviderIsStillAssigned (0.34s)
acts_test.go:84: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestTheFlipIsRefusedWhileAFoundContainerIsHeld (0.32s)
adopting_test.go:145: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestThePreviewNamesEveryHeldKind (0.32s)
adopting_test.go:547: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestTheSelfCheckSaysAnAgentAccountThatCanBecomeRoot (0.31s)
agent_account_integration_test.go:18: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAModuleAssignedAndNotPushedIsAwaitingAPushNotUncomposable (0.25s)
awaiting_push_integration_test.go:17: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestTwoMergesSecondsApartAreOneWalkAtTheLaterCommit (0.30s)
batches_integration_test.go:66: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAGroupsOrderBecomesTiersInsideTheWalk (0.31s)
batches_integration_test.go:408: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestABuildFromAnAgentsRepositoryIsNotRegisteredAsAModuleTheMeshHolds (0.29s)
build_source_integration_test.go:39: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestATerminalRequestCoversOnlyWhatItAsked (0.29s)
build_source_integration_test.go:240: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestASendThatCannotAssertTheBusSaysSoAndRaisesACondition (0.29s)
busobjects_test.go:123: the builds are not laid out under their modules yet; the controller's start does it and says so
the earlier checks' builds of novox/shop#7 could not be read, so the check builds: no bus
--- FAIL: TestTheSettingsVerbForwardsToConfigOnceTheValuesMoved (0.30s)
config_moved_integration_test.go:306: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestNatsTheBusIsWhatTheControllerDefines (0.27s)
doctor_integration_test.go:149: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAFaultBeforeTheSettleTimeWaitsForTheModuleBesideIt (0.27s)
gate_followup_test.go:64: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestABuildThatPassesItsGateRollsEverywhereUnattended (0.27s)
gate_integration_test.go:231: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestNatsH4ResetsTheControllersEventsConsumerAndItStillDelivers (0.28s)
healers_integration_test.go:343: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestASecondEligibleHolderStandsBesideTheOneHeldByBeingAlone (0.24s)
holdings_test.go:25: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAnOverflowingConsumerNeverRefusesItsProvidersMachine (0.28s)
identity_bound_integration_test.go:14: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAMergeOfAGroupWaitsEvenAlone (0.24s)
lone_merge_test.go:102: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAModuleAMachineRunsRemovedFromItsSourceFails (0.31s)
merge_gate_integration_test.go:133: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestTheRosterNamesOnlyTheMachines (0.23s)
network_test.go:316: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestANodeAddedAdoptedIsAdopted (0.25s)
nodes_test.go:107: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAnAssignThatLeavesItsNodeUnresolvedSaysOnlyThePlansRefusal (0.22s)
one_resolution_integration_test.go:57: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAPendingAssignmentExpiresWhenItsBuildFails (0.23s)
pending_integration_test.go:138: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAnActWithAModuleNotRegisteredIsRefusedWhole (0.21s)
pending_integration_test.go:412: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestOneProviderDownAndThreeConsumersFailingAreOneCondition (0.25s)
provider_hold_test.go:24: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAPlanIsAnsweredOnlyByTheBuildItAskedFor (0.26s)
queue_integration_test.go:403: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestARecordedModulesBundleOnlyMoveRollsOutInItsWalk (0.23s)
recorded_moves_test.go:187: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestTheBacklogIsReleasedOneMachineAtATimeEachJudged (0.40s)
release_test.go:176: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestReplay318 (0.32s)
replay318_test.go:37: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestReplay349 (0.22s)
replay349_test.go:24: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestReplayCrashLoopFailsItsGateOnTheFirstMachine (0.21s)
replays_integration_test.go:111: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestARestMachineThatFailsIsPutBackAloneAndTheOthersAreJudgedOn (0.22s)
rest_at_once_integration_test.go:66: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestASetThatDoesNotComposeIsMarkedAsTheNodesOwnProblem (0.21s)
roster_failure_test.go:15: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAWalkWhoseEveryBuildCameOutTheSameIsDone (0.21s)
same_program_integration_test.go:17: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestACrossingSendSupersedesASettingsGate (0.22s)
settings_walk_integration_test.go:361: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestTheMergeGateJudgesAChangeToATemplateAlone (0.22s)
template_integration_test.go:47: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAnyKeyOfAModuleWithATrustedMergeableFileIsRefusedThroughAVerb (0.20s)
terminal_settings_test.go:293: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestASendCarryingTheToolRunnerWaitsForItsWitnessWindow (0.21s)
tier_send_integration_test.go:380: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestPlanAndNodeListAnOptionalRequirementLeftUnbound (0.22s)
unbound_test.go:16: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestTheJSONStatusCarriesWhatIsHeldAndForWhichModule (0.21s)
untaken_integration_test.go:43: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAcceptOfAnOwnSecretTakesThePathOfItsModulesForm (0.21s)
vault_switch_test.go:117: the builds are not laid out under their modules yet; the controller's start does it and says so
FAIL github.com/novox/mesh-controller/cmd/mesh-controller 25s (shard 2 of 8: 140 tests)
--- FAIL: TestUnassigningAProviderNamesWhoIsNowBlocked (0.34s)
acts_test.go:105: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestTakingNamesWhatItReplaces (0.32s)
adopting_test.go:157: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestTheFlipIsRefusedOnAnAccountNamingNothingReachable (0.32s)
adopting_test.go:590: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestTheFactsCarryTheAgentAccountAsAPseudonym (0.33s)
agent_account_integration_test.go:68: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestASecretThePushCannotMakeIsStillUncomposable (0.29s)
awaiting_push_integration_test.go:72: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestThreeRepositoriesInOneWindowAreOneWalk (0.32s)
batches_integration_test.go:110: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestABatchSurvivesARestart (0.31s)
batches_integration_test.go:444: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestANewModuleFromARepositoryTheCatalogueDoesNotBuildFromIsNotRegistered (0.29s)
build_source_integration_test.go:71: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestNatsAModuleAssignedAfterStartGetsItsConsumerAtItsFirstSend (0.27s)
busobjects_test.go:165: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAComposedMembersCheckIsItsRepositoryChecksAlone (0.32s)
composed_member_check_test.go:48: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAnApprovalRaisedBeforeTheMoveOfConfigIsRefusedAfterIt (0.32s)
config_moved_integration_test.go:404: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAMergeWaitsForItsDeliverysWordAndThePersonsWordWorksWithoutIt (0.30s)
delivery_integration_test.go:20: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAMachineIsSentTheEpochOnlyOnceItSaysItReadsOne (0.27s)
epoch_send_test.go:30: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAPassIsCountedNoFasterThanTheGatesSpacing (0.22s)
gate_followup_test.go:106: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestABuildRollsToEveryMachineAtOnceWithNoGate (0.28s)
gate_integration_test.go:254: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestTheGrantsStepSendsTheUserListAndNothingElse (0.23s)
grants_step_store_test.go:27: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAGroupsBatchWaitsForItsLastMemberHoweverLongItTakes (0.23s)
group_one_batch_test.go:18: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAHolderOnRecordIsNotRewrittenByDerivation (0.22s)
holdings_test.go:83: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAWalkThatMovedNothingSaysWhichModulesMatchedWhatRuns (0.22s)
issue611_integration_test.go:14: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAHeadedMergeInNoGroupIsCutAtOnce (0.25s)
lone_merge_test.go:134: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestIssue278AWideRebuildIsSaidBeforeTheMerge (0.23s)
merge_gate_integration_test.go:141: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestTwoUnhealthyStatementsRaiseTheModulesConditionAndAHealthyOneClearsIt (0.23s)
module_health_test.go:39: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestPlacingANodeWithNothingSaidDoesNotUnplaceIt (0.25s)
network_test.go:38: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAMergeBuildsTheNewModuleItAdds (0.25s)
new_module_on_merge_test.go:33: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestATokenIssuedAdoptedSaysSoAndReissuingDoesNotConverge (0.26s)
nodes_test.go:128: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestTheConditionClearsWhenTheModuleIsAssignedLater (0.23s)
pending_integration_test.go:205: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestUnassignWithdrawsAPendingAssignment (0.21s)
pending_integration_test.go:427: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestADeclarationIsTheSameAfterPlacementMoves (0.28s)
placement_moved_test.go:24: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAControllerLeavesThePlansToTheOneHoldingThem (0.33s)
plans_one_at_a_time_test.go:16: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAConsumerFailingBesideAHealthyProviderIsItsOwn (0.30s)
provider_hold_test.go:145: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAPushSaysWhatItRecreates (0.21s)
push_recreates_test.go:20: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAFailedPlanIsRetriedAndGoesOnThroughItsLaterTiers (0.23s)
queue_integration_test.go:22: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestARebuildOfACommitAsksWhatTheModuleFollows (0.27s)
queue_integration_test.go:429: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestARecordedModulesMoveThatRecreatesAContainerWaits (0.45s)
--- FAIL: TestARecordedModulesMoveThatRecreatesAContainerWaits/image (0.21s)
recorded_moves_test.go:231: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestARecordedModulesMoveThatRecreatesAContainerWaits/spec (0.24s)
recorded_moves_test.go:231: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAFailedReleaseIsPutBackAndTheNextWaitsForAPerson (0.23s)
release_test.go:231: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestReplay325 (0.37s)
replay325_test.go:23: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestReplay401 (0.32s)
replay401_test.go:20: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestReplaySilentWebAppIsRaisedWithinTwoLooks (0.21s)
replays_integration_test.go:269: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAWalkTakesOverTheReadingsOfAGateJudgingTheSameBuildThere (0.21s)
rest_at_once_integration_test.go:101: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAStoreThatCannotBeReadIsNotANodeThatDoesNotCompose (0.21s)
roster_failure_test.go:35: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAModulePulledInIsHandedOnAMachineThatCanTakeItAndMirrored (0.23s)
sent_required_by_integration_test.go:17: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestASettingsWalkFailsOnARefusalThatCannotClear (0.21s)
settings_walk_integration_test.go:400: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestOnlyATrustedFilesNamedKeyIsRefusedThroughAVerb (0.23s)
terminal_settings_test.go:353: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAnAssignmentSaysOnlyWhatItChangedOnItsOwnNode (0.22s)
unheld_report_integration_test.go:13: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAcceptForAProviderTakesThePathOfTheProvidersModule (0.24s)
vault_switch_test.go:151: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAWalkLetGoAndStoppedByVerbsIsSaidStartedAndEnded (0.23s)
walk_said_integration_test.go:20: the builds are not laid out under their modules yet; the controller's start does it and says so
FAIL github.com/novox/mesh-controller/cmd/mesh-controller 24s (shard 3 of 8: 140 tests)
--- FAIL: TestTheRegistryTrustAndEveryImageFollowThePortTheNodeGaveTheStore (0.33s)
addresses_integration_test.go:17: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestATakeIsRefusedOnAChangedPreviewOrAStaleAccount (0.33s)
adopting_test.go:201: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAssigningWaitsForWhateverIsConvergingTheNode (0.31s)
adopting_test.go:618: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestASearchStillRunningAfterARestartIsNotUrgent (0.32s)
agent_account_integration_test.go:99: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAGivenSecretUnderAnOldKeyIsNotForeseen (0.30s)
awaiting_push_integration_test.go:105: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAMergeRestartsTheWindowAndTheMaximumClosesIt (0.32s)
batches_integration_test.go:144: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestALateMergeOfAOneModuleRepositoryIsNamed (0.31s)
batches_integration_test.go:469: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAnUnrelatedBatchWalksBesideAnOpenWalk (0.29s)
beside_test.go:16: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAtTheTerminalAnotherRepositoryIsRegistered (0.27s)
build_source_integration_test.go:91: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAnUnknownIdentityKeepsTheRecordedOne (0.30s)
build_source_integration_test.go:275: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestOneReadOfAnAssignmentNamesItsCommitBuildAndRolloutAndOneReadOfTheRolloutListsItsAssignments (0.24s)
chain_integration_test.go:26: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAReusedCheckBuildIsRegisteredByItsDigestAndGatedAsABuiltOne (0.31s)
check_builds_integration_test.go:39: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAMemberOfAGroupOfAnOlderMeshDeliveryKeepsItsOwnGate (0.29s)
composed_member_check_test.go:56: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAPlacementOnlyApprovalRaisedBeforeTheMoveIsSetAfterIt (0.34s)
config_moved_integration_test.go:442: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAWalkLetGoByAVerbIsSaidAsPlanMoved (0.31s)
delivery_integration_test.go:152: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestNothingIsComposedOrSentWithoutTheLease (0.25s)
epoch_send_test.go:87: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestACarriedPassCarriesOnlyItsOwnWait (0.26s)
gate_followup_test.go:131: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestALeafModulePassesOnOneHealthyReading (0.30s)
gate_integration_test.go:280: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAGroupWithAMemberOfEachKindIsOneBatchAndOneWalk (0.52s)
--- FAIL: TestAGroupWithAMemberOfEachKindIsOneBatchAndOneWalk/controller_member_first (0.25s)
group_one_batch_test.go:52: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAGroupWithAMemberOfEachKindIsOneBatchAndOneWalk/catalogue_member_first (0.27s)
group_one_batch_test.go:52: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestH1AsksAMachineToReportAndSendsItAgain (0.24s)
healers_integration_test.go:22: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAReportedHostVersionIsKeptAndReadBack (0.29s)
hosts_behind_integration_test.go:11: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestReplay201 (0.29s)
issue201_integration_test.go:69: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestReplay352 (0.45s)
--- FAIL: TestReplay352/a_newer_send_to_the_judged_machine_does_not_unreport_the_gate's (0.23s)
issue352_integration_test.go:27: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestReplay352/a_send_that_moves_the_module_supersedes_the_judging (0.21s)
issue352_integration_test.go:106: the builds are not laid out under their modules yet; the controller's start does it and says so
… 500 more line(s) naming what failed, past the 400 lines or 32 KiB kept
**Merge check** at `0b4cd46b`
Judged: head `0b4cd46b3f04` merged into trunk `da6d038e07c0`; read beside it: mesh-catalog `7f77ce663a9e`, mesh-controller-main `da6d038e07c0`, mesh-host `6469e8238443`, mesh-tools `7412c5b6c9c5`
- `mesh/merge-gate`: **ERROR** — the mesh as it is could not be raised, so the change cannot be judged against it (4 of 4 machines compose on the mesh and not in the gate); the first: a machine (f35) composes on the mesh and not as the gate raised it from the snapshot: the private network cannot be computed: whether f35 answers "mesh-addressing" cannot be read: this kind of record lives on the bus, and this process has not opened the bus: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus (modules: mesh-controller)
- `mesh/repo-check`: **FAIL** — its merge-check.sh failed: --- FAIL: TestAnAssignmentThatBlocksAnotherMachineSaysWhichAndWhy (0.34s); and TestConvergingIsRefusedOnAPreviewThatWouldBeStale, TestTheFlipHoldsTheNodeWhileItSends, TestAPlanCutFromAMergeOfABackedUpModuleAsksItsBackupAndNotItsTierUntilItIsDone, TestAFailedWalkWalksItsEarlierMergesAlone, TestARepositoryMadeAgainUnderItsNameIsNotTheModulesSource and 395 more
**Delivery plan** — builds mesh-controller → novox; no bus step
- tier 0: mesh-controller
- novox: receives mesh-controller
- read by no module's build: cmd/mesh-controller/chain_integration_test.go, cmd/mesh-controller/chain_no_table_integration_test.go, cmd/mesh-controller/pending_integration_test.go, cmd/mesh-controller/pending_test.go, cmd/mesh-controller/plan_moved_every_writer_test.go, cmd/mesh-controller/record_mirrors_switch_test.go, cmd/mesh-controller/sent_required_by_integration_test.go, internal/chain/pending_test.go, internal/inventory/chain_assignments_key_test.go, internal/inventory/chain_builds_layout_test.go, internal/inventory/chain_drop_test.go, internal/inventory/chain_move_test.go, internal/inventory/chain_moved_test.go, internal/inventory/chain_pending_test.go, internal/inventory/chain_rollouts_test.go, internal/inventory/chain_sent_copy_test.go, internal/inventory/chain_sent_test.go, internal/inventory/chain_source_test.go, internal/inventory/chain_store_test.go, internal/inventory/mirrored_test.go, internal/inventory/pin_completed_test.go, internal/inventory/sent_builds_test.go, internal/inventory/sent_plans_test.go, internal/recordmirror/mirror_store_test.go, testdata/store-tests
Run by the build seat on ace as `build-1792323739962081324` (`builds --log build-1792323739962081324`).
```
vault_secrets_integration_test.go:23: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAcceptForAMovedTrustedModuleAnnouncesBeforeTheVaultIsAsked (0.26s)
vault_switch_test.go:340: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAWalkRestartedByARebuildIsSaidStarted (0.24s)
walk_said_integration_test.go:210: the builds are not laid out under their modules yet; the controller's start does it and says so
FAIL
FAIL github.com/novox/mesh-controller/cmd/mesh-controller 15s (shard 8 of 8: 139 tests)
ok github.com/novox/mesh-controller/internal/inventory 16s (shard 1 of 4: 89 tests)
builds: the pointer alpha.newest was missing or wrong (a lookup of alpha.commit.c4) and is repaired from the records of alpha
builds: the pointer alpha.worked was missing or wrong (a lookup of alpha.commit.c4) and is repaired from the records of alpha
builds: the pointer alpha.held was missing or wrong (a lookup of alpha.commit.c4) and is repaired from the records of alpha
builds: the pointer alpha.commit.c4 was missing or wrong (a lookup of alpha.commit.c4) and is repaired from the records of alpha
builds: the pointer alpha.source.v1-s4 was missing or wrong (a lookup of alpha.commit.c4) and is repaired from the records of alpha
builds: the pointer alpha.commit.c2 was missing or wrong (a lookup of alpha.commit.c2) and is repaired from the records of alpha
--- FAIL: TestAPendingAssignmentIsAKeyOfTheAssignmentsBucket (0.16s)
chain_pending_test.go:57: known map[p-1792323830140566939:true p-1792323830146532820:true]: the key holds the newer one now
FAIL
FAIL github.com/novox/mesh-controller/internal/inventory 12s (shard 2 of 4: 89 tests)
--- FAIL: TestThePlansAreKeptInTheAssignmentsValuesAndNothingElseOfThemMoves (0.17s)
chain_store_test.go:314: dunst's value is {Node:anchor Module:dunst Assigned:2026-10-18 11:43:50.485416876 +0000 UTC RequiredBy: Provisioning:[123 34 116 101 109 112 108 97 116 101 115 34 58 123 34 115 111 117 114 99 101 34 58 34 104 116 116 112 58 47 47 115 116 111 114 101 58 53 48 48 48 47 118 50 47 100 117 110 115 116 47 102 105 108 101 115 47 98 108 111 98 115 47 115 104 97 50 53 54 58 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 34 44 34 100 105 103 101 115 116 34 58 34 115 104 97 50 53 54 58 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 34 125 44 34 102 105 108 101 115 34 58 91 123 34 105 100 34 58 34 99 111 110 102 105 103 117 114 97 116 105 111 110 34 44 34 112 97 116 104 34 58 34 47 104 111 109 101 47 111 112 47 46 99 111 110 102 105 103 47 100 117 110 115 116 47 100 117 110 115 116 114 99 34 44 34 116 101 109 112 108 97 116 101 34 58 34 100 117 110 115 116 114 99 34 44 34 111 119 110 101 114 45 97 116 45 114 117 110 116 105 109 101 34 58 34 111 119 110 101 100 34 44 34 116 97 107 101 115 34 58 34 114 101 108 111 97 100 45 111 110 34 125 93 125] Build: Artifact: Package:<nil> Commit: Rollout: Since:0001-01-01 00:00:00 +0000 UTC Ended:0001-01-01 00:00:00 +0000 UTC State: Pending:<nil> PulledIn:false SentUnknown:2026-10-18 11:43:50.492705524 +0000 UTC}
FAIL
FAIL github.com/novox/mesh-controller/internal/inventory 13s (shard 3 of 4: 88 tests)
ok github.com/novox/mesh-controller/internal/inventory 15s (shard 4 of 4: 88 tests)
ok github.com/novox/mesh-controller/internal/builder 14s (shard 1 of 4: 54 tests)
ok github.com/novox/mesh-controller/internal/builder 16s (shard 2 of 4: 53 tests)
ok github.com/novox/mesh-controller/internal/builder 24s (shard 3 of 4: 53 tests)
ok github.com/novox/mesh-controller/internal/builder 15s (shard 4 of 4: 53 tests)
ok github.com/novox/mesh-controller/internal/link 22s (shard 1 of 4: 50 tests)
ok github.com/novox/mesh-controller/internal/link 15s (shard 2 of 4: 50 tests)
ok github.com/novox/mesh-controller/internal/link 17s (shard 3 of 4: 49 tests)
ok github.com/novox/mesh-controller/internal/link 23s (shard 4 of 4: 49 tests)
integration level (the whole suite, tag integration): 3404 tests (6 skipped outside the shards), 62 s
nested module modules/build-agent:
ok build-agent 1.012s
nested module modules/route-proxy:
ok route-proxy/cmd/route-provider 1.011s
nested modules: 3 s
store tests, each run against the store:
./cmd/mesh-controller --- FAIL: TestAStopWithoutAMergeWalksTheOthersAgain (0.14s)
./cmd/mesh-controller --- FAIL: TestAStopWithoutAMergeEndsTheMergesThatContainIt (0.14s)
./cmd/mesh-controller --- FAIL: TestAStopWalksTheOthersAgainInTheOpenBatch (0.14s)
./cmd/mesh-controller --- FAIL: TestAStopNamesWhatStaysOnTheMachinesAndWhatStillCarriesIt (0.12s)
./cmd/mesh-controller --- FAIL: TestAStopWithoutAMergeLeavesItOutOfABatch (0.13s)
./cmd/mesh-controller --- FAIL: TestSavingPlansAndMovingMergesIsOneAct (0.16s)
./cmd/mesh-controller --- FAIL: TestAPlanFollowedFromTheStoreAnswersWhenItMoves (0.23s)
./cmd/mesh-controller --- FAIL: TestIssue969TheGateRaisesEachMachineAsItsEngineStatedItself (0.19s)
./cmd/mesh-controller --- FAIL: TestNodeShowAndStatusReadTheLastSendFromTheStore (0.20s)
./cmd/mesh-controller --- PASS: TestTheConditionsVerbReadsTheLooksTheBucketNoLongerHolds (0.13s)
./cmd/mesh-controller --- FAIL: TestAWalkLetGoAndStoppedByVerbsIsSaidStartedAndEnded (0.19s)
./cmd/mesh-controller --- FAIL: TestAWalkStoppedOrClosedByAPersonIsSaidEndedStopped (0.21s)
./cmd/mesh-controller --- FAIL: TestAWalkRetriedByAPersonIsSaidStartedAgain (0.17s)
./cmd/mesh-controller --- FAIL: TestABacklogReleasedByAPersonIsSaidStarted (0.17s)
./cmd/mesh-controller --- FAIL: TestAWalkEndedByCancelOrClearIsSaidEnded (0.21s)
./cmd/mesh-controller --- FAIL: TestAWalkRestartedByARebuildIsSaidStarted (0.18s)
./cmd/mesh-controller --- FAIL: TestAWalkStoppedByHandAndRetriedEndsFailedWhenItFailsAgain (0.26s)
./cmd/mesh-controller --- FAIL: TestReplay237 (0.19s)
./cmd/mesh-controller --- FAIL: TestAnUnassignThatLeavesItsNodeUnresolvedSaysSoOnceInItsAnswer (0.19s)
./cmd/mesh-controller --- FAIL: TestAnUnassignThatLeavesItsNodeResolvedSaysNothingOfIt (0.25s)
./cmd/mesh-controller --- FAIL: TestAnAssignThatLeavesItsNodeUnresolvedSaysOnlyThePlansRefusal (0.24s)
./cmd/mesh-controller --- FAIL: TestADirectoryOwnersKeyIsRefusedThroughAVerb (0.20s)
./cmd/mesh-controller --- FAIL: TestTheSendMakesNoValueForAnOutsideSecretNobodyGave (0.23s)
./cmd/mesh-controller --- FAIL: TestAQuestionComposesWithoutAnOutsideSecretNobodyGave (0.29s)
./cmd/mesh-controller --- FAIL: TestReplay201 (0.18s)
./cmd/mesh-controller --- FAIL: TestARollbackWhoseSendWasRefusedIsCompletedByTheNextSend (0.15s)
./cmd/mesh-controller --- FAIL: TestAGateJudgesTheOtherMovesBesideAKeptCore (0.14s)
./cmd/mesh-controller --- FAIL: TestReplay401 (0.23s)
./cmd/mesh-controller --- FAIL: TestReplay201ThePlansSend (0.18s)
./cmd/mesh-controller --- FAIL: TestPlanAndNodeListAnOptionalRequirementLeftUnbound (0.18s)
./cmd/mesh-controller --- FAIL: TestReplay340 (0.18s)
./cmd/mesh-controller --- FAIL: TestOnlyATrustedFilesNamedKeyIsRefusedThroughAVerb (0.20s)
./cmd/mesh-controller --- FAIL: TestReplay349 (0.26s)
./cmd/mesh-controller --- FAIL: TestReplay348AFaultFromBeforeTheSendFailsNoGate (0.28s)
./cmd/mesh-controller --- FAIL: TestReplay239AModuleNameIsNotTakenOverByAnotherRepository (0.22s)
./cmd/mesh-controller --- FAIL: TestAWalkThatMovedNothingSaysWhichModulesMatchedWhatRuns (0.14s)
./cmd/mesh-controller --- FAIL: TestAWalkWhoseEveryBuildCameOutTheSameIsDone (0.17s)
./cmd/mesh-controller --- PASS: TestReplay614ANewSDKPlansTheToolchainAndThenItsBundles (0.13s)
./cmd/mesh-controller --- FAIL: TestOneAcceptForAProviderIsPlacedForEveryConsumer (0.21s)
./cmd/mesh-controller --- FAIL: TestReplay164 (0.21s)
./cmd/mesh-controller --- FAIL: TestAnApprovedLayerOpensTheWalkThatSendsIt (0.16s)
./cmd/mesh-controller --- FAIL: TestASettingsWalkSendsOneMachineAtATimeEachJudged (0.19s)
./cmd/mesh-controller --- FAIL: TestAFailedSettingsWalkStopsAndHoldsNothingBack (0.17s)
./cmd/mesh-controller --- FAIL: TestASettingsWalkSendsTheLayerAloneEveryBuildKept (0.17s)
./cmd/mesh-controller --- FAIL: TestASettingsWalkStopsBeforeADataMoveAndPassesOverAMachineAway (0.19s)
./cmd/mesh-controller --- FAIL: TestACrossingSendSupersedesASettingsGate (0.17s)
./cmd/mesh-controller --- FAIL: TestASettingsWalkFailsOnARefusalThatCannotClear (0.17s)
./cmd/mesh-controller --- FAIL: TestAProviderElsewhereServesItsOwnComposedName (0.20s)
./cmd/mesh-controller --- FAIL: TestAReusedCheckBuildIsRegisteredByItsDigestAndGatedAsABuiltOne (0.12s)
./cmd/mesh-controller --- FAIL: TestTheMergeGateJudgesEachManifestAgainstTheListOfTheTree (0.24s)
./cmd/mesh-controller --- FAIL: TestRegistrationPublishesTheNewestTrunkListAndJudgesEveryModuleAgainstIt (0.25s)
./cmd/mesh-controller --- FAIL: TestADeclarationIsTheSameAfterPlacementMoves (0.27s)
./cmd/mesh-controller --- FAIL: TestAReleaseSendsTheRestAtOnceAfterTheFirstPasses (0.18s)
./cmd/mesh-controller --- FAIL: TestARestMachineThatFailsIsPutBackAloneAndTheOthersAreJudgedOn (0.20s)
./cmd/mesh-controller --- FAIL: TestAWalkTakesOverTheReadingsOfAGateJudgingTheSameBuildThere (0.19s)
./cmd/mesh-controller --- FAIL: TestAFirstSendMadeAndNotKeptIsNotSentAgain (0.19s)
./cmd/mesh-controller --- FAIL: TestAReleaseSendKeptAndMadeIsNotMadeAgain (0.19s)
./cmd/mesh-controller --- FAIL: TestAFirstMachineThatFailsStillStopsTheWalk (0.16s)
./cmd/mesh-controller --- FAIL: TestTheControlNodeIsSentLastInAStep (0.16s)
./cmd/mesh-controller --- FAIL: TestARestMachineSilentPastItsBoundIsLeftAndSaid (0.17s)
./cmd/mesh-controller --- FAIL: TestANoMoveTierWaitsForNoNewReport (0.15s)
./cmd/mesh-controller --- FAIL: TestOneProviderDownAndThreeConsumersFailingAreOneCondition (0.20s)
./cmd/mesh-controller --- FAIL: TestAConsumerFailingBesideAHealthyProviderIsItsOwn (0.32s)
./cmd/mesh-controller --- FAIL: TestTheProvisionerClientsAccountIsIssuedForItsServiceAndNeverInvented (0.41s)
./cmd/mesh-controller --- FAIL: TestAcceptOfAnOwnSecretTakesThePathOfItsModulesForm (0.16s)
./cmd/mesh-controller --- FAIL: TestAcceptForAProviderTakesThePathOfTheProvidersModule (0.16s)
./cmd/mesh-controller --- FAIL: TestAcceptForAMovedTrustedModuleAnnouncesBeforeTheVaultIsAsked (0.16s)
./cmd/mesh-controller --- FAIL: TestAcceptForAMovedModuleRecordsAHandActAndNeverTheValue (0.18s)
./cmd/mesh-controller --- FAIL: TestAcceptOfAnOutsideOfferTakesThePathOfTheProvidersModule (0.15s)
./cmd/mesh-controller --- FAIL: TestAnAskAtTheDeskTakesThePathOfItsModulesForm (0.23s)
./cmd/mesh-controller --- FAIL: TestAnIssuedValueTakesThePathOfItsProvidersModule (0.25s)
./cmd/mesh-controller --- FAIL: TestARotationTakesThePathOfItsModulesForm (0.24s)
./cmd/mesh-controller --- FAIL: TestADeclarationIsTheSameWhileTheWordsAreStillInTheLayers (0.23s)
./cmd/mesh-controller --- FAIL: TestADeclarationIsTheSameAfterTheMoveOfPlacement (0.26s)
./cmd/mesh-controller --- FAIL: TestTheSendSealsNoSecretOfAModuleHandedThere (0.18s)
./cmd/mesh-controller --- FAIL: TestAModulesSecretsAreTheVaultsOnceItIsMarkedMoved (0.18s)
./cmd/mesh-controller --- FAIL: TestEveryMachineIsToldTheSameAfterTheMoveOfConfig (0.13s)
./cmd/mesh-controller --- FAIL: TestTheMoveOfConfigRefusesWhatWouldChangeAMachine (0.13s)
./cmd/mesh-controller --- FAIL: TestTheSettingsVerbForwardsToConfigOnceTheValuesMoved (0.19s)
./cmd/mesh-controller --- FAIL: TestTheSendCarriesTheVaultsBoxForACoreCredentialAndKeepsIt (0.23s)
./cmd/mesh-controller --- FAIL: TestASilentVaultHoldsTheKeptBoxAndSaysSo (0.24s)
./cmd/mesh-controller --- FAIL: TestACoreModuleFirstPlacedWhileTheVaultIsSilentIsSealedByTheController (0.23s)
./cmd/mesh-controller --- FAIL: TestAnEngineBelowTheContractIsSentTheControllersSealAsBefore (0.23s)
./cmd/mesh-controller --- FAIL: TestModuleIssueHandsACoveredAccountToTheVaultAndOnlyThat (0.20s)
./cmd/mesh-controller --- FAIL: TestModuleIssueFailsWhenTheVaultDoesNotTakeACoveredAccount (0.18s)
./cmd/mesh-controller --- FAIL: TestModuleIssueBeforeTheVaultIsInstalledKeepsTheValueAndHandsNothing (0.23s)
./cmd/mesh-controller --- FAIL: TestARecordedModulesBundleOnlyMoveRollsOutInItsWalk (0.37s)
./cmd/mesh-controller --- FAIL: TestARecordedModulesMoveThatRecreatesAContainerWaits (0.75s)
./cmd/mesh-controller --- FAIL: TestARecordedModulesMoveThatTouchesDataOrAProviderWaits (1.03s)
./cmd/mesh-controller --- FAIL: TestAPersonsRecordAndTheBusHoldEveryMove (0.46s)
./cmd/mesh-controller --- FAIL: TestARecordedMoveThatCannotBeJudgedWaits (0.19s)
./cmd/mesh-controller --- FAIL: TestReplay867 (0.20s)
./cmd/mesh-controller --- FAIL: TestReplay867Recheck (0.19s)
./cmd/mesh-controller --- FAIL: TestTheRecheckVerbAsksMeshDeliveryOnABusOfItsOwn (0.24s)
./cmd/mesh-controller --- FAIL: TestAssigningTheClientIssuesItsAccount (0.54s)
./cmd/mesh-controller --- FAIL: TestAnUnrelatedBatchWalksBesideAnOpenWalk (0.22s)
./cmd/mesh-controller --- FAIL: TestARelatedBatchWaitsBehindTheOpenWalk (0.13s)
./cmd/mesh-controller --- FAIL: TestAnOwnPathBatchNeverWalksBeside (0.12s)
./cmd/mesh-controller --- FAIL: TestMergesHeardWhileAnotherHolderHasThePlansAreRecordedAndCarried (0.22s)
./cmd/mesh-controller --- FAIL: TestABatchWindowClosesByTheExpiryOfItsKey (0.18s)
./cmd/mesh-controller --- FAIL: TestEveryMoveAMergeAndTheCutMakeOfAPlanIsSaid (0.35s)
./cmd/mesh-controller --- FAIL: TestARolloutAdvancesOnEventsAndAReplacedControllerResumesIt (0.17s)
./cmd/mesh-controller --- FAIL: TestAWalkLetGoByTheDeliverVerbIsAskedWithNoOtherEvent (0.17s)
./cmd/mesh-controller --- FAIL: TestTwoMergesWithinAMinuteLeaveEachOpenPullRequestOneQueuedCheck (0.12s)
./cmd/mesh-controller --- FAIL: TestADeliveryGroupMovingAModuleMachinesRunPassesTheGate (0.15s)
./cmd/mesh-controller --- FAIL: TestAModuleMovesOnTheOperatorsApproveOfTheMergeThatMovedIt (0.12s)
./cmd/mesh-controller --- FAIL: TestAModuleBuiltFromANewRepositoryIsRegisteredOnlyOnTheOperatorsApproveOnTheBus (0.32s)
./cmd/mesh-controller --- FAIL: TestAMergeWhosePlanCannotBeSavedIsHeldAndRecordedWhenHandedOverAgain (0.15s)
./cmd/mesh-controller --- FAIL: TestOneReadOfAnAssignmentNamesItsCommitBuildAndRolloutAndOneReadOfTheRolloutListsItsAssignments (0.13s)
./cmd/mesh-controller --- FAIL: TestASendOfWhatAMachineRunsAlreadyChangesNoLinkOfItsAssignment (0.12s)
./cmd/mesh-controller --- FAIL: TestAnAssignmentWaitingForItsBuildIsOneKeyOfTheAssignmentsBucket (0.12s)
./cmd/mesh-controller --- FAIL: TestNoTableOfTheControllersStoreHoldsBuildsRolloutsOrAssignments (0.12s)
./cmd/mesh-controller FAIL: go test exited 1
./internal/inventory --- PASS: TestTheLastSendSaysWhatTheMachineAnswered (0.08s)
./internal/inventory --- PASS: TestAReportIsTheLastSendsAnswerOnlyWhenItIsAboutThatSend (0.08s)
./internal/inventory --- PASS: TestAnIssuedValueIsSealedToEveryHolderOnceAndNotAgain (0.17s)
./internal/inventory --- PASS: TestAnIssuedValueIsSealedAgainAfterAKeyChangeOrAnAcceptance (0.15s)
./internal/inventory --- PASS: TestAConditionsLooksAreKeptBesideTheBucket (0.12s)
./internal/inventory --- PASS: TestAPlanIdHoldingAQuoteIsReadAsAPlainId (0.08s)
./internal/inventory --- PASS: TestAWalksStartIsKeptAndARefusedSaveLeavesItUnsaid (0.06s)
./internal/inventory --- PASS: TestAWalksRestIsReadFromEachMachinesOwnSend (0.07s)
./internal/inventory --- PASS: TestAStoredBuildWithASilentMergeableFileIsStillReadAndComposed (0.06s)
./internal/inventory --- PASS: TestACredentialIssuedOutsideIsNeverMade (0.14s)
./internal/inventory --- PASS: TestOneAcceptForAProviderIsSealedToEveryConsumer (0.14s)
./internal/inventory --- PASS: TestASharedOwnSecretIssuedOutsideIsNeverMade (0.13s)
./internal/inventory --- PASS: TestAModuleInTheConfigFormIsMirroredWithItsWholeDeclaration (0.07s)
./internal/inventory --- PASS: TestAReportOfABusyContainerIsKeptAndReadBack (0.08s)
./internal/inventory --- PASS: TestANewerBuildsListReplacesTheKeptOneAndAnOlderOneHeardLaterDoesNot (0.09s)
./internal/inventory --- PASS: TestPlacementMovesOutOfTheSettingsLayers (0.40s)
./internal/inventory --- PASS: TestASettingRoutesPlacementBesideTheLayer (0.09s)
./internal/inventory --- PASS: TestTheProvisionerClientsMachineHasAnAccountOfItsOwn (0.12s)
./internal/inventory --- PASS: TestTheFourWordsAreKeptBesideTheLayer (0.09s)
./internal/inventory --- PASS: TestALayerStillHoldingTheWordsReadsThemAsPlacement (0.08s)
./internal/inventory --- PASS: TestTheMoveOfPlacementMovesWhatTheLayersStillHold (0.10s)
./internal/inventory --- PASS: TestTheMoveReadsEveryRowSealedToAMachineAsItIs (0.09s)
./internal/inventory --- PASS: TestASendKeepsThePlansItHandedAndTheMirrorCarriesThem (0.08s)
./internal/inventory --- PASS: TestTheLayersAreReadUntilTheMoveOfConfigHasRun (0.09s)
./internal/inventory --- PASS: TestAModuleReadsMeshConfigOnlyWhereItsValuesAre (0.08s)
./internal/inventory --- PASS: TestTheEndOfTheMoveRefusesALayerChangedSinceItWasRead (0.14s)
./internal/inventory --- PASS: TestACoreCredentialsVaultBoxIsKeptPerMachineAndReplaced (0.10s)
./internal/inventory --- PASS: TestWhatRunsIsTheRegisteredBuildNotANewerOnePutBack (0.07s)
./internal/inventory --- PASS: TestBuildsOnTheBusAreReadBackByEveryReader (0.07s)
./internal/inventory --- PASS: TestARequestIsTheBuildInStateAskedAndItsOutcomeTakesItsPlace (0.06s)
./internal/inventory --- PASS: TestAnAssignmentIsAKeyOfTheBucketAndAnUnassignmentEndsIt (0.10s)
./internal/inventory --- FAIL: TestThePlansAreKeptInTheAssignmentsValuesAndNothingElseOfThemMoves (0.09s)
./internal/inventory --- FAIL: TestAPendingAssignmentIsAKeyOfTheAssignmentsBucket (0.07s)
./internal/inventory --- PASS: TestARecordedPendingIsSkippedByAssignedAndTheJoins (0.07s)
./internal/inventory --- PASS: TestTwoClaimsOfOnePendingMakeOneAndTheOtherSeesFalse (0.08s)
./internal/inventory --- PASS: TestAssignOverAPendingKeepsItsRecordAsApplied (0.07s)
./internal/inventory --- PASS: TestAPendingIsMarkedOnceAndGoesWithItsMachine (0.08s)
./internal/inventory --- PASS: TestAReplacedWaitNeverLeavesTheOperatorWithoutItsCondition (0.06s)
./internal/inventory --- PASS: TestSentBuildsAnswersFromTheAssignmentsKeysOfTheNode (0.08s)
./internal/inventory --- PASS: TestASendReplacesTheWholeMapOfTheNodeAndAHandSendMakesItUnknown (0.08s)
./internal/inventory --- PASS: TestAFailedWriteOfTheLinksFailsTheRecordOfTheSend (0.07s)
./internal/inventory --- PASS: TestMigration0105RefusesAStoreWhoseRowsWereNotMovedAndDropsTheTablesOfAMovedOne (0.38s)
./internal/inventory --- PASS: TestMigration0105PassesAStoreThatNeverHeldARow (0.09s)
./internal/inventory --- PASS: TestTheColumnOfASentMachineIsCopiedOntoItsKeysAndEmptied (0.07s)
./internal/inventory --- PASS: TestASendEmptiesTheColumnSoALaterCopyLeavesAClearedKeyBare (0.09s)
./internal/inventory FAIL: go test exited 1
./internal/recordmirror --- PASS: TestNatsAnAssignmentAndARegistrationEachChangeOneKeyAndRaiseOneEvent (2.20s)
./internal/recordmirror --- PASS: TestNatsTheListOfPredefinedKeysKeptChangesTheMirrorsOneKey (1.49s)
114 store test(s) listed in testdata/store-tests did not run and pass against the store
--- what failed, picked from the whole of its output (the whole is in the build's log)
--- FAIL: TestAnAssignmentThatBlocksAnotherMachineSaysWhichAndWhy (0.34s)
acts_test.go:27: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestConvergingIsRefusedOnAPreviewThatWouldBeStale (0.34s)
adopting_test.go:134: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestTheFlipHoldsTheNodeWhileItSends (0.31s)
adopting_test.go:502: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAPlanCutFromAMergeOfABackedUpModuleAsksItsBackupAndNotItsTierUntilItIsDone (0.25s)
backups_before_send_integration_test.go:226: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAFailedWalkWalksItsEarlierMergesAlone (0.31s)
batches_integration_test.go:341: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestARepositoryMadeAgainUnderItsNameIsNotTheModulesSource (0.30s)
build_source_integration_test.go:214: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestASendAssertsWhatWasAssignedAfterStart (0.31s)
busobjects_test.go:84: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestNoTableOfTheControllersStoreHoldsBuildsRolloutsOrAssignments (0.29s)
chain_no_table_integration_test.go:18: the builds are not laid out under their modules yet; the controller's start does it and says so
the checks' builds of 1 pull request(s) could not be read, so the walk builds: no bus
--- FAIL: TestTwoMergesWithinAMinuteLeaveEachOpenPullRequestOneQueuedCheck (0.28s)
checks_queue_test.go:25: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestTheMoveOfConfigRefusesWhatWouldChangeAMachine (0.30s)
config_moved_integration_test.go:262: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAnEngineBelowTheContractIsSentTheControllersSealAsBefore (0.28s)
core_box_integration_test.go:121: the builds are not laid out under their modules yet; the controller's start does it and says so
novox/mesh-catalog changed more files than were listed: the manifests of its modules (modules/a/module.json) are read as changed
novox/mesh-catalog changed more files than were listed: the manifests of its modules (modules/a/module.json) are read as changed
--- FAIL: TestAMachineWhoseDeclarationDoesNotComposeIsSaid (0.27s)
doctor_integration_test.go:127: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestABuildThatFailsItsGateIsRolledBackOnItsFirstMachineAndGoesNoFurther (0.28s)
gate_integration_test.go:142: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestNatsH3AssertsAMissingConsumerAgainAndBrakesAfterItsBudget (0.28s)
healers_integration_test.go:253: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestANamedPushStillSendsAConsequenceNothingHolds (0.26s)
held_back_integration_test.go:130: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestSavingPlansAndMovingMergesIsOneAct (0.25s)
issue459_integration_test.go:268: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestNodeShowAndStatusReadTheLastSendFromTheStore (0.27s)
last_send_integration_test.go:14: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAMachineSilentPastItsBoundIsLeftAndSaidAtOnce (0.27s)
lean_walk_integration_test.go:95: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestARelatedMergeJoinsTheBatchAndWaitsForTheWindow (1.08s)
--- FAIL: TestARelatedMergeJoinsTheBatchAndWaitsForTheWindow/same_repository (0.25s)
lone_merge_test.go:41: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestARelatedMergeJoinsTheBatchAndWaitsForTheWindow/a_module_in_common (0.32s)
lone_merge_test.go:41: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestARelatedMergeJoinsTheBatchAndWaitsForTheWindow/an_edge_of_the_graph (0.25s)
lone_merge_test.go:41: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestARelatedMergeJoinsTheBatchAndWaitsForTheWindow/the_same_group_head (0.26s)
lone_merge_test.go:41: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestALoneMergeRelatedToAWalkTheCutFoldsJoinsTheBatch (0.24s)
lone_merge_test.go:314: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAFailedUnitIsTheModulesConditionAndTheMachinesOwnAreOneFinding (0.28s)
machine_units_integration_test.go:15: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAManifestTheRunningControllerCannotReadFailsThePullRequest (0.30s)
merge_gate_integration_test.go:124: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestTheResolverIsToldEveryMachineOnTheNetworkAndToldAgainWhenOneLeaves (0.26s)
network_test.go:260: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAskingAboutAMachineTheMeshHasNeverHeardOfIsRefused (0.26s)
nodes_test.go:98: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAnUnassignThatLeavesItsNodeResolvedSaysNothingOfIt (0.27s)
one_resolution_integration_test.go:38: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAStatusReadSettlesNothing (0.25s)
pending_integration_test.go:115: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAnUnknownModuleIsRefusedWithTheClosestNames (0.26s)
pending_integration_test.go:388: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestABuildNoLongerWaitedForIsStillInFlight (0.25s)
pending_integration_test.go:709: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAssigningTheClientIssuesItsAccount (0.28s)
provisioner_account_integration_test.go:55: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAPlanStoppedAtItsFirstMachineIsRetried (0.29s)
queue_integration_test.go:336: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestReplay348AFaultFromBeforeTheSendFailsNoGate (0.22s)
replay348_test.go:27: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestReplay273AConsumerBesideItsStoreStaysBoundToIt (0.24s)
replays_integration_test.go:50: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAReleaseSendsTheRestAtOnceAfterTheFirstPasses (0.27s)
rest_at_once_integration_test.go:40: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAnUnhealthyOwnRuntimeRaisesTheModulesUsualCondition (0.24s)
runtime_health_test.go:17: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestADefinitionMovingUnderAStoredSettingLeavesThatModuleOutNotTheMachine (0.21s)
sendable_integration_test.go:302: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestPreferencesListedFromTheStores (0.26s)
settings_effective_integration_test.go:13: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestASettingsWalkStopsBeforeADataMoveAndPassesOverAMachineAway (0.27s)
settings_walk_integration_test.go:315: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestTheAgentsManagedSettingsAreRefusedThroughAVerb (0.22s)
terminal_settings_test.go:223: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestATierPutsABrokenModuleBackAtOnce (0.49s)
--- FAIL: TestATierPutsABrokenModuleBackAtOnce/gate_kept_on_node-tools (0.21s)
tier_send_integration_test.go:325: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestATierPutsABrokenModuleBackAtOnce/gate_kept_on_app1 (0.28s)
tier_send_integration_test.go:325: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAHeldModuleIsFoundFromWhatTheMachineReported (0.23s)
untaken_integration_test.go:27: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAcceptForAMovedModuleRecordsAHandActAndNeverTheValue (0.24s)
vault_switch_test.go:386: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAWalkStoppedByHandAndRetriedEndsFailedWhenItFailsAgain (0.23s)
walk_said_integration_test.go:233: the builds are not laid out under their modules yet; the controller's start does it and says so
FAIL github.com/novox/mesh-controller/cmd/mesh-controller 15s (shard 1 of 8: 140 tests)
--- FAIL: TestAConsumerAssignedBeforeItsProviderIsStillAssigned (0.34s)
acts_test.go:84: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestTheFlipIsRefusedWhileAFoundContainerIsHeld (0.32s)
adopting_test.go:145: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestThePreviewNamesEveryHeldKind (0.32s)
adopting_test.go:547: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestTheSelfCheckSaysAnAgentAccountThatCanBecomeRoot (0.31s)
agent_account_integration_test.go:18: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAModuleAssignedAndNotPushedIsAwaitingAPushNotUncomposable (0.25s)
awaiting_push_integration_test.go:17: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestTwoMergesSecondsApartAreOneWalkAtTheLaterCommit (0.30s)
batches_integration_test.go:66: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAGroupsOrderBecomesTiersInsideTheWalk (0.31s)
batches_integration_test.go:408: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestABuildFromAnAgentsRepositoryIsNotRegisteredAsAModuleTheMeshHolds (0.29s)
build_source_integration_test.go:39: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestATerminalRequestCoversOnlyWhatItAsked (0.29s)
build_source_integration_test.go:240: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestASendThatCannotAssertTheBusSaysSoAndRaisesACondition (0.29s)
busobjects_test.go:123: the builds are not laid out under their modules yet; the controller's start does it and says so
the earlier checks' builds of novox/shop#7 could not be read, so the check builds: no bus
--- FAIL: TestTheSettingsVerbForwardsToConfigOnceTheValuesMoved (0.30s)
config_moved_integration_test.go:306: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestNatsTheBusIsWhatTheControllerDefines (0.27s)
doctor_integration_test.go:149: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAFaultBeforeTheSettleTimeWaitsForTheModuleBesideIt (0.27s)
gate_followup_test.go:64: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestABuildThatPassesItsGateRollsEverywhereUnattended (0.27s)
gate_integration_test.go:231: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestNatsH4ResetsTheControllersEventsConsumerAndItStillDelivers (0.28s)
healers_integration_test.go:343: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestASecondEligibleHolderStandsBesideTheOneHeldByBeingAlone (0.24s)
holdings_test.go:25: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAnOverflowingConsumerNeverRefusesItsProvidersMachine (0.28s)
identity_bound_integration_test.go:14: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAMergeOfAGroupWaitsEvenAlone (0.24s)
lone_merge_test.go:102: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAModuleAMachineRunsRemovedFromItsSourceFails (0.31s)
merge_gate_integration_test.go:133: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestTheRosterNamesOnlyTheMachines (0.23s)
network_test.go:316: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestANodeAddedAdoptedIsAdopted (0.25s)
nodes_test.go:107: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAnAssignThatLeavesItsNodeUnresolvedSaysOnlyThePlansRefusal (0.22s)
one_resolution_integration_test.go:57: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAPendingAssignmentExpiresWhenItsBuildFails (0.23s)
pending_integration_test.go:138: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAnActWithAModuleNotRegisteredIsRefusedWhole (0.21s)
pending_integration_test.go:412: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestOneProviderDownAndThreeConsumersFailingAreOneCondition (0.25s)
provider_hold_test.go:24: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAPlanIsAnsweredOnlyByTheBuildItAskedFor (0.26s)
queue_integration_test.go:403: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestARecordedModulesBundleOnlyMoveRollsOutInItsWalk (0.23s)
recorded_moves_test.go:187: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestTheBacklogIsReleasedOneMachineAtATimeEachJudged (0.40s)
release_test.go:176: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestReplay318 (0.32s)
replay318_test.go:37: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestReplay349 (0.22s)
replay349_test.go:24: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestReplayCrashLoopFailsItsGateOnTheFirstMachine (0.21s)
replays_integration_test.go:111: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestARestMachineThatFailsIsPutBackAloneAndTheOthersAreJudgedOn (0.22s)
rest_at_once_integration_test.go:66: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestASetThatDoesNotComposeIsMarkedAsTheNodesOwnProblem (0.21s)
roster_failure_test.go:15: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAWalkWhoseEveryBuildCameOutTheSameIsDone (0.21s)
same_program_integration_test.go:17: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestACrossingSendSupersedesASettingsGate (0.22s)
settings_walk_integration_test.go:361: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestTheMergeGateJudgesAChangeToATemplateAlone (0.22s)
template_integration_test.go:47: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAnyKeyOfAModuleWithATrustedMergeableFileIsRefusedThroughAVerb (0.20s)
terminal_settings_test.go:293: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestASendCarryingTheToolRunnerWaitsForItsWitnessWindow (0.21s)
tier_send_integration_test.go:380: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestPlanAndNodeListAnOptionalRequirementLeftUnbound (0.22s)
unbound_test.go:16: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestTheJSONStatusCarriesWhatIsHeldAndForWhichModule (0.21s)
untaken_integration_test.go:43: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAcceptOfAnOwnSecretTakesThePathOfItsModulesForm (0.21s)
vault_switch_test.go:117: the builds are not laid out under their modules yet; the controller's start does it and says so
FAIL github.com/novox/mesh-controller/cmd/mesh-controller 25s (shard 2 of 8: 140 tests)
--- FAIL: TestUnassigningAProviderNamesWhoIsNowBlocked (0.34s)
acts_test.go:105: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestTakingNamesWhatItReplaces (0.32s)
adopting_test.go:157: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestTheFlipIsRefusedOnAnAccountNamingNothingReachable (0.32s)
adopting_test.go:590: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestTheFactsCarryTheAgentAccountAsAPseudonym (0.33s)
agent_account_integration_test.go:68: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestASecretThePushCannotMakeIsStillUncomposable (0.29s)
awaiting_push_integration_test.go:72: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestThreeRepositoriesInOneWindowAreOneWalk (0.32s)
batches_integration_test.go:110: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestABatchSurvivesARestart (0.31s)
batches_integration_test.go:444: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestANewModuleFromARepositoryTheCatalogueDoesNotBuildFromIsNotRegistered (0.29s)
build_source_integration_test.go:71: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestNatsAModuleAssignedAfterStartGetsItsConsumerAtItsFirstSend (0.27s)
busobjects_test.go:165: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAComposedMembersCheckIsItsRepositoryChecksAlone (0.32s)
composed_member_check_test.go:48: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAnApprovalRaisedBeforeTheMoveOfConfigIsRefusedAfterIt (0.32s)
config_moved_integration_test.go:404: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAMergeWaitsForItsDeliverysWordAndThePersonsWordWorksWithoutIt (0.30s)
delivery_integration_test.go:20: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAMachineIsSentTheEpochOnlyOnceItSaysItReadsOne (0.27s)
epoch_send_test.go:30: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAPassIsCountedNoFasterThanTheGatesSpacing (0.22s)
gate_followup_test.go:106: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestABuildRollsToEveryMachineAtOnceWithNoGate (0.28s)
gate_integration_test.go:254: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestTheGrantsStepSendsTheUserListAndNothingElse (0.23s)
grants_step_store_test.go:27: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAGroupsBatchWaitsForItsLastMemberHoweverLongItTakes (0.23s)
group_one_batch_test.go:18: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAHolderOnRecordIsNotRewrittenByDerivation (0.22s)
holdings_test.go:83: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAWalkThatMovedNothingSaysWhichModulesMatchedWhatRuns (0.22s)
issue611_integration_test.go:14: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAHeadedMergeInNoGroupIsCutAtOnce (0.25s)
lone_merge_test.go:134: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestIssue278AWideRebuildIsSaidBeforeTheMerge (0.23s)
merge_gate_integration_test.go:141: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestTwoUnhealthyStatementsRaiseTheModulesConditionAndAHealthyOneClearsIt (0.23s)
module_health_test.go:39: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestPlacingANodeWithNothingSaidDoesNotUnplaceIt (0.25s)
network_test.go:38: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAMergeBuildsTheNewModuleItAdds (0.25s)
new_module_on_merge_test.go:33: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestATokenIssuedAdoptedSaysSoAndReissuingDoesNotConverge (0.26s)
nodes_test.go:128: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestTheConditionClearsWhenTheModuleIsAssignedLater (0.23s)
pending_integration_test.go:205: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestUnassignWithdrawsAPendingAssignment (0.21s)
pending_integration_test.go:427: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestADeclarationIsTheSameAfterPlacementMoves (0.28s)
placement_moved_test.go:24: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAControllerLeavesThePlansToTheOneHoldingThem (0.33s)
plans_one_at_a_time_test.go:16: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAConsumerFailingBesideAHealthyProviderIsItsOwn (0.30s)
provider_hold_test.go:145: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAPushSaysWhatItRecreates (0.21s)
push_recreates_test.go:20: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAFailedPlanIsRetriedAndGoesOnThroughItsLaterTiers (0.23s)
queue_integration_test.go:22: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestARebuildOfACommitAsksWhatTheModuleFollows (0.27s)
queue_integration_test.go:429: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestARecordedModulesMoveThatRecreatesAContainerWaits (0.45s)
--- FAIL: TestARecordedModulesMoveThatRecreatesAContainerWaits/image (0.21s)
recorded_moves_test.go:231: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestARecordedModulesMoveThatRecreatesAContainerWaits/spec (0.24s)
recorded_moves_test.go:231: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAFailedReleaseIsPutBackAndTheNextWaitsForAPerson (0.23s)
release_test.go:231: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestReplay325 (0.37s)
replay325_test.go:23: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestReplay401 (0.32s)
replay401_test.go:20: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestReplaySilentWebAppIsRaisedWithinTwoLooks (0.21s)
replays_integration_test.go:269: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAWalkTakesOverTheReadingsOfAGateJudgingTheSameBuildThere (0.21s)
rest_at_once_integration_test.go:101: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAStoreThatCannotBeReadIsNotANodeThatDoesNotCompose (0.21s)
roster_failure_test.go:35: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAModulePulledInIsHandedOnAMachineThatCanTakeItAndMirrored (0.23s)
sent_required_by_integration_test.go:17: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestASettingsWalkFailsOnARefusalThatCannotClear (0.21s)
settings_walk_integration_test.go:400: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestOnlyATrustedFilesNamedKeyIsRefusedThroughAVerb (0.23s)
terminal_settings_test.go:353: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAnAssignmentSaysOnlyWhatItChangedOnItsOwnNode (0.22s)
unheld_report_integration_test.go:13: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAcceptForAProviderTakesThePathOfTheProvidersModule (0.24s)
vault_switch_test.go:151: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAWalkLetGoAndStoppedByVerbsIsSaidStartedAndEnded (0.23s)
walk_said_integration_test.go:20: the builds are not laid out under their modules yet; the controller's start does it and says so
FAIL github.com/novox/mesh-controller/cmd/mesh-controller 24s (shard 3 of 8: 140 tests)
--- FAIL: TestTheRegistryTrustAndEveryImageFollowThePortTheNodeGaveTheStore (0.33s)
addresses_integration_test.go:17: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestATakeIsRefusedOnAChangedPreviewOrAStaleAccount (0.33s)
adopting_test.go:201: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAssigningWaitsForWhateverIsConvergingTheNode (0.31s)
adopting_test.go:618: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestASearchStillRunningAfterARestartIsNotUrgent (0.32s)
agent_account_integration_test.go:99: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAGivenSecretUnderAnOldKeyIsNotForeseen (0.30s)
awaiting_push_integration_test.go:105: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAMergeRestartsTheWindowAndTheMaximumClosesIt (0.32s)
batches_integration_test.go:144: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestALateMergeOfAOneModuleRepositoryIsNamed (0.31s)
batches_integration_test.go:469: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAnUnrelatedBatchWalksBesideAnOpenWalk (0.29s)
beside_test.go:16: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAtTheTerminalAnotherRepositoryIsRegistered (0.27s)
build_source_integration_test.go:91: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAnUnknownIdentityKeepsTheRecordedOne (0.30s)
build_source_integration_test.go:275: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestOneReadOfAnAssignmentNamesItsCommitBuildAndRolloutAndOneReadOfTheRolloutListsItsAssignments (0.24s)
chain_integration_test.go:26: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAReusedCheckBuildIsRegisteredByItsDigestAndGatedAsABuiltOne (0.31s)
check_builds_integration_test.go:39: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAMemberOfAGroupOfAnOlderMeshDeliveryKeepsItsOwnGate (0.29s)
composed_member_check_test.go:56: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAPlacementOnlyApprovalRaisedBeforeTheMoveIsSetAfterIt (0.34s)
config_moved_integration_test.go:442: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAWalkLetGoByAVerbIsSaidAsPlanMoved (0.31s)
delivery_integration_test.go:152: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestNothingIsComposedOrSentWithoutTheLease (0.25s)
epoch_send_test.go:87: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestACarriedPassCarriesOnlyItsOwnWait (0.26s)
gate_followup_test.go:131: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestALeafModulePassesOnOneHealthyReading (0.30s)
gate_integration_test.go:280: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAGroupWithAMemberOfEachKindIsOneBatchAndOneWalk (0.52s)
--- FAIL: TestAGroupWithAMemberOfEachKindIsOneBatchAndOneWalk/controller_member_first (0.25s)
group_one_batch_test.go:52: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAGroupWithAMemberOfEachKindIsOneBatchAndOneWalk/catalogue_member_first (0.27s)
group_one_batch_test.go:52: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestH1AsksAMachineToReportAndSendsItAgain (0.24s)
healers_integration_test.go:22: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAReportedHostVersionIsKeptAndReadBack (0.29s)
hosts_behind_integration_test.go:11: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestReplay201 (0.29s)
issue201_integration_test.go:69: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestReplay352 (0.45s)
--- FAIL: TestReplay352/a_newer_send_to_the_judged_machine_does_not_unreport_the_gate's (0.23s)
issue352_integration_test.go:27: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestReplay352/a_send_that_moves_the_module_supersedes_the_judging (0.21s)
issue352_integration_test.go:106: the builds are not laid out under their modules yet; the controller's start does it and says so
… 500 more line(s) naming what failed, past the 400 lines or 32 KiB kept
```
Merge check at 0b4cd46b
Judged: head 0b4cd46b3f04 merged into trunk da6d038e07c0; read beside it: mesh-catalog 7f77ce663a9e, mesh-controller-main da6d038e07c0, mesh-host 6469e8238443, mesh-tools 7412c5b6c9c5
mesh/merge-gate: ERROR — the mesh as it is could not be raised, so the change cannot be judged against it (4 of 4 machines compose on the mesh and not in the gate); the first: a machine (f35) composes on the mesh and not as the gate raised it from the snapshot: the private network cannot be computed: whether f35 answers "mesh-addressing" cannot be read: this kind of record lives on the bus, and this process has not opened the bus: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus (modules: build-agent, mesh-controller)
mesh/repo-check: FAIL — its merge-check.sh failed: --- FAIL: TestAnAssignmentThatBlocksAnotherMachineSaysWhichAndWhy (1.02s); and TestConvergingIsRefusedOnAPreviewThatWouldBeStale, TestTheFlipHoldsTheNodeWhileItSends, TestAPlanCutFromAMergeOfABackedUpModuleAsksItsBackupAndNotItsTierUntilItIsDone, TestAFailedWalkWalksItsEarlierMergesAlone, TestARepositoryMadeAgainUnderItsNameIsNotTheModulesSource and 395 more
Delivery plan — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
tier 0: mesh-controller
tier 1: build-agent
ace: receives build-agent
g14: receives build-agent
novox: receives mesh-controller, build-agent
shanks: receives build-agent
build-agent keeps data (ADR 0233): what it holds is backed up before it moves
grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before build-agent is judged on its first machine
Run by the build seat on ace as build-1792323924401214012 (builds --log build-1792323924401214012).
vault_secrets_integration_test.go:23: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAcceptForAMovedTrustedModuleAnnouncesBeforeTheVaultIsAsked (0.24s)
vault_switch_test.go:340: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAWalkRestartedByARebuildIsSaidStarted (0.30s)
walk_said_integration_test.go:210: the builds are not laid out under their modules yet; the controller's start does it and says so
FAIL
FAIL github.com/novox/mesh-controller/cmd/mesh-controller 34s (shard 8 of 8: 139 tests)
ok github.com/novox/mesh-controller/internal/inventory 33s (shard 1 of 4: 89 tests)
builds: the pointer alpha.newest was missing or wrong (a lookup of alpha.commit.c4) and is repaired from the records of alpha
builds: the pointer alpha.worked was missing or wrong (a lookup of alpha.commit.c4) and is repaired from the records of alpha
builds: the pointer alpha.held was missing or wrong (a lookup of alpha.commit.c4) and is repaired from the records of alpha
builds: the pointer alpha.commit.c4 was missing or wrong (a lookup of alpha.commit.c4) and is repaired from the records of alpha
builds: the pointer alpha.source.v1-s4 was missing or wrong (a lookup of alpha.commit.c4) and is repaired from the records of alpha
builds: the pointer alpha.commit.c2 was missing or wrong (a lookup of alpha.commit.c2) and is repaired from the records of alpha
--- FAIL: TestAPendingAssignmentIsAKeyOfTheAssignmentsBucket (0.50s)
chain_pending_test.go:57: known map[p-1792323976701951623:true p-1792323976719378380:true]: the key holds the newer one now
FAIL
FAIL github.com/novox/mesh-controller/internal/inventory 29s (shard 2 of 4: 89 tests)
--- FAIL: TestThePlansAreKeptInTheAssignmentsValuesAndNothingElseOfThemMoves (0.34s)
chain_store_test.go:314: dunst's value is {Node:anchor Module:dunst Assigned:2026-10-18 11:46:17.038645169 +0000 UTC RequiredBy: Provisioning:[123 34 116 101 109 112 108 97 116 101 115 34 58 123 34 115 111 117 114 99 101 34 58 34 104 116 116 112 58 47 47 115 116 111 114 101 58 53 48 48 48 47 118 50 47 100 117 110 115 116 47 102 105 108 101 115 47 98 108 111 98 115 47 115 104 97 50 53 54 58 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 34 44 34 100 105 103 101 115 116 34 58 34 115 104 97 50 53 54 58 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 34 125 44 34 102 105 108 101 115 34 58 91 123 34 105 100 34 58 34 99 111 110 102 105 103 117 114 97 116 105 111 110 34 44 34 112 97 116 104 34 58 34 47 104 111 109 101 47 111 112 47 46 99 111 110 102 105 103 47 100 117 110 115 116 47 100 117 110 115 116 114 99 34 44 34 116 101 109 112 108 97 116 101 34 58 34 100 117 110 115 116 114 99 34 44 34 111 119 110 101 114 45 97 116 45 114 117 110 116 105 109 101 34 58 34 111 119 110 101 100 34 44 34 116 97 107 101 115 34 58 34 114 101 108 111 97 100 45 111 110 34 125 93 125] Build: Artifact: Package:<nil> Commit: Rollout: Since:0001-01-01 00:00:00 +0000 UTC Ended:0001-01-01 00:00:00 +0000 UTC State: Pending:<nil> PulledIn:false SentUnknown:2026-10-18 11:46:17.052630914 +0000 UTC}
FAIL
FAIL github.com/novox/mesh-controller/internal/inventory 29s (shard 3 of 4: 88 tests)
ok github.com/novox/mesh-controller/internal/inventory 31s (shard 4 of 4: 88 tests)
ok github.com/novox/mesh-controller/internal/builder 32s (shard 1 of 4: 54 tests)
ok github.com/novox/mesh-controller/internal/builder 33s (shard 2 of 4: 53 tests)
ok github.com/novox/mesh-controller/internal/builder 34s (shard 3 of 4: 53 tests)
ok github.com/novox/mesh-controller/internal/builder 29s (shard 4 of 4: 53 tests)
ok github.com/novox/mesh-controller/internal/link 29s (shard 1 of 4: 50 tests)
ok github.com/novox/mesh-controller/internal/link 18s (shard 2 of 4: 50 tests)
ok github.com/novox/mesh-controller/internal/link 19s (shard 3 of 4: 49 tests)
ok github.com/novox/mesh-controller/internal/link 30s (shard 4 of 4: 49 tests)
integration level (the whole suite, tag integration): 3404 tests (6 skipped outside the shards), 59 s
nested module modules/build-agent:
ok build-agent 1.014s
nested module modules/route-proxy:
ok route-proxy/cmd/route-provider 1.012s
nested modules: 3 s
store tests, each run against the store:
./cmd/mesh-controller --- FAIL: TestAStopWithoutAMergeWalksTheOthersAgain (0.24s)
./cmd/mesh-controller --- FAIL: TestAStopWithoutAMergeEndsTheMergesThatContainIt (0.16s)
./cmd/mesh-controller --- FAIL: TestAStopWalksTheOthersAgainInTheOpenBatch (0.16s)
./cmd/mesh-controller --- FAIL: TestAStopNamesWhatStaysOnTheMachinesAndWhatStillCarriesIt (0.28s)
./cmd/mesh-controller --- FAIL: TestAStopWithoutAMergeLeavesItOutOfABatch (0.23s)
./cmd/mesh-controller --- FAIL: TestSavingPlansAndMovingMergesIsOneAct (0.24s)
./cmd/mesh-controller --- FAIL: TestAPlanFollowedFromTheStoreAnswersWhenItMoves (0.45s)
./cmd/mesh-controller --- FAIL: TestIssue969TheGateRaisesEachMachineAsItsEngineStatedItself (0.35s)
./cmd/mesh-controller --- FAIL: TestNodeShowAndStatusReadTheLastSendFromTheStore (0.36s)
./cmd/mesh-controller --- PASS: TestTheConditionsVerbReadsTheLooksTheBucketNoLongerHolds (0.14s)
./cmd/mesh-controller --- FAIL: TestAWalkLetGoAndStoppedByVerbsIsSaidStartedAndEnded (0.20s)
./cmd/mesh-controller --- FAIL: TestAWalkStoppedOrClosedByAPersonIsSaidEndedStopped (0.19s)
./cmd/mesh-controller --- FAIL: TestAWalkRetriedByAPersonIsSaidStartedAgain (0.19s)
./cmd/mesh-controller --- FAIL: TestABacklogReleasedByAPersonIsSaidStarted (0.16s)
./cmd/mesh-controller --- FAIL: TestAWalkEndedByCancelOrClearIsSaidEnded (0.63s)
./cmd/mesh-controller --- FAIL: TestAWalkRestartedByARebuildIsSaidStarted (1.29s)
./cmd/mesh-controller --- FAIL: TestAWalkStoppedByHandAndRetriedEndsFailedWhenItFailsAgain (0.71s)
./cmd/mesh-controller --- FAIL: TestReplay237 (0.34s)
./cmd/mesh-controller --- FAIL: TestAnUnassignThatLeavesItsNodeUnresolvedSaysSoOnceInItsAnswer (0.62s)
./cmd/mesh-controller --- FAIL: TestAnUnassignThatLeavesItsNodeResolvedSaysNothingOfIt (0.60s)
./cmd/mesh-controller --- FAIL: TestAnAssignThatLeavesItsNodeUnresolvedSaysOnlyThePlansRefusal (0.42s)
./cmd/mesh-controller --- FAIL: TestADirectoryOwnersKeyIsRefusedThroughAVerb (0.18s)
./cmd/mesh-controller --- FAIL: TestTheSendMakesNoValueForAnOutsideSecretNobodyGave (0.64s)
./cmd/mesh-controller --- FAIL: TestAQuestionComposesWithoutAnOutsideSecretNobodyGave (0.63s)
./cmd/mesh-controller --- FAIL: TestReplay201 (0.24s)
./cmd/mesh-controller --- FAIL: TestARollbackWhoseSendWasRefusedIsCompletedByTheNextSend (0.34s)
./cmd/mesh-controller --- FAIL: TestAGateJudgesTheOtherMovesBesideAKeptCore (0.22s)
./cmd/mesh-controller --- FAIL: TestReplay401 (0.73s)
./cmd/mesh-controller --- FAIL: TestReplay201ThePlansSend (0.54s)
./cmd/mesh-controller --- FAIL: TestPlanAndNodeListAnOptionalRequirementLeftUnbound (0.15s)
./cmd/mesh-controller --- FAIL: TestReplay340 (0.67s)
./cmd/mesh-controller --- FAIL: TestOnlyATrustedFilesNamedKeyIsRefusedThroughAVerb (0.22s)
./cmd/mesh-controller --- FAIL: TestReplay349 (1.86s)
./cmd/mesh-controller --- FAIL: TestReplay348AFaultFromBeforeTheSendFailsNoGate (0.56s)
./cmd/mesh-controller --- FAIL: TestReplay239AModuleNameIsNotTakenOverByAnotherRepository (0.46s)
./cmd/mesh-controller --- FAIL: TestAWalkThatMovedNothingSaysWhichModulesMatchedWhatRuns (0.19s)
./cmd/mesh-controller --- FAIL: TestAWalkWhoseEveryBuildCameOutTheSameIsDone (0.20s)
./cmd/mesh-controller --- PASS: TestReplay614ANewSDKPlansTheToolchainAndThenItsBundles (0.50s)
./cmd/mesh-controller --- FAIL: TestOneAcceptForAProviderIsPlacedForEveryConsumer (0.41s)
./cmd/mesh-controller --- FAIL: TestReplay164 (0.41s)
./cmd/mesh-controller --- FAIL: TestAnApprovedLayerOpensTheWalkThatSendsIt (0.22s)
./cmd/mesh-controller --- FAIL: TestASettingsWalkSendsOneMachineAtATimeEachJudged (0.18s)
./cmd/mesh-controller --- FAIL: TestAFailedSettingsWalkStopsAndHoldsNothingBack (0.17s)
./cmd/mesh-controller --- FAIL: TestASettingsWalkSendsTheLayerAloneEveryBuildKept (0.17s)
./cmd/mesh-controller --- FAIL: TestASettingsWalkStopsBeforeADataMoveAndPassesOverAMachineAway (0.18s)
./cmd/mesh-controller --- FAIL: TestACrossingSendSupersedesASettingsGate (0.23s)
./cmd/mesh-controller --- FAIL: TestASettingsWalkFailsOnARefusalThatCannotClear (0.51s)
./cmd/mesh-controller --- FAIL: TestAProviderElsewhereServesItsOwnComposedName (0.19s)
./cmd/mesh-controller --- FAIL: TestAReusedCheckBuildIsRegisteredByItsDigestAndGatedAsABuiltOne (0.13s)
./cmd/mesh-controller --- FAIL: TestTheMergeGateJudgesEachManifestAgainstTheListOfTheTree (0.40s)
./cmd/mesh-controller --- FAIL: TestRegistrationPublishesTheNewestTrunkListAndJudgesEveryModuleAgainstIt (0.42s)
./cmd/mesh-controller --- FAIL: TestADeclarationIsTheSameAfterPlacementMoves (0.55s)
./cmd/mesh-controller --- FAIL: TestAReleaseSendsTheRestAtOnceAfterTheFirstPasses (0.56s)
./cmd/mesh-controller --- FAIL: TestARestMachineThatFailsIsPutBackAloneAndTheOthersAreJudgedOn (0.40s)
./cmd/mesh-controller --- FAIL: TestAWalkTakesOverTheReadingsOfAGateJudgingTheSameBuildThere (0.29s)
./cmd/mesh-controller --- FAIL: TestAFirstSendMadeAndNotKeptIsNotSentAgain (0.22s)
./cmd/mesh-controller --- FAIL: TestAReleaseSendKeptAndMadeIsNotMadeAgain (0.25s)
./cmd/mesh-controller --- FAIL: TestAFirstMachineThatFailsStillStopsTheWalk (0.23s)
./cmd/mesh-controller --- FAIL: TestTheControlNodeIsSentLastInAStep (0.19s)
./cmd/mesh-controller --- FAIL: TestARestMachineSilentPastItsBoundIsLeftAndSaid (0.20s)
./cmd/mesh-controller --- FAIL: TestANoMoveTierWaitsForNoNewReport (0.24s)
./cmd/mesh-controller --- FAIL: TestOneProviderDownAndThreeConsumersFailingAreOneCondition (0.40s)
./cmd/mesh-controller --- FAIL: TestAConsumerFailingBesideAHealthyProviderIsItsOwn (0.32s)
./cmd/mesh-controller --- FAIL: TestTheProvisionerClientsAccountIsIssuedForItsServiceAndNeverInvented (0.44s)
./cmd/mesh-controller --- FAIL: TestAcceptOfAnOwnSecretTakesThePathOfItsModulesForm (0.16s)
./cmd/mesh-controller --- FAIL: TestAcceptForAProviderTakesThePathOfTheProvidersModule (0.22s)
./cmd/mesh-controller --- FAIL: TestAcceptForAMovedTrustedModuleAnnouncesBeforeTheVaultIsAsked (0.20s)
./cmd/mesh-controller --- FAIL: TestAcceptForAMovedModuleRecordsAHandActAndNeverTheValue (0.17s)
./cmd/mesh-controller --- FAIL: TestAcceptOfAnOutsideOfferTakesThePathOfTheProvidersModule (0.20s)
./cmd/mesh-controller --- FAIL: TestAnAskAtTheDeskTakesThePathOfItsModulesForm (0.16s)
./cmd/mesh-controller --- FAIL: TestAnIssuedValueTakesThePathOfItsProvidersModule (0.18s)
./cmd/mesh-controller --- FAIL: TestARotationTakesThePathOfItsModulesForm (0.30s)
./cmd/mesh-controller --- FAIL: TestADeclarationIsTheSameWhileTheWordsAreStillInTheLayers (0.75s)
./cmd/mesh-controller --- FAIL: TestADeclarationIsTheSameAfterTheMoveOfPlacement (0.45s)
./cmd/mesh-controller --- FAIL: TestTheSendSealsNoSecretOfAModuleHandedThere (0.18s)
./cmd/mesh-controller --- FAIL: TestAModulesSecretsAreTheVaultsOnceItIsMarkedMoved (0.18s)
./cmd/mesh-controller --- FAIL: TestEveryMachineIsToldTheSameAfterTheMoveOfConfig (0.14s)
./cmd/mesh-controller --- FAIL: TestTheMoveOfConfigRefusesWhatWouldChangeAMachine (0.13s)
./cmd/mesh-controller --- FAIL: TestTheSettingsVerbForwardsToConfigOnceTheValuesMoved (0.13s)
./cmd/mesh-controller --- FAIL: TestTheSendCarriesTheVaultsBoxForACoreCredentialAndKeepsIt (0.61s)
./cmd/mesh-controller --- FAIL: TestASilentVaultHoldsTheKeptBoxAndSaysSo (0.14s)
./cmd/mesh-controller --- FAIL: TestACoreModuleFirstPlacedWhileTheVaultIsSilentIsSealedByTheController (0.15s)
./cmd/mesh-controller --- FAIL: TestAnEngineBelowTheContractIsSentTheControllersSealAsBefore (0.17s)
./cmd/mesh-controller --- FAIL: TestModuleIssueHandsACoveredAccountToTheVaultAndOnlyThat (0.23s)
./cmd/mesh-controller --- FAIL: TestModuleIssueFailsWhenTheVaultDoesNotTakeACoveredAccount (0.34s)
./cmd/mesh-controller --- FAIL: TestModuleIssueBeforeTheVaultIsInstalledKeepsTheValueAndHandsNothing (0.30s)
./cmd/mesh-controller --- FAIL: TestARecordedModulesBundleOnlyMoveRollsOutInItsWalk (2.68s)
./cmd/mesh-controller --- FAIL: TestARecordedModulesMoveThatRecreatesAContainerWaits (1.16s)
./cmd/mesh-controller --- FAIL: TestARecordedModulesMoveThatTouchesDataOrAProviderWaits (1.93s)
./cmd/mesh-controller --- FAIL: TestAPersonsRecordAndTheBusHoldEveryMove (0.90s)
./cmd/mesh-controller --- FAIL: TestARecordedMoveThatCannotBeJudgedWaits (0.56s)
./cmd/mesh-controller --- FAIL: TestReplay867 (1.37s)
./cmd/mesh-controller --- FAIL: TestReplay867Recheck (0.31s)
./cmd/mesh-controller --- FAIL: TestTheRecheckVerbAsksMeshDeliveryOnABusOfItsOwn (0.66s)
./cmd/mesh-controller --- FAIL: TestAssigningTheClientIssuesItsAccount (0.36s)
./cmd/mesh-controller --- FAIL: TestAnUnrelatedBatchWalksBesideAnOpenWalk (0.24s)
./cmd/mesh-controller --- FAIL: TestARelatedBatchWaitsBehindTheOpenWalk (0.15s)
./cmd/mesh-controller --- FAIL: TestAnOwnPathBatchNeverWalksBeside (0.16s)
./cmd/mesh-controller --- FAIL: TestMergesHeardWhileAnotherHolderHasThePlansAreRecordedAndCarried (0.28s)
./cmd/mesh-controller --- FAIL: TestABatchWindowClosesByTheExpiryOfItsKey (1.16s)
./cmd/mesh-controller --- FAIL: TestEveryMoveAMergeAndTheCutMakeOfAPlanIsSaid (0.30s)
./cmd/mesh-controller --- FAIL: TestARolloutAdvancesOnEventsAndAReplacedControllerResumesIt (0.27s)
./cmd/mesh-controller --- FAIL: TestAWalkLetGoByTheDeliverVerbIsAskedWithNoOtherEvent (0.25s)
./cmd/mesh-controller --- FAIL: TestTwoMergesWithinAMinuteLeaveEachOpenPullRequestOneQueuedCheck (0.14s)
./cmd/mesh-controller --- FAIL: TestADeliveryGroupMovingAModuleMachinesRunPassesTheGate (0.32s)
./cmd/mesh-controller --- FAIL: TestAModuleMovesOnTheOperatorsApproveOfTheMergeThatMovedIt (0.15s)
./cmd/mesh-controller --- FAIL: TestAModuleBuiltFromANewRepositoryIsRegisteredOnlyOnTheOperatorsApproveOnTheBus (1.40s)
./cmd/mesh-controller --- FAIL: TestAMergeWhosePlanCannotBeSavedIsHeldAndRecordedWhenHandedOverAgain (0.60s)
./cmd/mesh-controller --- FAIL: TestOneReadOfAnAssignmentNamesItsCommitBuildAndRolloutAndOneReadOfTheRolloutListsItsAssignments (0.15s)
./cmd/mesh-controller --- FAIL: TestASendOfWhatAMachineRunsAlreadyChangesNoLinkOfItsAssignment (0.14s)
./cmd/mesh-controller --- FAIL: TestAnAssignmentWaitingForItsBuildIsOneKeyOfTheAssignmentsBucket (0.15s)
./cmd/mesh-controller --- FAIL: TestNoTableOfTheControllersStoreHoldsBuildsRolloutsOrAssignments (0.13s)
./cmd/mesh-controller FAIL: go test exited 1
./internal/inventory --- PASS: TestTheLastSendSaysWhatTheMachineAnswered (0.11s)
./internal/inventory --- PASS: TestAReportIsTheLastSendsAnswerOnlyWhenItIsAboutThatSend (0.16s)
./internal/inventory --- PASS: TestAnIssuedValueIsSealedToEveryHolderOnceAndNotAgain (0.10s)
./internal/inventory --- PASS: TestAnIssuedValueIsSealedAgainAfterAKeyChangeOrAnAcceptance (0.10s)
./internal/inventory --- PASS: TestAConditionsLooksAreKeptBesideTheBucket (0.08s)
./internal/inventory --- PASS: TestAPlanIdHoldingAQuoteIsReadAsAPlainId (0.13s)
./internal/inventory --- PASS: TestAWalksStartIsKeptAndARefusedSaveLeavesItUnsaid (0.09s)
./internal/inventory --- PASS: TestAWalksRestIsReadFromEachMachinesOwnSend (0.15s)
./internal/inventory --- PASS: TestAStoredBuildWithASilentMergeableFileIsStillReadAndComposed (0.10s)
./internal/inventory --- PASS: TestACredentialIssuedOutsideIsNeverMade (0.11s)
./internal/inventory --- PASS: TestOneAcceptForAProviderIsSealedToEveryConsumer (0.14s)
./internal/inventory --- PASS: TestASharedOwnSecretIssuedOutsideIsNeverMade (0.16s)
./internal/inventory --- PASS: TestAModuleInTheConfigFormIsMirroredWithItsWholeDeclaration (0.11s)
./internal/inventory --- PASS: TestAReportOfABusyContainerIsKeptAndReadBack (0.10s)
./internal/inventory --- PASS: TestANewerBuildsListReplacesTheKeptOneAndAnOlderOneHeardLaterDoesNot (0.14s)
./internal/inventory --- PASS: TestPlacementMovesOutOfTheSettingsLayers (0.68s)
./internal/inventory --- PASS: TestASettingRoutesPlacementBesideTheLayer (0.13s)
./internal/inventory --- PASS: TestTheProvisionerClientsMachineHasAnAccountOfItsOwn (0.43s)
./internal/inventory --- PASS: TestTheFourWordsAreKeptBesideTheLayer (0.10s)
./internal/inventory --- PASS: TestALayerStillHoldingTheWordsReadsThemAsPlacement (0.09s)
./internal/inventory --- PASS: TestTheMoveOfPlacementMovesWhatTheLayersStillHold (0.10s)
./internal/inventory --- PASS: TestTheMoveReadsEveryRowSealedToAMachineAsItIs (0.17s)
./internal/inventory --- PASS: TestASendKeepsThePlansItHandedAndTheMirrorCarriesThem (0.16s)
./internal/inventory --- PASS: TestTheLayersAreReadUntilTheMoveOfConfigHasRun (0.09s)
./internal/inventory --- PASS: TestAModuleReadsMeshConfigOnlyWhereItsValuesAre (0.09s)
./internal/inventory --- PASS: TestTheEndOfTheMoveRefusesALayerChangedSinceItWasRead (0.41s)
./internal/inventory --- PASS: TestACoreCredentialsVaultBoxIsKeptPerMachineAndReplaced (0.24s)
./internal/inventory --- PASS: TestWhatRunsIsTheRegisteredBuildNotANewerOnePutBack (0.10s)
./internal/inventory --- PASS: TestBuildsOnTheBusAreReadBackByEveryReader (0.07s)
./internal/inventory --- PASS: TestARequestIsTheBuildInStateAskedAndItsOutcomeTakesItsPlace (0.07s)
./internal/inventory --- PASS: TestAnAssignmentIsAKeyOfTheBucketAndAnUnassignmentEndsIt (0.11s)
./internal/inventory --- FAIL: TestThePlansAreKeptInTheAssignmentsValuesAndNothingElseOfThemMoves (0.08s)
./internal/inventory --- FAIL: TestAPendingAssignmentIsAKeyOfTheAssignmentsBucket (0.08s)
./internal/inventory --- PASS: TestARecordedPendingIsSkippedByAssignedAndTheJoins (0.08s)
./internal/inventory --- PASS: TestTwoClaimsOfOnePendingMakeOneAndTheOtherSeesFalse (0.08s)
./internal/inventory --- PASS: TestAssignOverAPendingKeepsItsRecordAsApplied (0.08s)
./internal/inventory --- PASS: TestAPendingIsMarkedOnceAndGoesWithItsMachine (0.09s)
./internal/inventory --- PASS: TestAReplacedWaitNeverLeavesTheOperatorWithoutItsCondition (0.07s)
./internal/inventory --- PASS: TestSentBuildsAnswersFromTheAssignmentsKeysOfTheNode (0.08s)
./internal/inventory --- PASS: TestASendReplacesTheWholeMapOfTheNodeAndAHandSendMakesItUnknown (0.08s)
./internal/inventory --- PASS: TestAFailedWriteOfTheLinksFailsTheRecordOfTheSend (0.07s)
./internal/inventory --- PASS: TestMigration0105RefusesAStoreWhoseRowsWereNotMovedAndDropsTheTablesOfAMovedOne (0.45s)
./internal/inventory --- PASS: TestMigration0105PassesAStoreThatNeverHeldARow (0.12s)
./internal/inventory --- PASS: TestTheColumnOfASentMachineIsCopiedOntoItsKeysAndEmptied (0.08s)
./internal/inventory --- PASS: TestASendEmptiesTheColumnSoALaterCopyLeavesAClearedKeyBare (0.08s)
./internal/inventory FAIL: go test exited 1
./internal/recordmirror --- PASS: TestNatsAnAssignmentAndARegistrationEachChangeOneKeyAndRaiseOneEvent (2.00s)
./internal/recordmirror --- PASS: TestNatsTheListOfPredefinedKeysKeptChangesTheMirrorsOneKey (1.44s)
114 store test(s) listed in testdata/store-tests did not run and pass against the store
--- what failed, picked from the whole of its output (the whole is in the build's log)
--- FAIL: TestAnAssignmentThatBlocksAnotherMachineSaysWhichAndWhy (1.02s)
acts_test.go:27: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestConvergingIsRefusedOnAPreviewThatWouldBeStale (1.08s)
adopting_test.go:134: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestTheFlipHoldsTheNodeWhileItSends (0.72s)
adopting_test.go:502: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAPlanCutFromAMergeOfABackedUpModuleAsksItsBackupAndNotItsTierUntilItIsDone (0.71s)
backups_before_send_integration_test.go:226: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAFailedWalkWalksItsEarlierMergesAlone (0.60s)
batches_integration_test.go:341: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestARepositoryMadeAgainUnderItsNameIsNotTheModulesSource (0.57s)
build_source_integration_test.go:214: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestASendAssertsWhatWasAssignedAfterStart (0.87s)
busobjects_test.go:84: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestNoTableOfTheControllersStoreHoldsBuildsRolloutsOrAssignments (1.03s)
chain_no_table_integration_test.go:18: the builds are not laid out under their modules yet; the controller's start does it and says so
the checks' builds of 1 pull request(s) could not be read, so the walk builds: no bus
--- FAIL: TestTwoMergesWithinAMinuteLeaveEachOpenPullRequestOneQueuedCheck (0.74s)
checks_queue_test.go:25: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestTheMoveOfConfigRefusesWhatWouldChangeAMachine (0.52s)
config_moved_integration_test.go:262: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAnEngineBelowTheContractIsSentTheControllersSealAsBefore (0.67s)
core_box_integration_test.go:121: the builds are not laid out under their modules yet; the controller's start does it and says so
novox/mesh-catalog changed more files than were listed: the manifests of its modules (modules/a/module.json) are read as changed
novox/mesh-catalog changed more files than were listed: the manifests of its modules (modules/a/module.json) are read as changed
--- FAIL: TestAMachineWhoseDeclarationDoesNotComposeIsSaid (0.63s)
doctor_integration_test.go:127: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestABuildThatFailsItsGateIsRolledBackOnItsFirstMachineAndGoesNoFurther (0.50s)
gate_integration_test.go:142: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestNatsH3AssertsAMissingConsumerAgainAndBrakesAfterItsBudget (0.59s)
healers_integration_test.go:253: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestANamedPushStillSendsAConsequenceNothingHolds (2.56s)
held_back_integration_test.go:130: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestSavingPlansAndMovingMergesIsOneAct (0.73s)
issue459_integration_test.go:268: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestNodeShowAndStatusReadTheLastSendFromTheStore (0.76s)
last_send_integration_test.go:14: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAMachineSilentPastItsBoundIsLeftAndSaidAtOnce (0.50s)
lean_walk_integration_test.go:95: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestARelatedMergeJoinsTheBatchAndWaitsForTheWindow (2.75s)
--- FAIL: TestARelatedMergeJoinsTheBatchAndWaitsForTheWindow/same_repository (0.41s)
lone_merge_test.go:41: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestARelatedMergeJoinsTheBatchAndWaitsForTheWindow/a_module_in_common (0.73s)
lone_merge_test.go:41: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestARelatedMergeJoinsTheBatchAndWaitsForTheWindow/an_edge_of_the_graph (0.50s)
lone_merge_test.go:41: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestARelatedMergeJoinsTheBatchAndWaitsForTheWindow/the_same_group_head (1.10s)
lone_merge_test.go:41: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestALoneMergeRelatedToAWalkTheCutFoldsJoinsTheBatch (0.53s)
lone_merge_test.go:314: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAFailedUnitIsTheModulesConditionAndTheMachinesOwnAreOneFinding (0.61s)
machine_units_integration_test.go:15: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAManifestTheRunningControllerCannotReadFailsThePullRequest (0.58s)
merge_gate_integration_test.go:124: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestTheResolverIsToldEveryMachineOnTheNetworkAndToldAgainWhenOneLeaves (1.93s)
network_test.go:260: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAskingAboutAMachineTheMeshHasNeverHeardOfIsRefused (0.89s)
nodes_test.go:98: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAnUnassignThatLeavesItsNodeResolvedSaysNothingOfIt (1.49s)
one_resolution_integration_test.go:38: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAStatusReadSettlesNothing (0.48s)
pending_integration_test.go:115: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAnUnknownModuleIsRefusedWithTheClosestNames (0.92s)
pending_integration_test.go:388: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestABuildNoLongerWaitedForIsStillInFlight (0.69s)
pending_integration_test.go:709: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAssigningTheClientIssuesItsAccount (0.31s)
provisioner_account_integration_test.go:55: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAPlanStoppedAtItsFirstMachineIsRetried (0.30s)
queue_integration_test.go:336: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestReplay348AFaultFromBeforeTheSendFailsNoGate (0.41s)
replay348_test.go:27: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestReplay273AConsumerBesideItsStoreStaysBoundToIt (0.29s)
replays_integration_test.go:50: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAReleaseSendsTheRestAtOnceAfterTheFirstPasses (0.29s)
rest_at_once_integration_test.go:40: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAnUnhealthyOwnRuntimeRaisesTheModulesUsualCondition (0.24s)
runtime_health_test.go:17: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestADefinitionMovingUnderAStoredSettingLeavesThatModuleOutNotTheMachine (0.55s)
sendable_integration_test.go:302: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestPreferencesListedFromTheStores (0.24s)
settings_effective_integration_test.go:13: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestASettingsWalkStopsBeforeADataMoveAndPassesOverAMachineAway (0.23s)
settings_walk_integration_test.go:315: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestTheAgentsManagedSettingsAreRefusedThroughAVerb (0.25s)
terminal_settings_test.go:223: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestATierPutsABrokenModuleBackAtOnce (0.47s)
--- FAIL: TestATierPutsABrokenModuleBackAtOnce/gate_kept_on_node-tools (0.23s)
tier_send_integration_test.go:325: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestATierPutsABrokenModuleBackAtOnce/gate_kept_on_app1 (0.24s)
tier_send_integration_test.go:325: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAHeldModuleIsFoundFromWhatTheMachineReported (0.26s)
untaken_integration_test.go:27: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAcceptForAMovedModuleRecordsAHandActAndNeverTheValue (0.23s)
vault_switch_test.go:386: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAWalkStoppedByHandAndRetriedEndsFailedWhenItFailsAgain (0.35s)
walk_said_integration_test.go:233: the builds are not laid out under their modules yet; the controller's start does it and says so
FAIL github.com/novox/mesh-controller/cmd/mesh-controller 34s (shard 1 of 8: 140 tests)
--- FAIL: TestAConsumerAssignedBeforeItsProviderIsStillAssigned (1.16s)
acts_test.go:84: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestTheFlipIsRefusedWhileAFoundContainerIsHeld (1.05s)
adopting_test.go:145: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestThePreviewNamesEveryHeldKind (0.64s)
adopting_test.go:547: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestTheSelfCheckSaysAnAgentAccountThatCanBecomeRoot (0.82s)
agent_account_integration_test.go:18: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAModuleAssignedAndNotPushedIsAwaitingAPushNotUncomposable (0.61s)
awaiting_push_integration_test.go:17: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestTwoMergesSecondsApartAreOneWalkAtTheLaterCommit (0.58s)
batches_integration_test.go:66: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAGroupsOrderBecomesTiersInsideTheWalk (0.78s)
batches_integration_test.go:408: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestABuildFromAnAgentsRepositoryIsNotRegisteredAsAModuleTheMeshHolds (0.88s)
build_source_integration_test.go:39: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestATerminalRequestCoversOnlyWhatItAsked (0.86s)
build_source_integration_test.go:240: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestASendThatCannotAssertTheBusSaysSoAndRaisesACondition (0.56s)
busobjects_test.go:123: the builds are not laid out under their modules yet; the controller's start does it and says so
the earlier checks' builds of novox/shop#7 could not be read, so the check builds: no bus
--- FAIL: TestTheSettingsVerbForwardsToConfigOnceTheValuesMoved (0.69s)
config_moved_integration_test.go:306: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestNatsTheBusIsWhatTheControllerDefines (0.41s)
doctor_integration_test.go:149: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAFaultBeforeTheSettleTimeWaitsForTheModuleBesideIt (0.49s)
gate_followup_test.go:64: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestABuildThatPassesItsGateRollsEverywhereUnattended (0.53s)
gate_integration_test.go:231: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestNatsH4ResetsTheControllersEventsConsumerAndItStillDelivers (2.68s)
healers_integration_test.go:343: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestASecondEligibleHolderStandsBesideTheOneHeldByBeingAlone (0.55s)
holdings_test.go:25: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAnOverflowingConsumerNeverRefusesItsProvidersMachine (0.59s)
identity_bound_integration_test.go:14: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAMergeOfAGroupWaitsEvenAlone (0.45s)
lone_merge_test.go:102: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAModuleAMachineRunsRemovedFromItsSourceFails (0.43s)
merge_gate_integration_test.go:133: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestTheRosterNamesOnlyTheMachines (1.87s)
network_test.go:316: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestANodeAddedAdoptedIsAdopted (2.11s)
nodes_test.go:107: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAnAssignThatLeavesItsNodeUnresolvedSaysOnlyThePlansRefusal (0.44s)
one_resolution_integration_test.go:57: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAPendingAssignmentExpiresWhenItsBuildFails (0.71s)
pending_integration_test.go:138: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAnActWithAModuleNotRegisteredIsRefusedWhole (0.79s)
pending_integration_test.go:412: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestOneProviderDownAndThreeConsumersFailingAreOneCondition (0.39s)
provider_hold_test.go:24: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAPlanIsAnsweredOnlyByTheBuildItAskedFor (0.32s)
queue_integration_test.go:403: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestARecordedModulesBundleOnlyMoveRollsOutInItsWalk (0.27s)
recorded_moves_test.go:187: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestTheBacklogIsReleasedOneMachineAtATimeEachJudged (0.29s)
release_test.go:176: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestReplay318 (0.23s)
replay318_test.go:37: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestReplay349 (0.29s)
replay349_test.go:24: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestReplayCrashLoopFailsItsGateOnTheFirstMachine (0.28s)
replays_integration_test.go:111: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestARestMachineThatFailsIsPutBackAloneAndTheOthersAreJudgedOn (0.27s)
rest_at_once_integration_test.go:66: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestASetThatDoesNotComposeIsMarkedAsTheNodesOwnProblem (1.37s)
roster_failure_test.go:15: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAWalkWhoseEveryBuildCameOutTheSameIsDone (0.48s)
same_program_integration_test.go:17: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestACrossingSendSupersedesASettingsGate (0.93s)
settings_walk_integration_test.go:361: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestTheMergeGateJudgesAChangeToATemplateAlone (1.05s)
template_integration_test.go:47: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAnyKeyOfAModuleWithATrustedMergeableFileIsRefusedThroughAVerb (1.02s)
terminal_settings_test.go:293: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestASendCarryingTheToolRunnerWaitsForItsWitnessWindow (0.35s)
tier_send_integration_test.go:380: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestPlanAndNodeListAnOptionalRequirementLeftUnbound (1.03s)
unbound_test.go:16: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestTheJSONStatusCarriesWhatIsHeldAndForWhichModule (0.28s)
untaken_integration_test.go:43: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAcceptOfAnOwnSecretTakesThePathOfItsModulesForm (1.09s)
vault_switch_test.go:117: the builds are not laid out under their modules yet; the controller's start does it and says so
FAIL github.com/novox/mesh-controller/cmd/mesh-controller 45s (shard 2 of 8: 140 tests)
--- FAIL: TestUnassigningAProviderNamesWhoIsNowBlocked (1.00s)
acts_test.go:105: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestTakingNamesWhatItReplaces (1.05s)
adopting_test.go:157: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestTheFlipIsRefusedOnAnAccountNamingNothingReachable (0.70s)
adopting_test.go:590: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestTheFactsCarryTheAgentAccountAsAPseudonym (0.78s)
agent_account_integration_test.go:68: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestASecretThePushCannotMakeIsStillUncomposable (0.67s)
awaiting_push_integration_test.go:72: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestThreeRepositoriesInOneWindowAreOneWalk (0.58s)
batches_integration_test.go:110: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestABatchSurvivesARestart (0.89s)
batches_integration_test.go:444: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestANewModuleFromARepositoryTheCatalogueDoesNotBuildFromIsNotRegistered (0.80s)
build_source_integration_test.go:71: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestNatsAModuleAssignedAfterStartGetsItsConsumerAtItsFirstSend (0.83s)
busobjects_test.go:165: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAComposedMembersCheckIsItsRepositoryChecksAlone (2.34s)
composed_member_check_test.go:48: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAnApprovalRaisedBeforeTheMoveOfConfigIsRefusedAfterIt (0.56s)
config_moved_integration_test.go:404: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAMergeWaitsForItsDeliverysWordAndThePersonsWordWorksWithoutIt (0.72s)
delivery_integration_test.go:20: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAMachineIsSentTheEpochOnlyOnceItSaysItReadsOne (0.38s)
epoch_send_test.go:30: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAPassIsCountedNoFasterThanTheGatesSpacing (0.73s)
gate_followup_test.go:106: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestABuildRollsToEveryMachineAtOnceWithNoGate (0.70s)
gate_integration_test.go:254: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestTheGrantsStepSendsTheUserListAndNothingElse (0.65s)
grants_step_store_test.go:27: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAGroupsBatchWaitsForItsLastMemberHoweverLongItTakes (0.47s)
group_one_batch_test.go:18: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAHolderOnRecordIsNotRewrittenByDerivation (0.69s)
holdings_test.go:83: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAWalkThatMovedNothingSaysWhichModulesMatchedWhatRuns (0.68s)
issue611_integration_test.go:14: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAHeadedMergeInNoGroupIsCutAtOnce (1.00s)
lone_merge_test.go:134: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestIssue278AWideRebuildIsSaidBeforeTheMerge (1.78s)
merge_gate_integration_test.go:141: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestTwoUnhealthyStatementsRaiseTheModulesConditionAndAHealthyOneClearsIt (0.90s)
module_health_test.go:39: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestPlacingANodeWithNothingSaidDoesNotUnplaceIt (0.58s)
network_test.go:38: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAMergeBuildsTheNewModuleItAdds (0.33s)
new_module_on_merge_test.go:33: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestATokenIssuedAdoptedSaysSoAndReissuingDoesNotConverge (0.31s)
nodes_test.go:128: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestTheConditionClearsWhenTheModuleIsAssignedLater (0.28s)
pending_integration_test.go:205: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestUnassignWithdrawsAPendingAssignment (0.29s)
pending_integration_test.go:427: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestADeclarationIsTheSameAfterPlacementMoves (0.40s)
placement_moved_test.go:24: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAControllerLeavesThePlansToTheOneHoldingThem (0.24s)
plans_one_at_a_time_test.go:16: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAConsumerFailingBesideAHealthyProviderIsItsOwn (0.25s)
provider_hold_test.go:145: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAPushSaysWhatItRecreates (0.23s)
push_recreates_test.go:20: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAFailedPlanIsRetriedAndGoesOnThroughItsLaterTiers (0.23s)
queue_integration_test.go:22: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestARebuildOfACommitAsksWhatTheModuleFollows (0.34s)
queue_integration_test.go:429: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestARecordedModulesMoveThatRecreatesAContainerWaits (0.54s)
--- FAIL: TestARecordedModulesMoveThatRecreatesAContainerWaits/image (0.23s)
recorded_moves_test.go:231: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestARecordedModulesMoveThatRecreatesAContainerWaits/spec (0.30s)
recorded_moves_test.go:231: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAFailedReleaseIsPutBackAndTheNextWaitsForAPerson (0.25s)
release_test.go:231: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestReplay325 (0.43s)
replay325_test.go:23: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestReplay401 (1.57s)
replay401_test.go:20: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestReplaySilentWebAppIsRaisedWithinTwoLooks (0.76s)
replays_integration_test.go:269: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAWalkTakesOverTheReadingsOfAGateJudgingTheSameBuildThere (1.14s)
rest_at_once_integration_test.go:101: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAStoreThatCannotBeReadIsNotANodeThatDoesNotCompose (0.96s)
roster_failure_test.go:35: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAModulePulledInIsHandedOnAMachineThatCanTakeItAndMirrored (0.99s)
sent_required_by_integration_test.go:17: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestASettingsWalkFailsOnARefusalThatCannotClear (1.02s)
settings_walk_integration_test.go:400: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestOnlyATrustedFilesNamedKeyIsRefusedThroughAVerb (1.42s)
terminal_settings_test.go:353: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAnAssignmentSaysOnlyWhatItChangedOnItsOwnNode (0.26s)
unheld_report_integration_test.go:13: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAcceptForAProviderTakesThePathOfTheProvidersModule (0.21s)
vault_switch_test.go:151: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAWalkLetGoAndStoppedByVerbsIsSaidStartedAndEnded (0.20s)
walk_said_integration_test.go:20: the builds are not laid out under their modules yet; the controller's start does it and says so
FAIL github.com/novox/mesh-controller/cmd/mesh-controller 45s (shard 3 of 8: 140 tests)
--- FAIL: TestTheRegistryTrustAndEveryImageFollowThePortTheNodeGaveTheStore (1.02s)
addresses_integration_test.go:17: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestATakeIsRefusedOnAChangedPreviewOrAStaleAccount (1.09s)
adopting_test.go:201: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAssigningWaitsForWhateverIsConvergingTheNode (0.70s)
adopting_test.go:618: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestASearchStillRunningAfterARestartIsNotUrgent (0.76s)
agent_account_integration_test.go:99: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAGivenSecretUnderAnOldKeyIsNotForeseen (0.61s)
awaiting_push_integration_test.go:105: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAMergeRestartsTheWindowAndTheMaximumClosesIt (0.60s)
batches_integration_test.go:144: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestALateMergeOfAOneModuleRepositoryIsNamed (0.80s)
batches_integration_test.go:469: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAnUnrelatedBatchWalksBesideAnOpenWalk (0.79s)
beside_test.go:16: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAtTheTerminalAnotherRepositoryIsRegistered (0.97s)
build_source_integration_test.go:91: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAnUnknownIdentityKeepsTheRecordedOne (0.54s)
build_source_integration_test.go:275: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestOneReadOfAnAssignmentNamesItsCommitBuildAndRolloutAndOneReadOfTheRolloutListsItsAssignments (0.64s)
chain_integration_test.go:26: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAReusedCheckBuildIsRegisteredByItsDigestAndGatedAsABuiltOne (0.59s)
check_builds_integration_test.go:39: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAMemberOfAGroupOfAnOlderMeshDeliveryKeepsItsOwnGate (0.44s)
composed_member_check_test.go:56: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAPlacementOnlyApprovalRaisedBeforeTheMoveIsSetAfterIt (0.46s)
config_moved_integration_test.go:442: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAWalkLetGoByAVerbIsSaidAsPlanMoved (2.56s)
delivery_integration_test.go:152: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestNothingIsComposedOrSentWithoutTheLease (0.66s)
epoch_send_test.go:87: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestACarriedPassCarriesOnlyItsOwnWait (0.69s)
gate_followup_test.go:131: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestALeafModulePassesOnOneHealthyReading (0.43s)
gate_integration_test.go:280: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAGroupWithAMemberOfEachKindIsOneBatchAndOneWalk (1.30s)
--- FAIL: TestAGroupWithAMemberOfEachKindIsOneBatchAndOneWalk/controller_member_first (0.57s)
group_one_batch_test.go:52: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAGroupWithAMemberOfEachKindIsOneBatchAndOneWalk/catalogue_member_first (0.73s)
group_one_batch_test.go:52: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestH1AsksAMachineToReportAndSendsItAgain (0.69s)
healers_integration_test.go:22: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAReportedHostVersionIsKeptAndReadBack (0.69s)
hosts_behind_integration_test.go:11: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestReplay201 (0.55s)
issue201_integration_test.go:69: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestReplay352 (1.21s)
--- FAIL: TestReplay352/a_newer_send_to_the_judged_machine_does_not_unreport_the_gate's (0.64s)
issue352_integration_test.go:27: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestReplay352/a_send_that_moves_the_module_supersedes_the_judging (0.57s)
issue352_integration_test.go:106: the builds are not laid out under their modules yet; the controller's start does it and says so
… 500 more line(s) naming what failed, past the 400 lines or 32 KiB kept
**Merge check** at `0b4cd46b`
Judged: head `0b4cd46b3f04` merged into trunk `da6d038e07c0`; read beside it: mesh-catalog `7f77ce663a9e`, mesh-controller-main `da6d038e07c0`, mesh-host `6469e8238443`, mesh-tools `7412c5b6c9c5`
- `mesh/merge-gate`: **ERROR** — the mesh as it is could not be raised, so the change cannot be judged against it (4 of 4 machines compose on the mesh and not in the gate); the first: a machine (f35) composes on the mesh and not as the gate raised it from the snapshot: the private network cannot be computed: whether f35 answers "mesh-addressing" cannot be read: this kind of record lives on the bus, and this process has not opened the bus: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus (modules: build-agent, mesh-controller)
- `mesh/repo-check`: **FAIL** — its merge-check.sh failed: --- FAIL: TestAnAssignmentThatBlocksAnotherMachineSaysWhichAndWhy (1.02s); and TestConvergingIsRefusedOnAPreviewThatWouldBeStale, TestTheFlipHoldsTheNodeWhileItSends, TestAPlanCutFromAMergeOfABackedUpModuleAsksItsBackupAndNotItsTierUntilItIsDone, TestAFailedWalkWalksItsEarlierMergesAlone, TestARepositoryMadeAgainUnderItsNameIsNotTheModulesSource and 395 more
**Delivery plan** — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
- tier 0: mesh-controller
- tier 1: build-agent
- ace: receives build-agent
- g14: receives build-agent
- novox: receives mesh-controller, build-agent
- shanks: receives build-agent
- build-agent keeps data (ADR 0233): what it holds is backed up before it moves
- grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before build-agent is judged on its first machine
- read by no module's build: cmd/mesh-controller/chain_integration_test.go, cmd/mesh-controller/chain_no_table_integration_test.go, cmd/mesh-controller/pending_integration_test.go, cmd/mesh-controller/pending_test.go, cmd/mesh-controller/plan_moved_every_writer_test.go, cmd/mesh-controller/record_mirrors_switch_test.go, cmd/mesh-controller/sent_required_by_integration_test.go, internal/chain/pending_test.go, internal/inventory/chain_assignments_key_test.go, internal/inventory/chain_builds_layout_test.go, internal/inventory/chain_drop_test.go, internal/inventory/chain_move_test.go, internal/inventory/chain_moved_test.go, internal/inventory/chain_pending_test.go, internal/inventory/chain_rollouts_test.go, internal/inventory/chain_sent_copy_test.go, internal/inventory/chain_sent_test.go, internal/inventory/chain_source_test.go, internal/inventory/chain_store_test.go, internal/inventory/mirrored_test.go, internal/inventory/pin_completed_test.go, internal/inventory/sent_builds_test.go, internal/inventory/sent_plans_test.go, internal/recordmirror/mirror_store_test.go, testdata/store-tests
Run by the build seat on ace as `build-1792323924401214012` (`builds --log build-1792323924401214012`).
```
vault_secrets_integration_test.go:23: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAcceptForAMovedTrustedModuleAnnouncesBeforeTheVaultIsAsked (0.24s)
vault_switch_test.go:340: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAWalkRestartedByARebuildIsSaidStarted (0.30s)
walk_said_integration_test.go:210: the builds are not laid out under their modules yet; the controller's start does it and says so
FAIL
FAIL github.com/novox/mesh-controller/cmd/mesh-controller 34s (shard 8 of 8: 139 tests)
ok github.com/novox/mesh-controller/internal/inventory 33s (shard 1 of 4: 89 tests)
builds: the pointer alpha.newest was missing or wrong (a lookup of alpha.commit.c4) and is repaired from the records of alpha
builds: the pointer alpha.worked was missing or wrong (a lookup of alpha.commit.c4) and is repaired from the records of alpha
builds: the pointer alpha.held was missing or wrong (a lookup of alpha.commit.c4) and is repaired from the records of alpha
builds: the pointer alpha.commit.c4 was missing or wrong (a lookup of alpha.commit.c4) and is repaired from the records of alpha
builds: the pointer alpha.source.v1-s4 was missing or wrong (a lookup of alpha.commit.c4) and is repaired from the records of alpha
builds: the pointer alpha.commit.c2 was missing or wrong (a lookup of alpha.commit.c2) and is repaired from the records of alpha
--- FAIL: TestAPendingAssignmentIsAKeyOfTheAssignmentsBucket (0.50s)
chain_pending_test.go:57: known map[p-1792323976701951623:true p-1792323976719378380:true]: the key holds the newer one now
FAIL
FAIL github.com/novox/mesh-controller/internal/inventory 29s (shard 2 of 4: 89 tests)
--- FAIL: TestThePlansAreKeptInTheAssignmentsValuesAndNothingElseOfThemMoves (0.34s)
chain_store_test.go:314: dunst's value is {Node:anchor Module:dunst Assigned:2026-10-18 11:46:17.038645169 +0000 UTC RequiredBy: Provisioning:[123 34 116 101 109 112 108 97 116 101 115 34 58 123 34 115 111 117 114 99 101 34 58 34 104 116 116 112 58 47 47 115 116 111 114 101 58 53 48 48 48 47 118 50 47 100 117 110 115 116 47 102 105 108 101 115 47 98 108 111 98 115 47 115 104 97 50 53 54 58 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 34 44 34 100 105 103 101 115 116 34 58 34 115 104 97 50 53 54 58 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 34 125 44 34 102 105 108 101 115 34 58 91 123 34 105 100 34 58 34 99 111 110 102 105 103 117 114 97 116 105 111 110 34 44 34 112 97 116 104 34 58 34 47 104 111 109 101 47 111 112 47 46 99 111 110 102 105 103 47 100 117 110 115 116 47 100 117 110 115 116 114 99 34 44 34 116 101 109 112 108 97 116 101 34 58 34 100 117 110 115 116 114 99 34 44 34 111 119 110 101 114 45 97 116 45 114 117 110 116 105 109 101 34 58 34 111 119 110 101 100 34 44 34 116 97 107 101 115 34 58 34 114 101 108 111 97 100 45 111 110 34 125 93 125] Build: Artifact: Package:<nil> Commit: Rollout: Since:0001-01-01 00:00:00 +0000 UTC Ended:0001-01-01 00:00:00 +0000 UTC State: Pending:<nil> PulledIn:false SentUnknown:2026-10-18 11:46:17.052630914 +0000 UTC}
FAIL
FAIL github.com/novox/mesh-controller/internal/inventory 29s (shard 3 of 4: 88 tests)
ok github.com/novox/mesh-controller/internal/inventory 31s (shard 4 of 4: 88 tests)
ok github.com/novox/mesh-controller/internal/builder 32s (shard 1 of 4: 54 tests)
ok github.com/novox/mesh-controller/internal/builder 33s (shard 2 of 4: 53 tests)
ok github.com/novox/mesh-controller/internal/builder 34s (shard 3 of 4: 53 tests)
ok github.com/novox/mesh-controller/internal/builder 29s (shard 4 of 4: 53 tests)
ok github.com/novox/mesh-controller/internal/link 29s (shard 1 of 4: 50 tests)
ok github.com/novox/mesh-controller/internal/link 18s (shard 2 of 4: 50 tests)
ok github.com/novox/mesh-controller/internal/link 19s (shard 3 of 4: 49 tests)
ok github.com/novox/mesh-controller/internal/link 30s (shard 4 of 4: 49 tests)
integration level (the whole suite, tag integration): 3404 tests (6 skipped outside the shards), 59 s
nested module modules/build-agent:
ok build-agent 1.014s
nested module modules/route-proxy:
ok route-proxy/cmd/route-provider 1.012s
nested modules: 3 s
store tests, each run against the store:
./cmd/mesh-controller --- FAIL: TestAStopWithoutAMergeWalksTheOthersAgain (0.24s)
./cmd/mesh-controller --- FAIL: TestAStopWithoutAMergeEndsTheMergesThatContainIt (0.16s)
./cmd/mesh-controller --- FAIL: TestAStopWalksTheOthersAgainInTheOpenBatch (0.16s)
./cmd/mesh-controller --- FAIL: TestAStopNamesWhatStaysOnTheMachinesAndWhatStillCarriesIt (0.28s)
./cmd/mesh-controller --- FAIL: TestAStopWithoutAMergeLeavesItOutOfABatch (0.23s)
./cmd/mesh-controller --- FAIL: TestSavingPlansAndMovingMergesIsOneAct (0.24s)
./cmd/mesh-controller --- FAIL: TestAPlanFollowedFromTheStoreAnswersWhenItMoves (0.45s)
./cmd/mesh-controller --- FAIL: TestIssue969TheGateRaisesEachMachineAsItsEngineStatedItself (0.35s)
./cmd/mesh-controller --- FAIL: TestNodeShowAndStatusReadTheLastSendFromTheStore (0.36s)
./cmd/mesh-controller --- PASS: TestTheConditionsVerbReadsTheLooksTheBucketNoLongerHolds (0.14s)
./cmd/mesh-controller --- FAIL: TestAWalkLetGoAndStoppedByVerbsIsSaidStartedAndEnded (0.20s)
./cmd/mesh-controller --- FAIL: TestAWalkStoppedOrClosedByAPersonIsSaidEndedStopped (0.19s)
./cmd/mesh-controller --- FAIL: TestAWalkRetriedByAPersonIsSaidStartedAgain (0.19s)
./cmd/mesh-controller --- FAIL: TestABacklogReleasedByAPersonIsSaidStarted (0.16s)
./cmd/mesh-controller --- FAIL: TestAWalkEndedByCancelOrClearIsSaidEnded (0.63s)
./cmd/mesh-controller --- FAIL: TestAWalkRestartedByARebuildIsSaidStarted (1.29s)
./cmd/mesh-controller --- FAIL: TestAWalkStoppedByHandAndRetriedEndsFailedWhenItFailsAgain (0.71s)
./cmd/mesh-controller --- FAIL: TestReplay237 (0.34s)
./cmd/mesh-controller --- FAIL: TestAnUnassignThatLeavesItsNodeUnresolvedSaysSoOnceInItsAnswer (0.62s)
./cmd/mesh-controller --- FAIL: TestAnUnassignThatLeavesItsNodeResolvedSaysNothingOfIt (0.60s)
./cmd/mesh-controller --- FAIL: TestAnAssignThatLeavesItsNodeUnresolvedSaysOnlyThePlansRefusal (0.42s)
./cmd/mesh-controller --- FAIL: TestADirectoryOwnersKeyIsRefusedThroughAVerb (0.18s)
./cmd/mesh-controller --- FAIL: TestTheSendMakesNoValueForAnOutsideSecretNobodyGave (0.64s)
./cmd/mesh-controller --- FAIL: TestAQuestionComposesWithoutAnOutsideSecretNobodyGave (0.63s)
./cmd/mesh-controller --- FAIL: TestReplay201 (0.24s)
./cmd/mesh-controller --- FAIL: TestARollbackWhoseSendWasRefusedIsCompletedByTheNextSend (0.34s)
./cmd/mesh-controller --- FAIL: TestAGateJudgesTheOtherMovesBesideAKeptCore (0.22s)
./cmd/mesh-controller --- FAIL: TestReplay401 (0.73s)
./cmd/mesh-controller --- FAIL: TestReplay201ThePlansSend (0.54s)
./cmd/mesh-controller --- FAIL: TestPlanAndNodeListAnOptionalRequirementLeftUnbound (0.15s)
./cmd/mesh-controller --- FAIL: TestReplay340 (0.67s)
./cmd/mesh-controller --- FAIL: TestOnlyATrustedFilesNamedKeyIsRefusedThroughAVerb (0.22s)
./cmd/mesh-controller --- FAIL: TestReplay349 (1.86s)
./cmd/mesh-controller --- FAIL: TestReplay348AFaultFromBeforeTheSendFailsNoGate (0.56s)
./cmd/mesh-controller --- FAIL: TestReplay239AModuleNameIsNotTakenOverByAnotherRepository (0.46s)
./cmd/mesh-controller --- FAIL: TestAWalkThatMovedNothingSaysWhichModulesMatchedWhatRuns (0.19s)
./cmd/mesh-controller --- FAIL: TestAWalkWhoseEveryBuildCameOutTheSameIsDone (0.20s)
./cmd/mesh-controller --- PASS: TestReplay614ANewSDKPlansTheToolchainAndThenItsBundles (0.50s)
./cmd/mesh-controller --- FAIL: TestOneAcceptForAProviderIsPlacedForEveryConsumer (0.41s)
./cmd/mesh-controller --- FAIL: TestReplay164 (0.41s)
./cmd/mesh-controller --- FAIL: TestAnApprovedLayerOpensTheWalkThatSendsIt (0.22s)
./cmd/mesh-controller --- FAIL: TestASettingsWalkSendsOneMachineAtATimeEachJudged (0.18s)
./cmd/mesh-controller --- FAIL: TestAFailedSettingsWalkStopsAndHoldsNothingBack (0.17s)
./cmd/mesh-controller --- FAIL: TestASettingsWalkSendsTheLayerAloneEveryBuildKept (0.17s)
./cmd/mesh-controller --- FAIL: TestASettingsWalkStopsBeforeADataMoveAndPassesOverAMachineAway (0.18s)
./cmd/mesh-controller --- FAIL: TestACrossingSendSupersedesASettingsGate (0.23s)
./cmd/mesh-controller --- FAIL: TestASettingsWalkFailsOnARefusalThatCannotClear (0.51s)
./cmd/mesh-controller --- FAIL: TestAProviderElsewhereServesItsOwnComposedName (0.19s)
./cmd/mesh-controller --- FAIL: TestAReusedCheckBuildIsRegisteredByItsDigestAndGatedAsABuiltOne (0.13s)
./cmd/mesh-controller --- FAIL: TestTheMergeGateJudgesEachManifestAgainstTheListOfTheTree (0.40s)
./cmd/mesh-controller --- FAIL: TestRegistrationPublishesTheNewestTrunkListAndJudgesEveryModuleAgainstIt (0.42s)
./cmd/mesh-controller --- FAIL: TestADeclarationIsTheSameAfterPlacementMoves (0.55s)
./cmd/mesh-controller --- FAIL: TestAReleaseSendsTheRestAtOnceAfterTheFirstPasses (0.56s)
./cmd/mesh-controller --- FAIL: TestARestMachineThatFailsIsPutBackAloneAndTheOthersAreJudgedOn (0.40s)
./cmd/mesh-controller --- FAIL: TestAWalkTakesOverTheReadingsOfAGateJudgingTheSameBuildThere (0.29s)
./cmd/mesh-controller --- FAIL: TestAFirstSendMadeAndNotKeptIsNotSentAgain (0.22s)
./cmd/mesh-controller --- FAIL: TestAReleaseSendKeptAndMadeIsNotMadeAgain (0.25s)
./cmd/mesh-controller --- FAIL: TestAFirstMachineThatFailsStillStopsTheWalk (0.23s)
./cmd/mesh-controller --- FAIL: TestTheControlNodeIsSentLastInAStep (0.19s)
./cmd/mesh-controller --- FAIL: TestARestMachineSilentPastItsBoundIsLeftAndSaid (0.20s)
./cmd/mesh-controller --- FAIL: TestANoMoveTierWaitsForNoNewReport (0.24s)
./cmd/mesh-controller --- FAIL: TestOneProviderDownAndThreeConsumersFailingAreOneCondition (0.40s)
./cmd/mesh-controller --- FAIL: TestAConsumerFailingBesideAHealthyProviderIsItsOwn (0.32s)
./cmd/mesh-controller --- FAIL: TestTheProvisionerClientsAccountIsIssuedForItsServiceAndNeverInvented (0.44s)
./cmd/mesh-controller --- FAIL: TestAcceptOfAnOwnSecretTakesThePathOfItsModulesForm (0.16s)
./cmd/mesh-controller --- FAIL: TestAcceptForAProviderTakesThePathOfTheProvidersModule (0.22s)
./cmd/mesh-controller --- FAIL: TestAcceptForAMovedTrustedModuleAnnouncesBeforeTheVaultIsAsked (0.20s)
./cmd/mesh-controller --- FAIL: TestAcceptForAMovedModuleRecordsAHandActAndNeverTheValue (0.17s)
./cmd/mesh-controller --- FAIL: TestAcceptOfAnOutsideOfferTakesThePathOfTheProvidersModule (0.20s)
./cmd/mesh-controller --- FAIL: TestAnAskAtTheDeskTakesThePathOfItsModulesForm (0.16s)
./cmd/mesh-controller --- FAIL: TestAnIssuedValueTakesThePathOfItsProvidersModule (0.18s)
./cmd/mesh-controller --- FAIL: TestARotationTakesThePathOfItsModulesForm (0.30s)
./cmd/mesh-controller --- FAIL: TestADeclarationIsTheSameWhileTheWordsAreStillInTheLayers (0.75s)
./cmd/mesh-controller --- FAIL: TestADeclarationIsTheSameAfterTheMoveOfPlacement (0.45s)
./cmd/mesh-controller --- FAIL: TestTheSendSealsNoSecretOfAModuleHandedThere (0.18s)
./cmd/mesh-controller --- FAIL: TestAModulesSecretsAreTheVaultsOnceItIsMarkedMoved (0.18s)
./cmd/mesh-controller --- FAIL: TestEveryMachineIsToldTheSameAfterTheMoveOfConfig (0.14s)
./cmd/mesh-controller --- FAIL: TestTheMoveOfConfigRefusesWhatWouldChangeAMachine (0.13s)
./cmd/mesh-controller --- FAIL: TestTheSettingsVerbForwardsToConfigOnceTheValuesMoved (0.13s)
./cmd/mesh-controller --- FAIL: TestTheSendCarriesTheVaultsBoxForACoreCredentialAndKeepsIt (0.61s)
./cmd/mesh-controller --- FAIL: TestASilentVaultHoldsTheKeptBoxAndSaysSo (0.14s)
./cmd/mesh-controller --- FAIL: TestACoreModuleFirstPlacedWhileTheVaultIsSilentIsSealedByTheController (0.15s)
./cmd/mesh-controller --- FAIL: TestAnEngineBelowTheContractIsSentTheControllersSealAsBefore (0.17s)
./cmd/mesh-controller --- FAIL: TestModuleIssueHandsACoveredAccountToTheVaultAndOnlyThat (0.23s)
./cmd/mesh-controller --- FAIL: TestModuleIssueFailsWhenTheVaultDoesNotTakeACoveredAccount (0.34s)
./cmd/mesh-controller --- FAIL: TestModuleIssueBeforeTheVaultIsInstalledKeepsTheValueAndHandsNothing (0.30s)
./cmd/mesh-controller --- FAIL: TestARecordedModulesBundleOnlyMoveRollsOutInItsWalk (2.68s)
./cmd/mesh-controller --- FAIL: TestARecordedModulesMoveThatRecreatesAContainerWaits (1.16s)
./cmd/mesh-controller --- FAIL: TestARecordedModulesMoveThatTouchesDataOrAProviderWaits (1.93s)
./cmd/mesh-controller --- FAIL: TestAPersonsRecordAndTheBusHoldEveryMove (0.90s)
./cmd/mesh-controller --- FAIL: TestARecordedMoveThatCannotBeJudgedWaits (0.56s)
./cmd/mesh-controller --- FAIL: TestReplay867 (1.37s)
./cmd/mesh-controller --- FAIL: TestReplay867Recheck (0.31s)
./cmd/mesh-controller --- FAIL: TestTheRecheckVerbAsksMeshDeliveryOnABusOfItsOwn (0.66s)
./cmd/mesh-controller --- FAIL: TestAssigningTheClientIssuesItsAccount (0.36s)
./cmd/mesh-controller --- FAIL: TestAnUnrelatedBatchWalksBesideAnOpenWalk (0.24s)
./cmd/mesh-controller --- FAIL: TestARelatedBatchWaitsBehindTheOpenWalk (0.15s)
./cmd/mesh-controller --- FAIL: TestAnOwnPathBatchNeverWalksBeside (0.16s)
./cmd/mesh-controller --- FAIL: TestMergesHeardWhileAnotherHolderHasThePlansAreRecordedAndCarried (0.28s)
./cmd/mesh-controller --- FAIL: TestABatchWindowClosesByTheExpiryOfItsKey (1.16s)
./cmd/mesh-controller --- FAIL: TestEveryMoveAMergeAndTheCutMakeOfAPlanIsSaid (0.30s)
./cmd/mesh-controller --- FAIL: TestARolloutAdvancesOnEventsAndAReplacedControllerResumesIt (0.27s)
./cmd/mesh-controller --- FAIL: TestAWalkLetGoByTheDeliverVerbIsAskedWithNoOtherEvent (0.25s)
./cmd/mesh-controller --- FAIL: TestTwoMergesWithinAMinuteLeaveEachOpenPullRequestOneQueuedCheck (0.14s)
./cmd/mesh-controller --- FAIL: TestADeliveryGroupMovingAModuleMachinesRunPassesTheGate (0.32s)
./cmd/mesh-controller --- FAIL: TestAModuleMovesOnTheOperatorsApproveOfTheMergeThatMovedIt (0.15s)
./cmd/mesh-controller --- FAIL: TestAModuleBuiltFromANewRepositoryIsRegisteredOnlyOnTheOperatorsApproveOnTheBus (1.40s)
./cmd/mesh-controller --- FAIL: TestAMergeWhosePlanCannotBeSavedIsHeldAndRecordedWhenHandedOverAgain (0.60s)
./cmd/mesh-controller --- FAIL: TestOneReadOfAnAssignmentNamesItsCommitBuildAndRolloutAndOneReadOfTheRolloutListsItsAssignments (0.15s)
./cmd/mesh-controller --- FAIL: TestASendOfWhatAMachineRunsAlreadyChangesNoLinkOfItsAssignment (0.14s)
./cmd/mesh-controller --- FAIL: TestAnAssignmentWaitingForItsBuildIsOneKeyOfTheAssignmentsBucket (0.15s)
./cmd/mesh-controller --- FAIL: TestNoTableOfTheControllersStoreHoldsBuildsRolloutsOrAssignments (0.13s)
./cmd/mesh-controller FAIL: go test exited 1
./internal/inventory --- PASS: TestTheLastSendSaysWhatTheMachineAnswered (0.11s)
./internal/inventory --- PASS: TestAReportIsTheLastSendsAnswerOnlyWhenItIsAboutThatSend (0.16s)
./internal/inventory --- PASS: TestAnIssuedValueIsSealedToEveryHolderOnceAndNotAgain (0.10s)
./internal/inventory --- PASS: TestAnIssuedValueIsSealedAgainAfterAKeyChangeOrAnAcceptance (0.10s)
./internal/inventory --- PASS: TestAConditionsLooksAreKeptBesideTheBucket (0.08s)
./internal/inventory --- PASS: TestAPlanIdHoldingAQuoteIsReadAsAPlainId (0.13s)
./internal/inventory --- PASS: TestAWalksStartIsKeptAndARefusedSaveLeavesItUnsaid (0.09s)
./internal/inventory --- PASS: TestAWalksRestIsReadFromEachMachinesOwnSend (0.15s)
./internal/inventory --- PASS: TestAStoredBuildWithASilentMergeableFileIsStillReadAndComposed (0.10s)
./internal/inventory --- PASS: TestACredentialIssuedOutsideIsNeverMade (0.11s)
./internal/inventory --- PASS: TestOneAcceptForAProviderIsSealedToEveryConsumer (0.14s)
./internal/inventory --- PASS: TestASharedOwnSecretIssuedOutsideIsNeverMade (0.16s)
./internal/inventory --- PASS: TestAModuleInTheConfigFormIsMirroredWithItsWholeDeclaration (0.11s)
./internal/inventory --- PASS: TestAReportOfABusyContainerIsKeptAndReadBack (0.10s)
./internal/inventory --- PASS: TestANewerBuildsListReplacesTheKeptOneAndAnOlderOneHeardLaterDoesNot (0.14s)
./internal/inventory --- PASS: TestPlacementMovesOutOfTheSettingsLayers (0.68s)
./internal/inventory --- PASS: TestASettingRoutesPlacementBesideTheLayer (0.13s)
./internal/inventory --- PASS: TestTheProvisionerClientsMachineHasAnAccountOfItsOwn (0.43s)
./internal/inventory --- PASS: TestTheFourWordsAreKeptBesideTheLayer (0.10s)
./internal/inventory --- PASS: TestALayerStillHoldingTheWordsReadsThemAsPlacement (0.09s)
./internal/inventory --- PASS: TestTheMoveOfPlacementMovesWhatTheLayersStillHold (0.10s)
./internal/inventory --- PASS: TestTheMoveReadsEveryRowSealedToAMachineAsItIs (0.17s)
./internal/inventory --- PASS: TestASendKeepsThePlansItHandedAndTheMirrorCarriesThem (0.16s)
./internal/inventory --- PASS: TestTheLayersAreReadUntilTheMoveOfConfigHasRun (0.09s)
./internal/inventory --- PASS: TestAModuleReadsMeshConfigOnlyWhereItsValuesAre (0.09s)
./internal/inventory --- PASS: TestTheEndOfTheMoveRefusesALayerChangedSinceItWasRead (0.41s)
./internal/inventory --- PASS: TestACoreCredentialsVaultBoxIsKeptPerMachineAndReplaced (0.24s)
./internal/inventory --- PASS: TestWhatRunsIsTheRegisteredBuildNotANewerOnePutBack (0.10s)
./internal/inventory --- PASS: TestBuildsOnTheBusAreReadBackByEveryReader (0.07s)
./internal/inventory --- PASS: TestARequestIsTheBuildInStateAskedAndItsOutcomeTakesItsPlace (0.07s)
./internal/inventory --- PASS: TestAnAssignmentIsAKeyOfTheBucketAndAnUnassignmentEndsIt (0.11s)
./internal/inventory --- FAIL: TestThePlansAreKeptInTheAssignmentsValuesAndNothingElseOfThemMoves (0.08s)
./internal/inventory --- FAIL: TestAPendingAssignmentIsAKeyOfTheAssignmentsBucket (0.08s)
./internal/inventory --- PASS: TestARecordedPendingIsSkippedByAssignedAndTheJoins (0.08s)
./internal/inventory --- PASS: TestTwoClaimsOfOnePendingMakeOneAndTheOtherSeesFalse (0.08s)
./internal/inventory --- PASS: TestAssignOverAPendingKeepsItsRecordAsApplied (0.08s)
./internal/inventory --- PASS: TestAPendingIsMarkedOnceAndGoesWithItsMachine (0.09s)
./internal/inventory --- PASS: TestAReplacedWaitNeverLeavesTheOperatorWithoutItsCondition (0.07s)
./internal/inventory --- PASS: TestSentBuildsAnswersFromTheAssignmentsKeysOfTheNode (0.08s)
./internal/inventory --- PASS: TestASendReplacesTheWholeMapOfTheNodeAndAHandSendMakesItUnknown (0.08s)
./internal/inventory --- PASS: TestAFailedWriteOfTheLinksFailsTheRecordOfTheSend (0.07s)
./internal/inventory --- PASS: TestMigration0105RefusesAStoreWhoseRowsWereNotMovedAndDropsTheTablesOfAMovedOne (0.45s)
./internal/inventory --- PASS: TestMigration0105PassesAStoreThatNeverHeldARow (0.12s)
./internal/inventory --- PASS: TestTheColumnOfASentMachineIsCopiedOntoItsKeysAndEmptied (0.08s)
./internal/inventory --- PASS: TestASendEmptiesTheColumnSoALaterCopyLeavesAClearedKeyBare (0.08s)
./internal/inventory FAIL: go test exited 1
./internal/recordmirror --- PASS: TestNatsAnAssignmentAndARegistrationEachChangeOneKeyAndRaiseOneEvent (2.00s)
./internal/recordmirror --- PASS: TestNatsTheListOfPredefinedKeysKeptChangesTheMirrorsOneKey (1.44s)
114 store test(s) listed in testdata/store-tests did not run and pass against the store
--- what failed, picked from the whole of its output (the whole is in the build's log)
--- FAIL: TestAnAssignmentThatBlocksAnotherMachineSaysWhichAndWhy (1.02s)
acts_test.go:27: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestConvergingIsRefusedOnAPreviewThatWouldBeStale (1.08s)
adopting_test.go:134: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestTheFlipHoldsTheNodeWhileItSends (0.72s)
adopting_test.go:502: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAPlanCutFromAMergeOfABackedUpModuleAsksItsBackupAndNotItsTierUntilItIsDone (0.71s)
backups_before_send_integration_test.go:226: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAFailedWalkWalksItsEarlierMergesAlone (0.60s)
batches_integration_test.go:341: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestARepositoryMadeAgainUnderItsNameIsNotTheModulesSource (0.57s)
build_source_integration_test.go:214: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestASendAssertsWhatWasAssignedAfterStart (0.87s)
busobjects_test.go:84: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestNoTableOfTheControllersStoreHoldsBuildsRolloutsOrAssignments (1.03s)
chain_no_table_integration_test.go:18: the builds are not laid out under their modules yet; the controller's start does it and says so
the checks' builds of 1 pull request(s) could not be read, so the walk builds: no bus
--- FAIL: TestTwoMergesWithinAMinuteLeaveEachOpenPullRequestOneQueuedCheck (0.74s)
checks_queue_test.go:25: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestTheMoveOfConfigRefusesWhatWouldChangeAMachine (0.52s)
config_moved_integration_test.go:262: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAnEngineBelowTheContractIsSentTheControllersSealAsBefore (0.67s)
core_box_integration_test.go:121: the builds are not laid out under their modules yet; the controller's start does it and says so
novox/mesh-catalog changed more files than were listed: the manifests of its modules (modules/a/module.json) are read as changed
novox/mesh-catalog changed more files than were listed: the manifests of its modules (modules/a/module.json) are read as changed
--- FAIL: TestAMachineWhoseDeclarationDoesNotComposeIsSaid (0.63s)
doctor_integration_test.go:127: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestABuildThatFailsItsGateIsRolledBackOnItsFirstMachineAndGoesNoFurther (0.50s)
gate_integration_test.go:142: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestNatsH3AssertsAMissingConsumerAgainAndBrakesAfterItsBudget (0.59s)
healers_integration_test.go:253: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestANamedPushStillSendsAConsequenceNothingHolds (2.56s)
held_back_integration_test.go:130: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestSavingPlansAndMovingMergesIsOneAct (0.73s)
issue459_integration_test.go:268: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestNodeShowAndStatusReadTheLastSendFromTheStore (0.76s)
last_send_integration_test.go:14: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAMachineSilentPastItsBoundIsLeftAndSaidAtOnce (0.50s)
lean_walk_integration_test.go:95: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestARelatedMergeJoinsTheBatchAndWaitsForTheWindow (2.75s)
--- FAIL: TestARelatedMergeJoinsTheBatchAndWaitsForTheWindow/same_repository (0.41s)
lone_merge_test.go:41: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestARelatedMergeJoinsTheBatchAndWaitsForTheWindow/a_module_in_common (0.73s)
lone_merge_test.go:41: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestARelatedMergeJoinsTheBatchAndWaitsForTheWindow/an_edge_of_the_graph (0.50s)
lone_merge_test.go:41: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestARelatedMergeJoinsTheBatchAndWaitsForTheWindow/the_same_group_head (1.10s)
lone_merge_test.go:41: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestALoneMergeRelatedToAWalkTheCutFoldsJoinsTheBatch (0.53s)
lone_merge_test.go:314: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAFailedUnitIsTheModulesConditionAndTheMachinesOwnAreOneFinding (0.61s)
machine_units_integration_test.go:15: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAManifestTheRunningControllerCannotReadFailsThePullRequest (0.58s)
merge_gate_integration_test.go:124: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestTheResolverIsToldEveryMachineOnTheNetworkAndToldAgainWhenOneLeaves (1.93s)
network_test.go:260: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAskingAboutAMachineTheMeshHasNeverHeardOfIsRefused (0.89s)
nodes_test.go:98: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAnUnassignThatLeavesItsNodeResolvedSaysNothingOfIt (1.49s)
one_resolution_integration_test.go:38: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAStatusReadSettlesNothing (0.48s)
pending_integration_test.go:115: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAnUnknownModuleIsRefusedWithTheClosestNames (0.92s)
pending_integration_test.go:388: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestABuildNoLongerWaitedForIsStillInFlight (0.69s)
pending_integration_test.go:709: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAssigningTheClientIssuesItsAccount (0.31s)
provisioner_account_integration_test.go:55: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAPlanStoppedAtItsFirstMachineIsRetried (0.30s)
queue_integration_test.go:336: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestReplay348AFaultFromBeforeTheSendFailsNoGate (0.41s)
replay348_test.go:27: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestReplay273AConsumerBesideItsStoreStaysBoundToIt (0.29s)
replays_integration_test.go:50: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAReleaseSendsTheRestAtOnceAfterTheFirstPasses (0.29s)
rest_at_once_integration_test.go:40: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAnUnhealthyOwnRuntimeRaisesTheModulesUsualCondition (0.24s)
runtime_health_test.go:17: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestADefinitionMovingUnderAStoredSettingLeavesThatModuleOutNotTheMachine (0.55s)
sendable_integration_test.go:302: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestPreferencesListedFromTheStores (0.24s)
settings_effective_integration_test.go:13: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestASettingsWalkStopsBeforeADataMoveAndPassesOverAMachineAway (0.23s)
settings_walk_integration_test.go:315: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestTheAgentsManagedSettingsAreRefusedThroughAVerb (0.25s)
terminal_settings_test.go:223: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestATierPutsABrokenModuleBackAtOnce (0.47s)
--- FAIL: TestATierPutsABrokenModuleBackAtOnce/gate_kept_on_node-tools (0.23s)
tier_send_integration_test.go:325: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestATierPutsABrokenModuleBackAtOnce/gate_kept_on_app1 (0.24s)
tier_send_integration_test.go:325: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAHeldModuleIsFoundFromWhatTheMachineReported (0.26s)
untaken_integration_test.go:27: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAcceptForAMovedModuleRecordsAHandActAndNeverTheValue (0.23s)
vault_switch_test.go:386: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAWalkStoppedByHandAndRetriedEndsFailedWhenItFailsAgain (0.35s)
walk_said_integration_test.go:233: the builds are not laid out under their modules yet; the controller's start does it and says so
FAIL github.com/novox/mesh-controller/cmd/mesh-controller 34s (shard 1 of 8: 140 tests)
--- FAIL: TestAConsumerAssignedBeforeItsProviderIsStillAssigned (1.16s)
acts_test.go:84: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestTheFlipIsRefusedWhileAFoundContainerIsHeld (1.05s)
adopting_test.go:145: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestThePreviewNamesEveryHeldKind (0.64s)
adopting_test.go:547: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestTheSelfCheckSaysAnAgentAccountThatCanBecomeRoot (0.82s)
agent_account_integration_test.go:18: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAModuleAssignedAndNotPushedIsAwaitingAPushNotUncomposable (0.61s)
awaiting_push_integration_test.go:17: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestTwoMergesSecondsApartAreOneWalkAtTheLaterCommit (0.58s)
batches_integration_test.go:66: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAGroupsOrderBecomesTiersInsideTheWalk (0.78s)
batches_integration_test.go:408: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestABuildFromAnAgentsRepositoryIsNotRegisteredAsAModuleTheMeshHolds (0.88s)
build_source_integration_test.go:39: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestATerminalRequestCoversOnlyWhatItAsked (0.86s)
build_source_integration_test.go:240: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestASendThatCannotAssertTheBusSaysSoAndRaisesACondition (0.56s)
busobjects_test.go:123: the builds are not laid out under their modules yet; the controller's start does it and says so
the earlier checks' builds of novox/shop#7 could not be read, so the check builds: no bus
--- FAIL: TestTheSettingsVerbForwardsToConfigOnceTheValuesMoved (0.69s)
config_moved_integration_test.go:306: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestNatsTheBusIsWhatTheControllerDefines (0.41s)
doctor_integration_test.go:149: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAFaultBeforeTheSettleTimeWaitsForTheModuleBesideIt (0.49s)
gate_followup_test.go:64: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestABuildThatPassesItsGateRollsEverywhereUnattended (0.53s)
gate_integration_test.go:231: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestNatsH4ResetsTheControllersEventsConsumerAndItStillDelivers (2.68s)
healers_integration_test.go:343: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestASecondEligibleHolderStandsBesideTheOneHeldByBeingAlone (0.55s)
holdings_test.go:25: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAnOverflowingConsumerNeverRefusesItsProvidersMachine (0.59s)
identity_bound_integration_test.go:14: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAMergeOfAGroupWaitsEvenAlone (0.45s)
lone_merge_test.go:102: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAModuleAMachineRunsRemovedFromItsSourceFails (0.43s)
merge_gate_integration_test.go:133: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestTheRosterNamesOnlyTheMachines (1.87s)
network_test.go:316: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestANodeAddedAdoptedIsAdopted (2.11s)
nodes_test.go:107: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAnAssignThatLeavesItsNodeUnresolvedSaysOnlyThePlansRefusal (0.44s)
one_resolution_integration_test.go:57: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAPendingAssignmentExpiresWhenItsBuildFails (0.71s)
pending_integration_test.go:138: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAnActWithAModuleNotRegisteredIsRefusedWhole (0.79s)
pending_integration_test.go:412: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestOneProviderDownAndThreeConsumersFailingAreOneCondition (0.39s)
provider_hold_test.go:24: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAPlanIsAnsweredOnlyByTheBuildItAskedFor (0.32s)
queue_integration_test.go:403: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestARecordedModulesBundleOnlyMoveRollsOutInItsWalk (0.27s)
recorded_moves_test.go:187: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestTheBacklogIsReleasedOneMachineAtATimeEachJudged (0.29s)
release_test.go:176: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestReplay318 (0.23s)
replay318_test.go:37: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestReplay349 (0.29s)
replay349_test.go:24: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestReplayCrashLoopFailsItsGateOnTheFirstMachine (0.28s)
replays_integration_test.go:111: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestARestMachineThatFailsIsPutBackAloneAndTheOthersAreJudgedOn (0.27s)
rest_at_once_integration_test.go:66: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestASetThatDoesNotComposeIsMarkedAsTheNodesOwnProblem (1.37s)
roster_failure_test.go:15: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAWalkWhoseEveryBuildCameOutTheSameIsDone (0.48s)
same_program_integration_test.go:17: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestACrossingSendSupersedesASettingsGate (0.93s)
settings_walk_integration_test.go:361: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestTheMergeGateJudgesAChangeToATemplateAlone (1.05s)
template_integration_test.go:47: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAnyKeyOfAModuleWithATrustedMergeableFileIsRefusedThroughAVerb (1.02s)
terminal_settings_test.go:293: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestASendCarryingTheToolRunnerWaitsForItsWitnessWindow (0.35s)
tier_send_integration_test.go:380: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestPlanAndNodeListAnOptionalRequirementLeftUnbound (1.03s)
unbound_test.go:16: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestTheJSONStatusCarriesWhatIsHeldAndForWhichModule (0.28s)
untaken_integration_test.go:43: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAcceptOfAnOwnSecretTakesThePathOfItsModulesForm (1.09s)
vault_switch_test.go:117: the builds are not laid out under their modules yet; the controller's start does it and says so
FAIL github.com/novox/mesh-controller/cmd/mesh-controller 45s (shard 2 of 8: 140 tests)
--- FAIL: TestUnassigningAProviderNamesWhoIsNowBlocked (1.00s)
acts_test.go:105: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestTakingNamesWhatItReplaces (1.05s)
adopting_test.go:157: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestTheFlipIsRefusedOnAnAccountNamingNothingReachable (0.70s)
adopting_test.go:590: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestTheFactsCarryTheAgentAccountAsAPseudonym (0.78s)
agent_account_integration_test.go:68: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestASecretThePushCannotMakeIsStillUncomposable (0.67s)
awaiting_push_integration_test.go:72: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestThreeRepositoriesInOneWindowAreOneWalk (0.58s)
batches_integration_test.go:110: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestABatchSurvivesARestart (0.89s)
batches_integration_test.go:444: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestANewModuleFromARepositoryTheCatalogueDoesNotBuildFromIsNotRegistered (0.80s)
build_source_integration_test.go:71: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestNatsAModuleAssignedAfterStartGetsItsConsumerAtItsFirstSend (0.83s)
busobjects_test.go:165: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAComposedMembersCheckIsItsRepositoryChecksAlone (2.34s)
composed_member_check_test.go:48: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAnApprovalRaisedBeforeTheMoveOfConfigIsRefusedAfterIt (0.56s)
config_moved_integration_test.go:404: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAMergeWaitsForItsDeliverysWordAndThePersonsWordWorksWithoutIt (0.72s)
delivery_integration_test.go:20: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAMachineIsSentTheEpochOnlyOnceItSaysItReadsOne (0.38s)
epoch_send_test.go:30: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAPassIsCountedNoFasterThanTheGatesSpacing (0.73s)
gate_followup_test.go:106: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestABuildRollsToEveryMachineAtOnceWithNoGate (0.70s)
gate_integration_test.go:254: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestTheGrantsStepSendsTheUserListAndNothingElse (0.65s)
grants_step_store_test.go:27: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAGroupsBatchWaitsForItsLastMemberHoweverLongItTakes (0.47s)
group_one_batch_test.go:18: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAHolderOnRecordIsNotRewrittenByDerivation (0.69s)
holdings_test.go:83: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAWalkThatMovedNothingSaysWhichModulesMatchedWhatRuns (0.68s)
issue611_integration_test.go:14: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAHeadedMergeInNoGroupIsCutAtOnce (1.00s)
lone_merge_test.go:134: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestIssue278AWideRebuildIsSaidBeforeTheMerge (1.78s)
merge_gate_integration_test.go:141: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestTwoUnhealthyStatementsRaiseTheModulesConditionAndAHealthyOneClearsIt (0.90s)
module_health_test.go:39: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestPlacingANodeWithNothingSaidDoesNotUnplaceIt (0.58s)
network_test.go:38: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAMergeBuildsTheNewModuleItAdds (0.33s)
new_module_on_merge_test.go:33: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestATokenIssuedAdoptedSaysSoAndReissuingDoesNotConverge (0.31s)
nodes_test.go:128: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestTheConditionClearsWhenTheModuleIsAssignedLater (0.28s)
pending_integration_test.go:205: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestUnassignWithdrawsAPendingAssignment (0.29s)
pending_integration_test.go:427: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestADeclarationIsTheSameAfterPlacementMoves (0.40s)
placement_moved_test.go:24: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAControllerLeavesThePlansToTheOneHoldingThem (0.24s)
plans_one_at_a_time_test.go:16: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAConsumerFailingBesideAHealthyProviderIsItsOwn (0.25s)
provider_hold_test.go:145: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAPushSaysWhatItRecreates (0.23s)
push_recreates_test.go:20: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAFailedPlanIsRetriedAndGoesOnThroughItsLaterTiers (0.23s)
queue_integration_test.go:22: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestARebuildOfACommitAsksWhatTheModuleFollows (0.34s)
queue_integration_test.go:429: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestARecordedModulesMoveThatRecreatesAContainerWaits (0.54s)
--- FAIL: TestARecordedModulesMoveThatRecreatesAContainerWaits/image (0.23s)
recorded_moves_test.go:231: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestARecordedModulesMoveThatRecreatesAContainerWaits/spec (0.30s)
recorded_moves_test.go:231: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAFailedReleaseIsPutBackAndTheNextWaitsForAPerson (0.25s)
release_test.go:231: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestReplay325 (0.43s)
replay325_test.go:23: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestReplay401 (1.57s)
replay401_test.go:20: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestReplaySilentWebAppIsRaisedWithinTwoLooks (0.76s)
replays_integration_test.go:269: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAWalkTakesOverTheReadingsOfAGateJudgingTheSameBuildThere (1.14s)
rest_at_once_integration_test.go:101: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAStoreThatCannotBeReadIsNotANodeThatDoesNotCompose (0.96s)
roster_failure_test.go:35: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAModulePulledInIsHandedOnAMachineThatCanTakeItAndMirrored (0.99s)
sent_required_by_integration_test.go:17: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestASettingsWalkFailsOnARefusalThatCannotClear (1.02s)
settings_walk_integration_test.go:400: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestOnlyATrustedFilesNamedKeyIsRefusedThroughAVerb (1.42s)
terminal_settings_test.go:353: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAnAssignmentSaysOnlyWhatItChangedOnItsOwnNode (0.26s)
unheld_report_integration_test.go:13: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAcceptForAProviderTakesThePathOfTheProvidersModule (0.21s)
vault_switch_test.go:151: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAWalkLetGoAndStoppedByVerbsIsSaidStartedAndEnded (0.20s)
walk_said_integration_test.go:20: the builds are not laid out under their modules yet; the controller's start does it and says so
FAIL github.com/novox/mesh-controller/cmd/mesh-controller 45s (shard 3 of 8: 140 tests)
--- FAIL: TestTheRegistryTrustAndEveryImageFollowThePortTheNodeGaveTheStore (1.02s)
addresses_integration_test.go:17: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestATakeIsRefusedOnAChangedPreviewOrAStaleAccount (1.09s)
adopting_test.go:201: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAssigningWaitsForWhateverIsConvergingTheNode (0.70s)
adopting_test.go:618: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestASearchStillRunningAfterARestartIsNotUrgent (0.76s)
agent_account_integration_test.go:99: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAGivenSecretUnderAnOldKeyIsNotForeseen (0.61s)
awaiting_push_integration_test.go:105: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAMergeRestartsTheWindowAndTheMaximumClosesIt (0.60s)
batches_integration_test.go:144: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestALateMergeOfAOneModuleRepositoryIsNamed (0.80s)
batches_integration_test.go:469: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAnUnrelatedBatchWalksBesideAnOpenWalk (0.79s)
beside_test.go:16: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAtTheTerminalAnotherRepositoryIsRegistered (0.97s)
build_source_integration_test.go:91: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAnUnknownIdentityKeepsTheRecordedOne (0.54s)
build_source_integration_test.go:275: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestOneReadOfAnAssignmentNamesItsCommitBuildAndRolloutAndOneReadOfTheRolloutListsItsAssignments (0.64s)
chain_integration_test.go:26: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAReusedCheckBuildIsRegisteredByItsDigestAndGatedAsABuiltOne (0.59s)
check_builds_integration_test.go:39: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAMemberOfAGroupOfAnOlderMeshDeliveryKeepsItsOwnGate (0.44s)
composed_member_check_test.go:56: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAPlacementOnlyApprovalRaisedBeforeTheMoveIsSetAfterIt (0.46s)
config_moved_integration_test.go:442: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAWalkLetGoByAVerbIsSaidAsPlanMoved (2.56s)
delivery_integration_test.go:152: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestNothingIsComposedOrSentWithoutTheLease (0.66s)
epoch_send_test.go:87: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestACarriedPassCarriesOnlyItsOwnWait (0.69s)
gate_followup_test.go:131: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestALeafModulePassesOnOneHealthyReading (0.43s)
gate_integration_test.go:280: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAGroupWithAMemberOfEachKindIsOneBatchAndOneWalk (1.30s)
--- FAIL: TestAGroupWithAMemberOfEachKindIsOneBatchAndOneWalk/controller_member_first (0.57s)
group_one_batch_test.go:52: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAGroupWithAMemberOfEachKindIsOneBatchAndOneWalk/catalogue_member_first (0.73s)
group_one_batch_test.go:52: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestH1AsksAMachineToReportAndSendsItAgain (0.69s)
healers_integration_test.go:22: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestAReportedHostVersionIsKeptAndReadBack (0.69s)
hosts_behind_integration_test.go:11: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestReplay201 (0.55s)
issue201_integration_test.go:69: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestReplay352 (1.21s)
--- FAIL: TestReplay352/a_newer_send_to_the_judged_machine_does_not_unreport_the_gate's (0.64s)
issue352_integration_test.go:27: the builds are not laid out under their modules yet; the controller's start does it and says so
--- FAIL: TestReplay352/a_send_that_moves_the_module_supersedes_the_judging (0.57s)
issue352_integration_test.go:106: the builds are not laid out under their modules yet; the controller's start does it and says so
… 500 more line(s) naming what failed, past the 400 lines or 32 KiB kept
```
mesh/merge-gate head cbc6bac8c070 merged into trunk da6d038e07c0 — error: builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step; the m…
mesh/repo-check head cbc6bac8c070 merged into trunk da6d038e07c0 — fail: its merge-check.sh failed: --- FAIL: TestTheGrantsStepSendsTheUserListAndNothingEl…
The fixtures' fresh chain writes the layout marker, as the controller's start leaves a mesh, so the gate stays for the live start. A pending wait that ended unanswered is carried by the next one, so both are known. A hand send forgets what each assignment runs, so the test writes its build and commit after the send.
Merge check at cbc6bac8
Judged: head cbc6bac8c070 merged into trunk da6d038e07c0; read beside it: mesh-catalog 7f77ce663a9e, mesh-controller-main da6d038e07c0, mesh-host 6469e8238443, mesh-tools 7412c5b6c9c5
mesh/merge-gate: ERROR — the mesh as it is could not be raised, so the change cannot be judged against it (4 of 4 machines compose on the mesh and not in the gate); the first: a machine (f35) composes on the mesh and not as the gate raised it from the snapshot: the private network cannot be computed: whether f35 answers "mesh-addressing" cannot be read: this kind of record lives on the bus, and this process has not opened the bus: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus (modules: build-agent, mesh-controller)
mesh/repo-check: FAIL — its merge-check.sh failed: --- FAIL: TestTheGrantsStepSendsTheUserListAndNothingElse (0.53s); and TestADeliveryGroupsHeadsAreComposedTogether, TestIssue285AModuleOnTheBusComposesInTheGate, TestMergesHeardWhileAnotherHolderHasThePlansAreRecordedAndCarried, TestALastSendIsReadFromTheSendAndTheReport, TestIssue285AMachineTheGateCannotRaiseIsAnErrorNeverAPass and 4 more
Delivery plan — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
tier 0: mesh-controller
tier 1: build-agent
ace: receives build-agent
g14: receives build-agent
novox: receives mesh-controller, build-agent
shanks: receives build-agent
build-agent keeps data (ADR 0233): what it holds is backed up before it moves
grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before build-agent is judged on its first machine
Run by the build seat on ace as build-1792324330116343529 (builds --log build-1792324330116343529).
plan-gate: the send to anchor in tier 0 failed its gate: not healthy within -1s of its apply: anchor has not reported on what it was sent; app was left as it was — anchor already ran app c2, or a build identical to it, before the send, so nothing of it moved and nothing is put back
plan-gate: the send to anchor in tier 0 failed its gate: not healthy within -1s of its apply: anchor has not reported on what it was sent; app was left as it was — anchor already ran app c2, or a build identical to it, before the send, so nothing of it moved and nothing is put back; none reported left as it was
tier 0: the vault now holds accept/token (generation 1), accepted: sealed at this terminal to the vault's key for this call, opened in the vault alone and never remade by it; its machine takes it from the vault
this act could NOT be recorded in the hand-act log, and is done anyway: the hand-act log mesh-controller_hand-acts is not on the bus — the controller asserts it at its start, so one older than this has not: nats: bucket not found
the vault now holds accept/token (generation 1), accepted: sealed at this terminal to the vault's key for this call, opened in the vault alone and never remade by it; its machine takes it from the vault
this change could NOT be announced on the operator's channels: no channel took it
this act could NOT be recorded in the hand-act log, and is done anyway: the hand-act log mesh-controller_hand-acts is not on the bus — the controller asserts it at its start, so one older than this has not: nats: bucket not found
tier 0: rebuild asked as build-1792324564866430518, joining plan-308-rebuild at tier 0 (novox/a at c0ffee): the plan takes this build as a's outcome; the plan had failed and builds again from this tier
FAIL
FAIL github.com/novox/mesh-controller/cmd/mesh-controller 131s (shard 8 of 8: 139 tests)
ok github.com/novox/mesh-controller/internal/inventory 16s (shard 1 of 4: 89 tests)
builds: the pointer alpha.newest was missing or wrong (a lookup of alpha.commit.c4) and is repaired from the records of alpha
builds: the pointer alpha.worked was missing or wrong (a lookup of alpha.commit.c4) and is repaired from the records of alpha
builds: the pointer alpha.held was missing or wrong (a lookup of alpha.commit.c4) and is repaired from the records of alpha
builds: the pointer alpha.commit.c4 was missing or wrong (a lookup of alpha.commit.c4) and is repaired from the records of alpha
builds: the pointer alpha.source.v1-s4 was missing or wrong (a lookup of alpha.commit.c4) and is repaired from the records of alpha
builds: the pointer alpha.commit.c2 was missing or wrong (a lookup of alpha.commit.c2) and is repaired from the records of alpha
--- FAIL: TestAPendingAssignmentIsAKeyOfTheAssignmentsBucket (0.18s)
chain_pending_test.go:61: the earlier wait is in the key's history: 3 values
FAIL
FAIL github.com/novox/mesh-controller/internal/inventory 12s (shard 2 of 4: 89 tests)
ok github.com/novox/mesh-controller/internal/inventory 13s (shard 3 of 4: 88 tests)
ok github.com/novox/mesh-controller/internal/inventory 15s (shard 4 of 4: 88 tests)
ok github.com/novox/mesh-controller/internal/builder 15s (shard 1 of 4: 54 tests)
ok github.com/novox/mesh-controller/internal/builder 17s (shard 2 of 4: 53 tests)
ok github.com/novox/mesh-controller/internal/builder 25s (shard 3 of 4: 53 tests)
ok github.com/novox/mesh-controller/internal/builder 15s (shard 4 of 4: 53 tests)
ok github.com/novox/mesh-controller/internal/link 22s (shard 1 of 4: 50 tests)
ok github.com/novox/mesh-controller/internal/link 15s (shard 2 of 4: 50 tests)
ok github.com/novox/mesh-controller/internal/link 16s (shard 3 of 4: 49 tests)
ok github.com/novox/mesh-controller/internal/link 23s (shard 4 of 4: 49 tests)
integration level (the whole suite, tag integration): 3404 tests (6 skipped outside the shards), 159 s
nested module modules/build-agent:
ok build-agent 1.012s
nested module modules/route-proxy:
ok route-proxy/cmd/route-provider 1.012s
nested modules: 3 s
store tests, each run against the store:
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeWalksTheOthersAgain (0.33s)
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeEndsTheMergesThatContainIt (0.28s)
./cmd/mesh-controller --- PASS: TestAStopWalksTheOthersAgainInTheOpenBatch (0.23s)
./cmd/mesh-controller --- PASS: TestAStopNamesWhatStaysOnTheMachinesAndWhatStillCarriesIt (0.24s)
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeLeavesItOutOfABatch (0.20s)
./cmd/mesh-controller --- PASS: TestSavingPlansAndMovingMergesIsOneAct (0.19s)
./cmd/mesh-controller --- PASS: TestAPlanFollowedFromTheStoreAnswersWhenItMoves (1.98s)
./cmd/mesh-controller --- PASS: TestIssue969TheGateRaisesEachMachineAsItsEngineStatedItself (0.77s)
./cmd/mesh-controller --- PASS: TestNodeShowAndStatusReadTheLastSendFromTheStore (0.27s)
./cmd/mesh-controller --- PASS: TestTheConditionsVerbReadsTheLooksTheBucketNoLongerHolds (0.15s)
./cmd/mesh-controller --- PASS: TestAWalkLetGoAndStoppedByVerbsIsSaidStartedAndEnded (0.23s)
./cmd/mesh-controller --- PASS: TestAWalkStoppedOrClosedByAPersonIsSaidEndedStopped (0.26s)
./cmd/mesh-controller --- PASS: TestAWalkRetriedByAPersonIsSaidStartedAgain (0.19s)
./cmd/mesh-controller --- PASS: TestABacklogReleasedByAPersonIsSaidStarted (0.20s)
./cmd/mesh-controller --- PASS: TestAWalkEndedByCancelOrClearIsSaidEnded (0.26s)
./cmd/mesh-controller --- PASS: TestAWalkRestartedByARebuildIsSaidStarted (0.20s)
./cmd/mesh-controller --- PASS: TestAWalkStoppedByHandAndRetriedEndsFailedWhenItFailsAgain (0.23s)
./cmd/mesh-controller --- PASS: TestReplay237 (0.20s)
./cmd/mesh-controller --- PASS: TestAnUnassignThatLeavesItsNodeUnresolvedSaysSoOnceInItsAnswer (0.23s)
./cmd/mesh-controller --- PASS: TestAnUnassignThatLeavesItsNodeResolvedSaysNothingOfIt (0.24s)
./cmd/mesh-controller --- PASS: TestAnAssignThatLeavesItsNodeUnresolvedSaysOnlyThePlansRefusal (0.23s)
./cmd/mesh-controller --- PASS: TestADirectoryOwnersKeyIsRefusedThroughAVerb (0.24s)
./cmd/mesh-controller --- PASS: TestTheSendMakesNoValueForAnOutsideSecretNobodyGave (0.35s)
./cmd/mesh-controller --- PASS: TestAQuestionComposesWithoutAnOutsideSecretNobodyGave (0.30s)
./cmd/mesh-controller --- PASS: TestReplay201 (0.17s)
./cmd/mesh-controller --- PASS: TestARollbackWhoseSendWasRefusedIsCompletedByTheNextSend (0.18s)
./cmd/mesh-controller --- PASS: TestAGateJudgesTheOtherMovesBesideAKeptCore (0.20s)
./cmd/mesh-controller --- PASS: TestReplay401 (0.29s)
./cmd/mesh-controller --- PASS: TestReplay201ThePlansSend (0.24s)
./cmd/mesh-controller --- PASS: TestPlanAndNodeListAnOptionalRequirementLeftUnbound (0.31s)
./cmd/mesh-controller --- PASS: TestReplay340 (0.26s)
./cmd/mesh-controller --- PASS: TestOnlyATrustedFilesNamedKeyIsRefusedThroughAVerb (0.20s)
./cmd/mesh-controller --- PASS: TestReplay349 (0.20s)
./cmd/mesh-controller --- PASS: TestReplay348AFaultFromBeforeTheSendFailsNoGate (0.19s)
./cmd/mesh-controller --- PASS: TestReplay239AModuleNameIsNotTakenOverByAnotherRepository (0.14s)
./cmd/mesh-controller --- PASS: TestAWalkThatMovedNothingSaysWhichModulesMatchedWhatRuns (0.20s)
./cmd/mesh-controller --- PASS: TestAWalkWhoseEveryBuildCameOutTheSameIsDone (0.16s)
./cmd/mesh-controller --- PASS: TestReplay614ANewSDKPlansTheToolchainAndThenItsBundles (0.08s)
./cmd/mesh-controller --- PASS: TestOneAcceptForAProviderIsPlacedForEveryConsumer (0.56s)
./cmd/mesh-controller --- PASS: TestReplay164 (0.29s)
./cmd/mesh-controller --- PASS: TestAnApprovedLayerOpensTheWalkThatSendsIt (0.19s)
./cmd/mesh-controller --- PASS: TestASettingsWalkSendsOneMachineAtATimeEachJudged (0.18s)
./cmd/mesh-controller --- PASS: TestAFailedSettingsWalkStopsAndHoldsNothingBack (0.19s)
./cmd/mesh-controller --- PASS: TestASettingsWalkSendsTheLayerAloneEveryBuildKept (0.17s)
./cmd/mesh-controller --- PASS: TestASettingsWalkStopsBeforeADataMoveAndPassesOverAMachineAway (0.49s)
./cmd/mesh-controller --- PASS: TestACrossingSendSupersedesASettingsGate (0.16s)
./cmd/mesh-controller --- PASS: TestASettingsWalkFailsOnARefusalThatCannotClear (0.15s)
./cmd/mesh-controller --- PASS: TestAProviderElsewhereServesItsOwnComposedName (0.36s)
./cmd/mesh-controller --- PASS: TestAReusedCheckBuildIsRegisteredByItsDigestAndGatedAsABuiltOne (0.28s)
./cmd/mesh-controller --- PASS: TestTheMergeGateJudgesEachManifestAgainstTheListOfTheTree (4.30s)
./cmd/mesh-controller --- PASS: TestRegistrationPublishesTheNewestTrunkListAndJudgesEveryModuleAgainstIt (0.20s)
./cmd/mesh-controller --- PASS: TestADeclarationIsTheSameAfterPlacementMoves (0.36s)
./cmd/mesh-controller --- PASS: TestAReleaseSendsTheRestAtOnceAfterTheFirstPasses (0.48s)
./cmd/mesh-controller --- PASS: TestARestMachineThatFailsIsPutBackAloneAndTheOthersAreJudgedOn (0.25s)
./cmd/mesh-controller --- PASS: TestAWalkTakesOverTheReadingsOfAGateJudgingTheSameBuildThere (0.18s)
./cmd/mesh-controller --- PASS: TestAFirstSendMadeAndNotKeptIsNotSentAgain (0.38s)
./cmd/mesh-controller --- PASS: TestAReleaseSendKeptAndMadeIsNotMadeAgain (0.29s)
./cmd/mesh-controller --- PASS: TestAFirstMachineThatFailsStillStopsTheWalk (0.18s)
./cmd/mesh-controller --- PASS: TestTheControlNodeIsSentLastInAStep (0.20s)
./cmd/mesh-controller --- PASS: TestARestMachineSilentPastItsBoundIsLeftAndSaid (0.20s)
./cmd/mesh-controller --- PASS: TestANoMoveTierWaitsForNoNewReport (0.24s)
./cmd/mesh-controller --- PASS: TestOneProviderDownAndThreeConsumersFailingAreOneCondition (0.18s)
./cmd/mesh-controller --- PASS: TestAConsumerFailingBesideAHealthyProviderIsItsOwn (0.17s)
./cmd/mesh-controller --- PASS: TestTheProvisionerClientsAccountIsIssuedForItsServiceAndNeverInvented (0.19s)
./cmd/mesh-controller --- PASS: TestAcceptOfAnOwnSecretTakesThePathOfItsModulesForm (0.24s)
./cmd/mesh-controller --- PASS: TestAcceptForAProviderTakesThePathOfTheProvidersModule (0.28s)
./cmd/mesh-controller --- PASS: TestAcceptForAMovedTrustedModuleAnnouncesBeforeTheVaultIsAsked (0.25s)
./cmd/mesh-controller --- PASS: TestAcceptForAMovedModuleRecordsAHandActAndNeverTheValue (0.23s)
./cmd/mesh-controller --- PASS: TestAcceptOfAnOutsideOfferTakesThePathOfTheProvidersModule (0.27s)
./cmd/mesh-controller --- PASS: TestAnAskAtTheDeskTakesThePathOfItsModulesForm (0.28s)
./cmd/mesh-controller --- PASS: TestAnIssuedValueTakesThePathOfItsProvidersModule (0.29s)
./cmd/mesh-controller --- PASS: TestARotationTakesThePathOfItsModulesForm (0.24s)
./cmd/mesh-controller --- PASS: TestADeclarationIsTheSameWhileTheWordsAreStillInTheLayers (2.13s)
./cmd/mesh-controller --- PASS: TestADeclarationIsTheSameAfterTheMoveOfPlacement (4.02s)
./cmd/mesh-controller --- PASS: TestTheSendSealsNoSecretOfAModuleHandedThere (0.26s)
./cmd/mesh-controller --- PASS: TestAModulesSecretsAreTheVaultsOnceItIsMarkedMoved (0.17s)
./cmd/mesh-controller --- PASS: TestEveryMachineIsToldTheSameAfterTheMoveOfConfig (25.56s)
./cmd/mesh-controller --- PASS: TestTheMoveOfConfigRefusesWhatWouldChangeAMachine (8.32s)
./cmd/mesh-controller --- PASS: TestTheSettingsVerbForwardsToConfigOnceTheValuesMoved (11.59s)
./cmd/mesh-controller --- PASS: TestTheSendCarriesTheVaultsBoxForACoreCredentialAndKeepsIt (0.38s)
./cmd/mesh-controller --- PASS: TestASilentVaultHoldsTheKeptBoxAndSaysSo (0.35s)
./cmd/mesh-controller --- PASS: TestACoreModuleFirstPlacedWhileTheVaultIsSilentIsSealedByTheController (0.29s)
./cmd/mesh-controller --- PASS: TestAnEngineBelowTheContractIsSentTheControllersSealAsBefore (0.28s)
./cmd/mesh-controller --- PASS: TestModuleIssueHandsACoveredAccountToTheVaultAndOnlyThat (0.26s)
./cmd/mesh-controller --- PASS: TestModuleIssueFailsWhenTheVaultDoesNotTakeACoveredAccount (0.22s)
./cmd/mesh-controller --- PASS: TestModuleIssueBeforeTheVaultIsInstalledKeepsTheValueAndHandsNothing (0.23s)
./cmd/mesh-controller --- PASS: TestARecordedModulesBundleOnlyMoveRollsOutInItsWalk (0.36s)
./cmd/mesh-controller --- PASS: TestARecordedModulesMoveThatRecreatesAContainerWaits (0.61s)
./cmd/mesh-controller --- PASS: TestARecordedModulesMoveThatTouchesDataOrAProviderWaits (0.64s)
./cmd/mesh-controller --- PASS: TestAPersonsRecordAndTheBusHoldEveryMove (0.41s)
./cmd/mesh-controller --- PASS: TestARecordedMoveThatCannotBeJudgedWaits (0.33s)
./cmd/mesh-controller --- PASS: TestReplay867 (3.39s)
./cmd/mesh-controller --- PASS: TestReplay867Recheck (3.81s)
./cmd/mesh-controller --- PASS: TestTheRecheckVerbAsksMeshDeliveryOnABusOfItsOwn (0.34s)
./cmd/mesh-controller --- PASS: TestAssigningTheClientIssuesItsAccount (0.18s)
./cmd/mesh-controller --- PASS: TestAnUnrelatedBatchWalksBesideAnOpenWalk (0.25s)
./cmd/mesh-controller --- PASS: TestARelatedBatchWaitsBehindTheOpenWalk (0.19s)
./cmd/mesh-controller --- PASS: TestAnOwnPathBatchNeverWalksBeside (0.17s)
./cmd/mesh-controller --- FAIL: TestMergesHeardWhileAnotherHolderHasThePlansAreRecordedAndCarried (15.28s)
./cmd/mesh-controller --- PASS: TestABatchWindowClosesByTheExpiryOfItsKey (1.31s)
./cmd/mesh-controller --- PASS: TestEveryMoveAMergeAndTheCutMakeOfAPlanIsSaid (0.20s)
./cmd/mesh-controller --- PASS: TestARolloutAdvancesOnEventsAndAReplacedControllerResumesIt (3.90s)
./cmd/mesh-controller --- PASS: TestAWalkLetGoByTheDeliverVerbIsAskedWithNoOtherEvent (0.82s)
./cmd/mesh-controller --- PASS: TestTwoMergesWithinAMinuteLeaveEachOpenPullRequestOneQueuedCheck (0.57s)
./cmd/mesh-controller --- PASS: TestADeliveryGroupMovingAModuleMachinesRunPassesTheGate (4.70s)
./cmd/mesh-controller --- PASS: TestAModuleMovesOnTheOperatorsApproveOfTheMergeThatMovedIt (1.09s)
./cmd/mesh-controller --- PASS: TestAModuleBuiltFromANewRepositoryIsRegisteredOnlyOnTheOperatorsApproveOnTheBus (0.65s)
./cmd/mesh-controller --- PASS: TestAMergeWhosePlanCannotBeSavedIsHeldAndRecordedWhenHandedOverAgain (0.17s)
./cmd/mesh-controller --- PASS: TestOneReadOfAnAssignmentNamesItsCommitBuildAndRolloutAndOneReadOfTheRolloutListsItsAssignments (0.39s)
./cmd/mesh-controller --- PASS: TestASendOfWhatAMachineRunsAlreadyChangesNoLinkOfItsAssignment (0.27s)
./cmd/mesh-controller --- PASS: TestAnAssignmentWaitingForItsBuildIsOneKeyOfTheAssignmentsBucket (0.23s)
./cmd/mesh-controller --- PASS: TestNoTableOfTheControllersStoreHoldsBuildsRolloutsOrAssignments (0.22s)
./cmd/mesh-controller FAIL: go test exited 1
./internal/inventory --- PASS: TestTheLastSendSaysWhatTheMachineAnswered (0.08s)
./internal/inventory --- PASS: TestAReportIsTheLastSendsAnswerOnlyWhenItIsAboutThatSend (0.09s)
./internal/inventory --- PASS: TestAnIssuedValueIsSealedToEveryHolderOnceAndNotAgain (0.15s)
./internal/inventory --- PASS: TestAnIssuedValueIsSealedAgainAfterAKeyChangeOrAnAcceptance (0.13s)
./internal/inventory --- PASS: TestAConditionsLooksAreKeptBesideTheBucket (0.09s)
./internal/inventory --- PASS: TestAPlanIdHoldingAQuoteIsReadAsAPlainId (0.06s)
./internal/inventory --- PASS: TestAWalksStartIsKeptAndARefusedSaveLeavesItUnsaid (0.08s)
./internal/inventory --- PASS: TestAWalksRestIsReadFromEachMachinesOwnSend (0.12s)
./internal/inventory --- PASS: TestAStoredBuildWithASilentMergeableFileIsStillReadAndComposed (0.06s)
./internal/inventory --- PASS: TestACredentialIssuedOutsideIsNeverMade (0.13s)
./internal/inventory --- PASS: TestOneAcceptForAProviderIsSealedToEveryConsumer (0.14s)
./internal/inventory --- PASS: TestASharedOwnSecretIssuedOutsideIsNeverMade (0.13s)
./internal/inventory --- PASS: TestAModuleInTheConfigFormIsMirroredWithItsWholeDeclaration (0.07s)
./internal/inventory --- PASS: TestAReportOfABusyContainerIsKeptAndReadBack (0.08s)
./internal/inventory --- PASS: TestANewerBuildsListReplacesTheKeptOneAndAnOlderOneHeardLaterDoesNot (0.07s)
./internal/inventory --- PASS: TestPlacementMovesOutOfTheSettingsLayers (0.47s)
./internal/inventory --- PASS: TestASettingRoutesPlacementBesideTheLayer (0.10s)
./internal/inventory --- PASS: TestTheProvisionerClientsMachineHasAnAccountOfItsOwn (0.09s)
./internal/inventory --- PASS: TestTheFourWordsAreKeptBesideTheLayer (0.09s)
./internal/inventory --- PASS: TestALayerStillHoldingTheWordsReadsThemAsPlacement (0.12s)
./internal/inventory --- PASS: TestTheMoveOfPlacementMovesWhatTheLayersStillHold (0.09s)
./internal/inventory --- PASS: TestTheMoveReadsEveryRowSealedToAMachineAsItIs (0.09s)
./internal/inventory --- PASS: TestASendKeepsThePlansItHandedAndTheMirrorCarriesThem (0.07s)
./internal/inventory --- PASS: TestTheLayersAreReadUntilTheMoveOfConfigHasRun (0.08s)
./internal/inventory --- PASS: TestAModuleReadsMeshConfigOnlyWhereItsValuesAre (0.08s)
./internal/inventory --- PASS: TestTheEndOfTheMoveRefusesALayerChangedSinceItWasRead (0.10s)
./internal/inventory --- PASS: TestACoreCredentialsVaultBoxIsKeptPerMachineAndReplaced (0.11s)
./internal/inventory --- PASS: TestWhatRunsIsTheRegisteredBuildNotANewerOnePutBack (0.07s)
./internal/inventory --- PASS: TestBuildsOnTheBusAreReadBackByEveryReader (0.07s)
./internal/inventory --- PASS: TestARequestIsTheBuildInStateAskedAndItsOutcomeTakesItsPlace (0.08s)
./internal/inventory --- PASS: TestAnAssignmentIsAKeyOfTheBucketAndAnUnassignmentEndsIt (0.12s)
./internal/inventory --- PASS: TestThePlansAreKeptInTheAssignmentsValuesAndNothingElseOfThemMoves (0.08s)
./internal/inventory --- FAIL: TestAPendingAssignmentIsAKeyOfTheAssignmentsBucket (0.07s)
./internal/inventory --- PASS: TestARecordedPendingIsSkippedByAssignedAndTheJoins (0.07s)
./internal/inventory --- PASS: TestTwoClaimsOfOnePendingMakeOneAndTheOtherSeesFalse (0.08s)
./internal/inventory --- PASS: TestAssignOverAPendingKeepsItsRecordAsApplied (0.08s)
./internal/inventory --- PASS: TestAPendingIsMarkedOnceAndGoesWithItsMachine (0.09s)
./internal/inventory --- PASS: TestAReplacedWaitNeverLeavesTheOperatorWithoutItsCondition (0.09s)
./internal/inventory --- PASS: TestSentBuildsAnswersFromTheAssignmentsKeysOfTheNode (0.08s)
./internal/inventory --- PASS: TestASendReplacesTheWholeMapOfTheNodeAndAHandSendMakesItUnknown (0.09s)
./internal/inventory --- PASS: TestAFailedWriteOfTheLinksFailsTheRecordOfTheSend (0.10s)
./internal/inventory --- PASS: TestMigration0105RefusesAStoreWhoseRowsWereNotMovedAndDropsTheTablesOfAMovedOne (0.38s)
./internal/inventory --- PASS: TestMigration0105PassesAStoreThatNeverHeldARow (0.09s)
./internal/inventory --- PASS: TestTheColumnOfASentMachineIsCopiedOntoItsKeysAndEmptied (0.08s)
./internal/inventory --- PASS: TestASendEmptiesTheColumnSoALaterCopyLeavesAClearedKeyBare (0.09s)
./internal/inventory FAIL: go test exited 1
./internal/recordmirror --- PASS: TestNatsAnAssignmentAndARegistrationEachChangeOneKeyAndRaiseOneEvent (2.12s)
./internal/recordmirror --- PASS: TestNatsTheListOfPredefinedKeysKeptChangesTheMirrorsOneKey (1.48s)
4 store test(s) listed in testdata/store-tests did not run and pass against the store
--- what failed, picked from the whole of its output (the whole is in the build's log)
--- FAIL: TestTheGrantsStepSendsTheUserListAndNothingElse (0.53s)
grants_step_store_test.go:105: with nothing changed, the step reads "its send would change more than the bus's user list: mesh-wireguard newly assigned", <nil>
FAIL github.com/novox/mesh-controller/cmd/mesh-controller 69s (shard 3 of 8: 140 tests)
--- FAIL: TestADeliveryGroupsHeadsAreComposedTogether (1.79s)
merge_gate_integration_test.go:176: a requirement nothing provides passed alone:
merge gate: ERROR — the mesh as it is could not be raised, so the change cannot be judged against it (2 of 2 machines compose on the mesh and not in the gate); the first: a machine (kecitn) composes on the mesh and not as the gate raised it from the snapshot: the private network cannot be computed: whether fjtoel answers "mesh-addressing" cannot be read: this kind of record lives on the bus, and this process has not opened the bus: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
judged by controller development build against the facts of 2026-10-18T11:54:44Z
FAIL github.com/novox/mesh-controller/cmd/mesh-controller 83s (shard 4 of 8: 140 tests)
--- FAIL: TestIssue285AModuleOnTheBusComposesInTheGate (1.96s)
merge_gate_integration_test.go:276: the mesh as it is does not pass:
merge gate: ERROR — the mesh as it is could not be raised, so the change cannot be judged against it (2 of 2 machines compose on the mesh and not in the gate); the first: a machine (kecitn) composes on the mesh and not as the gate raised it from the snapshot: the private network cannot be computed: whether fjtoel answers "mesh-addressing" cannot be read: this kind of record lives on the bus, and this process has not opened the bus: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
judged by controller development build against the facts of 2026-10-18T11:54:10Z
--- FAIL: TestMergesHeardWhileAnotherHolderHasThePlansAreRecordedAndCarried (15.42s)
merge_on_the_bus_test.go:105: the first rollout opening did not happen within 15s
FAIL github.com/novox/mesh-controller/cmd/mesh-controller 65s (shard 5 of 8: 140 tests)
--- FAIL: TestALastSendIsReadFromTheSendAndTheReport (0.40s)
awaiting_push_integration_test.go:162: a module the machine was sent long ago is not expected to answer
--- FAIL: TestIssue285AMachineTheGateCannotRaiseIsAnErrorNeverAPass (1.93s)
merge_gate_integration_test.go:305: the error does not name what could not be raised: [a machine (kecitn) composes on the mesh and not as the gate raised it from the snapshot: the private network cannot be computed: whether fjtoel answers "mesh-addressing" cannot be read: this kind of record lives on the bus, and this process has not opened the bus: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus the hub (fjtoel) composes on the mesh and not as the gate raised it from the snapshot: the private network cannot be computed: whether fjtoel answers "mesh-addressing" cannot be read: this kind of record lives on the bus, and this process has not opened the bus: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus]
--- FAIL: TestABatchWindowClosesByTheExpiryOfItsKey (10.45s)
merge_on_the_bus_test.go:159: the merge waiting in a batch did not happen within 10s
FAIL github.com/novox/mesh-controller/cmd/mesh-controller 56s (shard 6 of 8: 140 tests)
--- FAIL: TestNatsUnassigningIrreplaceableDataRetiresItAndAnEmptyReplacementIsUrgent (0.61s)
data_integration_test.go:117: what the holder measured was not kept: {Machine:laptop Module:house Item:config Class:irreplaceable Path: Owned:true Protection:backup FirstSeen:2026-10-18 11:55:44.112549 +0000 UTC DeclaredAt:2026-10-18 11:55:44.112549 +0000 UTC MeasureError: Precision: Redundancy:<nil> Size:<nil> LastWrite:<nil> MeasuredAt:<nil> LastBackup:<nil> RetiredAt:<nil> RetiredWhy: DeletedAt:<nil> DeletedBy: DeletedWhy:}, <nil>
--- FAIL: TestIssue236AManifestTheNodeEngineRefusesFailsThePullRequest (1.54s)
merge_gate_integration_test.go:107: a service the node-engine refuses passed the gate:
merge gate: ERROR — the mesh as it is could not be raised, so the change cannot be judged against it (2 of 2 machines compose on the mesh and not in the gate); the first: a machine (kecitn) composes on the mesh and not as the gate raised it from the snapshot: the private network cannot be computed: whether fjtoel answers "mesh-addressing" cannot be read: this kind of record lives on the bus, and this process has not opened the bus: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
judged by controller development build against the facts of 2026-10-18T11:55:49Z
FAIL github.com/novox/mesh-controller/cmd/mesh-controller 131s (shard 8 of 8: 139 tests)
--- FAIL: TestAPendingAssignmentIsAKeyOfTheAssignmentsBucket (0.18s)
chain_pending_test.go:61: the earlier wait is in the key's history: 3 values
FAIL github.com/novox/mesh-controller/internal/inventory 12s (shard 2 of 4: 89 tests)
**Merge check** at `cbc6bac8`
Judged: head `cbc6bac8c070` merged into trunk `da6d038e07c0`; read beside it: mesh-catalog `7f77ce663a9e`, mesh-controller-main `da6d038e07c0`, mesh-host `6469e8238443`, mesh-tools `7412c5b6c9c5`
- `mesh/merge-gate`: **ERROR** — the mesh as it is could not be raised, so the change cannot be judged against it (4 of 4 machines compose on the mesh and not in the gate); the first: a machine (f35) composes on the mesh and not as the gate raised it from the snapshot: the private network cannot be computed: whether f35 answers "mesh-addressing" cannot be read: this kind of record lives on the bus, and this process has not opened the bus: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus (modules: build-agent, mesh-controller)
- `mesh/repo-check`: **FAIL** — its merge-check.sh failed: --- FAIL: TestTheGrantsStepSendsTheUserListAndNothingElse (0.53s); and TestADeliveryGroupsHeadsAreComposedTogether, TestIssue285AModuleOnTheBusComposesInTheGate, TestMergesHeardWhileAnotherHolderHasThePlansAreRecordedAndCarried, TestALastSendIsReadFromTheSendAndTheReport, TestIssue285AMachineTheGateCannotRaiseIsAnErrorNeverAPass and 4 more
**Delivery plan** — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
- tier 0: mesh-controller
- tier 1: build-agent
- ace: receives build-agent
- g14: receives build-agent
- novox: receives mesh-controller, build-agent
- shanks: receives build-agent
- build-agent keeps data (ADR 0233): what it holds is backed up before it moves
- grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before build-agent is judged on its first machine
- read by no module's build: cmd/mesh-controller/chain_integration_test.go, cmd/mesh-controller/chain_no_table_integration_test.go, cmd/mesh-controller/pending_integration_test.go, cmd/mesh-controller/pending_test.go, cmd/mesh-controller/plan_moved_every_writer_test.go, cmd/mesh-controller/record_mirrors_switch_test.go, cmd/mesh-controller/sent_required_by_integration_test.go, internal/chain/pending_test.go, internal/inventory/chain_assignments_key_test.go, internal/inventory/chain_builds_layout_test.go, internal/inventory/chain_drop_test.go, internal/inventory/chain_move_test.go, internal/inventory/chain_moved_test.go, internal/inventory/chain_pending_test.go, internal/inventory/chain_rollouts_test.go, internal/inventory/chain_sent_copy_test.go, internal/inventory/chain_sent_test.go, internal/inventory/chain_source_test.go, internal/inventory/chain_store_test.go, internal/inventory/mirrored_test.go, internal/inventory/pin_completed_test.go, internal/inventory/sent_builds_test.go, internal/inventory/sent_plans_test.go, internal/recordmirror/mirror_store_test.go, testdata/store-tests
Run by the build seat on ace as `build-1792324330116343529` (`builds --log build-1792324330116343529`).
```
plan-gate: the send to anchor in tier 0 failed its gate: not healthy within -1s of its apply: anchor has not reported on what it was sent; app was left as it was — anchor already ran app c2, or a build identical to it, before the send, so nothing of it moved and nothing is put back
plan-gate: the send to anchor in tier 0 failed its gate: not healthy within -1s of its apply: anchor has not reported on what it was sent; app was left as it was — anchor already ran app c2, or a build identical to it, before the send, so nothing of it moved and nothing is put back; none reported left as it was
tier 0: the vault now holds accept/token (generation 1), accepted: sealed at this terminal to the vault's key for this call, opened in the vault alone and never remade by it; its machine takes it from the vault
this act could NOT be recorded in the hand-act log, and is done anyway: the hand-act log mesh-controller_hand-acts is not on the bus — the controller asserts it at its start, so one older than this has not: nats: bucket not found
the vault now holds accept/token (generation 1), accepted: sealed at this terminal to the vault's key for this call, opened in the vault alone and never remade by it; its machine takes it from the vault
this change could NOT be announced on the operator's channels: no channel took it
this act could NOT be recorded in the hand-act log, and is done anyway: the hand-act log mesh-controller_hand-acts is not on the bus — the controller asserts it at its start, so one older than this has not: nats: bucket not found
tier 0: rebuild asked as build-1792324564866430518, joining plan-308-rebuild at tier 0 (novox/a at c0ffee): the plan takes this build as a's outcome; the plan had failed and builds again from this tier
FAIL
FAIL github.com/novox/mesh-controller/cmd/mesh-controller 131s (shard 8 of 8: 139 tests)
ok github.com/novox/mesh-controller/internal/inventory 16s (shard 1 of 4: 89 tests)
builds: the pointer alpha.newest was missing or wrong (a lookup of alpha.commit.c4) and is repaired from the records of alpha
builds: the pointer alpha.worked was missing or wrong (a lookup of alpha.commit.c4) and is repaired from the records of alpha
builds: the pointer alpha.held was missing or wrong (a lookup of alpha.commit.c4) and is repaired from the records of alpha
builds: the pointer alpha.commit.c4 was missing or wrong (a lookup of alpha.commit.c4) and is repaired from the records of alpha
builds: the pointer alpha.source.v1-s4 was missing or wrong (a lookup of alpha.commit.c4) and is repaired from the records of alpha
builds: the pointer alpha.commit.c2 was missing or wrong (a lookup of alpha.commit.c2) and is repaired from the records of alpha
--- FAIL: TestAPendingAssignmentIsAKeyOfTheAssignmentsBucket (0.18s)
chain_pending_test.go:61: the earlier wait is in the key's history: 3 values
FAIL
FAIL github.com/novox/mesh-controller/internal/inventory 12s (shard 2 of 4: 89 tests)
ok github.com/novox/mesh-controller/internal/inventory 13s (shard 3 of 4: 88 tests)
ok github.com/novox/mesh-controller/internal/inventory 15s (shard 4 of 4: 88 tests)
ok github.com/novox/mesh-controller/internal/builder 15s (shard 1 of 4: 54 tests)
ok github.com/novox/mesh-controller/internal/builder 17s (shard 2 of 4: 53 tests)
ok github.com/novox/mesh-controller/internal/builder 25s (shard 3 of 4: 53 tests)
ok github.com/novox/mesh-controller/internal/builder 15s (shard 4 of 4: 53 tests)
ok github.com/novox/mesh-controller/internal/link 22s (shard 1 of 4: 50 tests)
ok github.com/novox/mesh-controller/internal/link 15s (shard 2 of 4: 50 tests)
ok github.com/novox/mesh-controller/internal/link 16s (shard 3 of 4: 49 tests)
ok github.com/novox/mesh-controller/internal/link 23s (shard 4 of 4: 49 tests)
integration level (the whole suite, tag integration): 3404 tests (6 skipped outside the shards), 159 s
nested module modules/build-agent:
ok build-agent 1.012s
nested module modules/route-proxy:
ok route-proxy/cmd/route-provider 1.012s
nested modules: 3 s
store tests, each run against the store:
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeWalksTheOthersAgain (0.33s)
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeEndsTheMergesThatContainIt (0.28s)
./cmd/mesh-controller --- PASS: TestAStopWalksTheOthersAgainInTheOpenBatch (0.23s)
./cmd/mesh-controller --- PASS: TestAStopNamesWhatStaysOnTheMachinesAndWhatStillCarriesIt (0.24s)
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeLeavesItOutOfABatch (0.20s)
./cmd/mesh-controller --- PASS: TestSavingPlansAndMovingMergesIsOneAct (0.19s)
./cmd/mesh-controller --- PASS: TestAPlanFollowedFromTheStoreAnswersWhenItMoves (1.98s)
./cmd/mesh-controller --- PASS: TestIssue969TheGateRaisesEachMachineAsItsEngineStatedItself (0.77s)
./cmd/mesh-controller --- PASS: TestNodeShowAndStatusReadTheLastSendFromTheStore (0.27s)
./cmd/mesh-controller --- PASS: TestTheConditionsVerbReadsTheLooksTheBucketNoLongerHolds (0.15s)
./cmd/mesh-controller --- PASS: TestAWalkLetGoAndStoppedByVerbsIsSaidStartedAndEnded (0.23s)
./cmd/mesh-controller --- PASS: TestAWalkStoppedOrClosedByAPersonIsSaidEndedStopped (0.26s)
./cmd/mesh-controller --- PASS: TestAWalkRetriedByAPersonIsSaidStartedAgain (0.19s)
./cmd/mesh-controller --- PASS: TestABacklogReleasedByAPersonIsSaidStarted (0.20s)
./cmd/mesh-controller --- PASS: TestAWalkEndedByCancelOrClearIsSaidEnded (0.26s)
./cmd/mesh-controller --- PASS: TestAWalkRestartedByARebuildIsSaidStarted (0.20s)
./cmd/mesh-controller --- PASS: TestAWalkStoppedByHandAndRetriedEndsFailedWhenItFailsAgain (0.23s)
./cmd/mesh-controller --- PASS: TestReplay237 (0.20s)
./cmd/mesh-controller --- PASS: TestAnUnassignThatLeavesItsNodeUnresolvedSaysSoOnceInItsAnswer (0.23s)
./cmd/mesh-controller --- PASS: TestAnUnassignThatLeavesItsNodeResolvedSaysNothingOfIt (0.24s)
./cmd/mesh-controller --- PASS: TestAnAssignThatLeavesItsNodeUnresolvedSaysOnlyThePlansRefusal (0.23s)
./cmd/mesh-controller --- PASS: TestADirectoryOwnersKeyIsRefusedThroughAVerb (0.24s)
./cmd/mesh-controller --- PASS: TestTheSendMakesNoValueForAnOutsideSecretNobodyGave (0.35s)
./cmd/mesh-controller --- PASS: TestAQuestionComposesWithoutAnOutsideSecretNobodyGave (0.30s)
./cmd/mesh-controller --- PASS: TestReplay201 (0.17s)
./cmd/mesh-controller --- PASS: TestARollbackWhoseSendWasRefusedIsCompletedByTheNextSend (0.18s)
./cmd/mesh-controller --- PASS: TestAGateJudgesTheOtherMovesBesideAKeptCore (0.20s)
./cmd/mesh-controller --- PASS: TestReplay401 (0.29s)
./cmd/mesh-controller --- PASS: TestReplay201ThePlansSend (0.24s)
./cmd/mesh-controller --- PASS: TestPlanAndNodeListAnOptionalRequirementLeftUnbound (0.31s)
./cmd/mesh-controller --- PASS: TestReplay340 (0.26s)
./cmd/mesh-controller --- PASS: TestOnlyATrustedFilesNamedKeyIsRefusedThroughAVerb (0.20s)
./cmd/mesh-controller --- PASS: TestReplay349 (0.20s)
./cmd/mesh-controller --- PASS: TestReplay348AFaultFromBeforeTheSendFailsNoGate (0.19s)
./cmd/mesh-controller --- PASS: TestReplay239AModuleNameIsNotTakenOverByAnotherRepository (0.14s)
./cmd/mesh-controller --- PASS: TestAWalkThatMovedNothingSaysWhichModulesMatchedWhatRuns (0.20s)
./cmd/mesh-controller --- PASS: TestAWalkWhoseEveryBuildCameOutTheSameIsDone (0.16s)
./cmd/mesh-controller --- PASS: TestReplay614ANewSDKPlansTheToolchainAndThenItsBundles (0.08s)
./cmd/mesh-controller --- PASS: TestOneAcceptForAProviderIsPlacedForEveryConsumer (0.56s)
./cmd/mesh-controller --- PASS: TestReplay164 (0.29s)
./cmd/mesh-controller --- PASS: TestAnApprovedLayerOpensTheWalkThatSendsIt (0.19s)
./cmd/mesh-controller --- PASS: TestASettingsWalkSendsOneMachineAtATimeEachJudged (0.18s)
./cmd/mesh-controller --- PASS: TestAFailedSettingsWalkStopsAndHoldsNothingBack (0.19s)
./cmd/mesh-controller --- PASS: TestASettingsWalkSendsTheLayerAloneEveryBuildKept (0.17s)
./cmd/mesh-controller --- PASS: TestASettingsWalkStopsBeforeADataMoveAndPassesOverAMachineAway (0.49s)
./cmd/mesh-controller --- PASS: TestACrossingSendSupersedesASettingsGate (0.16s)
./cmd/mesh-controller --- PASS: TestASettingsWalkFailsOnARefusalThatCannotClear (0.15s)
./cmd/mesh-controller --- PASS: TestAProviderElsewhereServesItsOwnComposedName (0.36s)
./cmd/mesh-controller --- PASS: TestAReusedCheckBuildIsRegisteredByItsDigestAndGatedAsABuiltOne (0.28s)
./cmd/mesh-controller --- PASS: TestTheMergeGateJudgesEachManifestAgainstTheListOfTheTree (4.30s)
./cmd/mesh-controller --- PASS: TestRegistrationPublishesTheNewestTrunkListAndJudgesEveryModuleAgainstIt (0.20s)
./cmd/mesh-controller --- PASS: TestADeclarationIsTheSameAfterPlacementMoves (0.36s)
./cmd/mesh-controller --- PASS: TestAReleaseSendsTheRestAtOnceAfterTheFirstPasses (0.48s)
./cmd/mesh-controller --- PASS: TestARestMachineThatFailsIsPutBackAloneAndTheOthersAreJudgedOn (0.25s)
./cmd/mesh-controller --- PASS: TestAWalkTakesOverTheReadingsOfAGateJudgingTheSameBuildThere (0.18s)
./cmd/mesh-controller --- PASS: TestAFirstSendMadeAndNotKeptIsNotSentAgain (0.38s)
./cmd/mesh-controller --- PASS: TestAReleaseSendKeptAndMadeIsNotMadeAgain (0.29s)
./cmd/mesh-controller --- PASS: TestAFirstMachineThatFailsStillStopsTheWalk (0.18s)
./cmd/mesh-controller --- PASS: TestTheControlNodeIsSentLastInAStep (0.20s)
./cmd/mesh-controller --- PASS: TestARestMachineSilentPastItsBoundIsLeftAndSaid (0.20s)
./cmd/mesh-controller --- PASS: TestANoMoveTierWaitsForNoNewReport (0.24s)
./cmd/mesh-controller --- PASS: TestOneProviderDownAndThreeConsumersFailingAreOneCondition (0.18s)
./cmd/mesh-controller --- PASS: TestAConsumerFailingBesideAHealthyProviderIsItsOwn (0.17s)
./cmd/mesh-controller --- PASS: TestTheProvisionerClientsAccountIsIssuedForItsServiceAndNeverInvented (0.19s)
./cmd/mesh-controller --- PASS: TestAcceptOfAnOwnSecretTakesThePathOfItsModulesForm (0.24s)
./cmd/mesh-controller --- PASS: TestAcceptForAProviderTakesThePathOfTheProvidersModule (0.28s)
./cmd/mesh-controller --- PASS: TestAcceptForAMovedTrustedModuleAnnouncesBeforeTheVaultIsAsked (0.25s)
./cmd/mesh-controller --- PASS: TestAcceptForAMovedModuleRecordsAHandActAndNeverTheValue (0.23s)
./cmd/mesh-controller --- PASS: TestAcceptOfAnOutsideOfferTakesThePathOfTheProvidersModule (0.27s)
./cmd/mesh-controller --- PASS: TestAnAskAtTheDeskTakesThePathOfItsModulesForm (0.28s)
./cmd/mesh-controller --- PASS: TestAnIssuedValueTakesThePathOfItsProvidersModule (0.29s)
./cmd/mesh-controller --- PASS: TestARotationTakesThePathOfItsModulesForm (0.24s)
./cmd/mesh-controller --- PASS: TestADeclarationIsTheSameWhileTheWordsAreStillInTheLayers (2.13s)
./cmd/mesh-controller --- PASS: TestADeclarationIsTheSameAfterTheMoveOfPlacement (4.02s)
./cmd/mesh-controller --- PASS: TestTheSendSealsNoSecretOfAModuleHandedThere (0.26s)
./cmd/mesh-controller --- PASS: TestAModulesSecretsAreTheVaultsOnceItIsMarkedMoved (0.17s)
./cmd/mesh-controller --- PASS: TestEveryMachineIsToldTheSameAfterTheMoveOfConfig (25.56s)
./cmd/mesh-controller --- PASS: TestTheMoveOfConfigRefusesWhatWouldChangeAMachine (8.32s)
./cmd/mesh-controller --- PASS: TestTheSettingsVerbForwardsToConfigOnceTheValuesMoved (11.59s)
./cmd/mesh-controller --- PASS: TestTheSendCarriesTheVaultsBoxForACoreCredentialAndKeepsIt (0.38s)
./cmd/mesh-controller --- PASS: TestASilentVaultHoldsTheKeptBoxAndSaysSo (0.35s)
./cmd/mesh-controller --- PASS: TestACoreModuleFirstPlacedWhileTheVaultIsSilentIsSealedByTheController (0.29s)
./cmd/mesh-controller --- PASS: TestAnEngineBelowTheContractIsSentTheControllersSealAsBefore (0.28s)
./cmd/mesh-controller --- PASS: TestModuleIssueHandsACoveredAccountToTheVaultAndOnlyThat (0.26s)
./cmd/mesh-controller --- PASS: TestModuleIssueFailsWhenTheVaultDoesNotTakeACoveredAccount (0.22s)
./cmd/mesh-controller --- PASS: TestModuleIssueBeforeTheVaultIsInstalledKeepsTheValueAndHandsNothing (0.23s)
./cmd/mesh-controller --- PASS: TestARecordedModulesBundleOnlyMoveRollsOutInItsWalk (0.36s)
./cmd/mesh-controller --- PASS: TestARecordedModulesMoveThatRecreatesAContainerWaits (0.61s)
./cmd/mesh-controller --- PASS: TestARecordedModulesMoveThatTouchesDataOrAProviderWaits (0.64s)
./cmd/mesh-controller --- PASS: TestAPersonsRecordAndTheBusHoldEveryMove (0.41s)
./cmd/mesh-controller --- PASS: TestARecordedMoveThatCannotBeJudgedWaits (0.33s)
./cmd/mesh-controller --- PASS: TestReplay867 (3.39s)
./cmd/mesh-controller --- PASS: TestReplay867Recheck (3.81s)
./cmd/mesh-controller --- PASS: TestTheRecheckVerbAsksMeshDeliveryOnABusOfItsOwn (0.34s)
./cmd/mesh-controller --- PASS: TestAssigningTheClientIssuesItsAccount (0.18s)
./cmd/mesh-controller --- PASS: TestAnUnrelatedBatchWalksBesideAnOpenWalk (0.25s)
./cmd/mesh-controller --- PASS: TestARelatedBatchWaitsBehindTheOpenWalk (0.19s)
./cmd/mesh-controller --- PASS: TestAnOwnPathBatchNeverWalksBeside (0.17s)
./cmd/mesh-controller --- FAIL: TestMergesHeardWhileAnotherHolderHasThePlansAreRecordedAndCarried (15.28s)
./cmd/mesh-controller --- PASS: TestABatchWindowClosesByTheExpiryOfItsKey (1.31s)
./cmd/mesh-controller --- PASS: TestEveryMoveAMergeAndTheCutMakeOfAPlanIsSaid (0.20s)
./cmd/mesh-controller --- PASS: TestARolloutAdvancesOnEventsAndAReplacedControllerResumesIt (3.90s)
./cmd/mesh-controller --- PASS: TestAWalkLetGoByTheDeliverVerbIsAskedWithNoOtherEvent (0.82s)
./cmd/mesh-controller --- PASS: TestTwoMergesWithinAMinuteLeaveEachOpenPullRequestOneQueuedCheck (0.57s)
./cmd/mesh-controller --- PASS: TestADeliveryGroupMovingAModuleMachinesRunPassesTheGate (4.70s)
./cmd/mesh-controller --- PASS: TestAModuleMovesOnTheOperatorsApproveOfTheMergeThatMovedIt (1.09s)
./cmd/mesh-controller --- PASS: TestAModuleBuiltFromANewRepositoryIsRegisteredOnlyOnTheOperatorsApproveOnTheBus (0.65s)
./cmd/mesh-controller --- PASS: TestAMergeWhosePlanCannotBeSavedIsHeldAndRecordedWhenHandedOverAgain (0.17s)
./cmd/mesh-controller --- PASS: TestOneReadOfAnAssignmentNamesItsCommitBuildAndRolloutAndOneReadOfTheRolloutListsItsAssignments (0.39s)
./cmd/mesh-controller --- PASS: TestASendOfWhatAMachineRunsAlreadyChangesNoLinkOfItsAssignment (0.27s)
./cmd/mesh-controller --- PASS: TestAnAssignmentWaitingForItsBuildIsOneKeyOfTheAssignmentsBucket (0.23s)
./cmd/mesh-controller --- PASS: TestNoTableOfTheControllersStoreHoldsBuildsRolloutsOrAssignments (0.22s)
./cmd/mesh-controller FAIL: go test exited 1
./internal/inventory --- PASS: TestTheLastSendSaysWhatTheMachineAnswered (0.08s)
./internal/inventory --- PASS: TestAReportIsTheLastSendsAnswerOnlyWhenItIsAboutThatSend (0.09s)
./internal/inventory --- PASS: TestAnIssuedValueIsSealedToEveryHolderOnceAndNotAgain (0.15s)
./internal/inventory --- PASS: TestAnIssuedValueIsSealedAgainAfterAKeyChangeOrAnAcceptance (0.13s)
./internal/inventory --- PASS: TestAConditionsLooksAreKeptBesideTheBucket (0.09s)
./internal/inventory --- PASS: TestAPlanIdHoldingAQuoteIsReadAsAPlainId (0.06s)
./internal/inventory --- PASS: TestAWalksStartIsKeptAndARefusedSaveLeavesItUnsaid (0.08s)
./internal/inventory --- PASS: TestAWalksRestIsReadFromEachMachinesOwnSend (0.12s)
./internal/inventory --- PASS: TestAStoredBuildWithASilentMergeableFileIsStillReadAndComposed (0.06s)
./internal/inventory --- PASS: TestACredentialIssuedOutsideIsNeverMade (0.13s)
./internal/inventory --- PASS: TestOneAcceptForAProviderIsSealedToEveryConsumer (0.14s)
./internal/inventory --- PASS: TestASharedOwnSecretIssuedOutsideIsNeverMade (0.13s)
./internal/inventory --- PASS: TestAModuleInTheConfigFormIsMirroredWithItsWholeDeclaration (0.07s)
./internal/inventory --- PASS: TestAReportOfABusyContainerIsKeptAndReadBack (0.08s)
./internal/inventory --- PASS: TestANewerBuildsListReplacesTheKeptOneAndAnOlderOneHeardLaterDoesNot (0.07s)
./internal/inventory --- PASS: TestPlacementMovesOutOfTheSettingsLayers (0.47s)
./internal/inventory --- PASS: TestASettingRoutesPlacementBesideTheLayer (0.10s)
./internal/inventory --- PASS: TestTheProvisionerClientsMachineHasAnAccountOfItsOwn (0.09s)
./internal/inventory --- PASS: TestTheFourWordsAreKeptBesideTheLayer (0.09s)
./internal/inventory --- PASS: TestALayerStillHoldingTheWordsReadsThemAsPlacement (0.12s)
./internal/inventory --- PASS: TestTheMoveOfPlacementMovesWhatTheLayersStillHold (0.09s)
./internal/inventory --- PASS: TestTheMoveReadsEveryRowSealedToAMachineAsItIs (0.09s)
./internal/inventory --- PASS: TestASendKeepsThePlansItHandedAndTheMirrorCarriesThem (0.07s)
./internal/inventory --- PASS: TestTheLayersAreReadUntilTheMoveOfConfigHasRun (0.08s)
./internal/inventory --- PASS: TestAModuleReadsMeshConfigOnlyWhereItsValuesAre (0.08s)
./internal/inventory --- PASS: TestTheEndOfTheMoveRefusesALayerChangedSinceItWasRead (0.10s)
./internal/inventory --- PASS: TestACoreCredentialsVaultBoxIsKeptPerMachineAndReplaced (0.11s)
./internal/inventory --- PASS: TestWhatRunsIsTheRegisteredBuildNotANewerOnePutBack (0.07s)
./internal/inventory --- PASS: TestBuildsOnTheBusAreReadBackByEveryReader (0.07s)
./internal/inventory --- PASS: TestARequestIsTheBuildInStateAskedAndItsOutcomeTakesItsPlace (0.08s)
./internal/inventory --- PASS: TestAnAssignmentIsAKeyOfTheBucketAndAnUnassignmentEndsIt (0.12s)
./internal/inventory --- PASS: TestThePlansAreKeptInTheAssignmentsValuesAndNothingElseOfThemMoves (0.08s)
./internal/inventory --- FAIL: TestAPendingAssignmentIsAKeyOfTheAssignmentsBucket (0.07s)
./internal/inventory --- PASS: TestARecordedPendingIsSkippedByAssignedAndTheJoins (0.07s)
./internal/inventory --- PASS: TestTwoClaimsOfOnePendingMakeOneAndTheOtherSeesFalse (0.08s)
./internal/inventory --- PASS: TestAssignOverAPendingKeepsItsRecordAsApplied (0.08s)
./internal/inventory --- PASS: TestAPendingIsMarkedOnceAndGoesWithItsMachine (0.09s)
./internal/inventory --- PASS: TestAReplacedWaitNeverLeavesTheOperatorWithoutItsCondition (0.09s)
./internal/inventory --- PASS: TestSentBuildsAnswersFromTheAssignmentsKeysOfTheNode (0.08s)
./internal/inventory --- PASS: TestASendReplacesTheWholeMapOfTheNodeAndAHandSendMakesItUnknown (0.09s)
./internal/inventory --- PASS: TestAFailedWriteOfTheLinksFailsTheRecordOfTheSend (0.10s)
./internal/inventory --- PASS: TestMigration0105RefusesAStoreWhoseRowsWereNotMovedAndDropsTheTablesOfAMovedOne (0.38s)
./internal/inventory --- PASS: TestMigration0105PassesAStoreThatNeverHeldARow (0.09s)
./internal/inventory --- PASS: TestTheColumnOfASentMachineIsCopiedOntoItsKeysAndEmptied (0.08s)
./internal/inventory --- PASS: TestASendEmptiesTheColumnSoALaterCopyLeavesAClearedKeyBare (0.09s)
./internal/inventory FAIL: go test exited 1
./internal/recordmirror --- PASS: TestNatsAnAssignmentAndARegistrationEachChangeOneKeyAndRaiseOneEvent (2.12s)
./internal/recordmirror --- PASS: TestNatsTheListOfPredefinedKeysKeptChangesTheMirrorsOneKey (1.48s)
4 store test(s) listed in testdata/store-tests did not run and pass against the store
--- what failed, picked from the whole of its output (the whole is in the build's log)
--- FAIL: TestTheGrantsStepSendsTheUserListAndNothingElse (0.53s)
grants_step_store_test.go:105: with nothing changed, the step reads "its send would change more than the bus's user list: mesh-wireguard newly assigned", <nil>
FAIL github.com/novox/mesh-controller/cmd/mesh-controller 69s (shard 3 of 8: 140 tests)
--- FAIL: TestADeliveryGroupsHeadsAreComposedTogether (1.79s)
merge_gate_integration_test.go:176: a requirement nothing provides passed alone:
merge gate: ERROR — the mesh as it is could not be raised, so the change cannot be judged against it (2 of 2 machines compose on the mesh and not in the gate); the first: a machine (kecitn) composes on the mesh and not as the gate raised it from the snapshot: the private network cannot be computed: whether fjtoel answers "mesh-addressing" cannot be read: this kind of record lives on the bus, and this process has not opened the bus: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
judged by controller development build against the facts of 2026-10-18T11:54:44Z
FAIL github.com/novox/mesh-controller/cmd/mesh-controller 83s (shard 4 of 8: 140 tests)
--- FAIL: TestIssue285AModuleOnTheBusComposesInTheGate (1.96s)
merge_gate_integration_test.go:276: the mesh as it is does not pass:
merge gate: ERROR — the mesh as it is could not be raised, so the change cannot be judged against it (2 of 2 machines compose on the mesh and not in the gate); the first: a machine (kecitn) composes on the mesh and not as the gate raised it from the snapshot: the private network cannot be computed: whether fjtoel answers "mesh-addressing" cannot be read: this kind of record lives on the bus, and this process has not opened the bus: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
judged by controller development build against the facts of 2026-10-18T11:54:10Z
--- FAIL: TestMergesHeardWhileAnotherHolderHasThePlansAreRecordedAndCarried (15.42s)
merge_on_the_bus_test.go:105: the first rollout opening did not happen within 15s
FAIL github.com/novox/mesh-controller/cmd/mesh-controller 65s (shard 5 of 8: 140 tests)
--- FAIL: TestALastSendIsReadFromTheSendAndTheReport (0.40s)
awaiting_push_integration_test.go:162: a module the machine was sent long ago is not expected to answer
--- FAIL: TestIssue285AMachineTheGateCannotRaiseIsAnErrorNeverAPass (1.93s)
merge_gate_integration_test.go:305: the error does not name what could not be raised: [a machine (kecitn) composes on the mesh and not as the gate raised it from the snapshot: the private network cannot be computed: whether fjtoel answers "mesh-addressing" cannot be read: this kind of record lives on the bus, and this process has not opened the bus: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus the hub (fjtoel) composes on the mesh and not as the gate raised it from the snapshot: the private network cannot be computed: whether fjtoel answers "mesh-addressing" cannot be read: this kind of record lives on the bus, and this process has not opened the bus: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus]
--- FAIL: TestABatchWindowClosesByTheExpiryOfItsKey (10.45s)
merge_on_the_bus_test.go:159: the merge waiting in a batch did not happen within 10s
FAIL github.com/novox/mesh-controller/cmd/mesh-controller 56s (shard 6 of 8: 140 tests)
--- FAIL: TestNatsUnassigningIrreplaceableDataRetiresItAndAnEmptyReplacementIsUrgent (0.61s)
data_integration_test.go:117: what the holder measured was not kept: {Machine:laptop Module:house Item:config Class:irreplaceable Path: Owned:true Protection:backup FirstSeen:2026-10-18 11:55:44.112549 +0000 UTC DeclaredAt:2026-10-18 11:55:44.112549 +0000 UTC MeasureError: Precision: Redundancy:<nil> Size:<nil> LastWrite:<nil> MeasuredAt:<nil> LastBackup:<nil> RetiredAt:<nil> RetiredWhy: DeletedAt:<nil> DeletedBy: DeletedWhy:}, <nil>
--- FAIL: TestIssue236AManifestTheNodeEngineRefusesFailsThePullRequest (1.54s)
merge_gate_integration_test.go:107: a service the node-engine refuses passed the gate:
merge gate: ERROR — the mesh as it is could not be raised, so the change cannot be judged against it (2 of 2 machines compose on the mesh and not in the gate); the first: a machine (kecitn) composes on the mesh and not as the gate raised it from the snapshot: the private network cannot be computed: whether fjtoel answers "mesh-addressing" cannot be read: this kind of record lives on the bus, and this process has not opened the bus: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus
judged by controller development build against the facts of 2026-10-18T11:55:49Z
FAIL github.com/novox/mesh-controller/cmd/mesh-controller 131s (shard 8 of 8: 139 tests)
--- FAIL: TestAPendingAssignmentIsAKeyOfTheAssignmentsBucket (0.18s)
chain_pending_test.go:61: the earlier wait is in the key's history: 3 values
FAIL github.com/novox/mesh-controller/internal/inventory 12s (shard 2 of 4: 89 tests)
```
mesh/merge-gate head 68db18bdfc1b merged into trunk da6d038e07c0 — pass: builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step; every …
The merge gate raises the snapshot's mesh in a throwaway store and now gives it a chain in memory, since the chain lives only on the bus. A module with no commit is carried by no send (a send is read from the commits on the assignments' keys), so the grants step flags only a module with a commit as newly assigned. The tests that sent a module with no build record one, the merge test waits for the merges' consumer before publishing and for the last look of a window before the next test, the pending test follows a chain that deletes nothing, and a wait's settling is a value of its key.
Merge check at 68db18bd
Judged: head 68db18bdfc1b merged into trunk da6d038e07c0; read beside it: mesh-catalog 7f77ce663a9e, mesh-controller-main da6d038e07c0, mesh-host 6469e8238443, mesh-tools 7412c5b6c9c5
mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller)
mesh/repo-check: PASS — its merge-check.sh passed
Delivery plan — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
tier 0: mesh-controller
tier 1: build-agent
ace: receives build-agent
g14: receives build-agent
novox: receives mesh-controller, build-agent
shanks: receives build-agent
build-agent keeps data (ADR 0233): what it holds is backed up before it moves
grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before build-agent is judged on its first machine
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Milestone 5 of design 47, delivery 2. Delivery 1 (mesh-controller #379, mesh-catalog #357) put builds, rollouts and assignments on the bus and moved the rows; the fix of issue 1121 (#380, ADR 0427) laid builds out under their module. This delivery makes the bus the only source (ADR 0408 §2, §8).
It removes data: migration 0105 drops the store's tables of builds, rollouts with their tiers and assignments, and chain_moved. It refuses, in the same transaction and before any drop, while a pending assignment is waiting, applying, or raised and unanswered. Your Approve of this merge is your word on dropping them; every row was copied onto the bus by delivery 1 and is read back from there.
layout.donemarker, never overwrites a pointer and skips records already laid out (nothing reads the chain before the marker exists).Issues: 1094, 1108, 1109, 1110, 1096, 1111; design 47 milestone 5 (981).
Reviewed-by: reviewer-1121@shanks at
7f074d9c94(the merge onto #380; delivery 2 itself approved in round 3 at 4eeba8fb203255297c47b33b1315d8722c67476c; head0b4cd46bonly merges main, identical tree)Delivery
novox/mesh-controller@68db18bdfc1b— delivered since 2026-10-18T12:45:04ZDelivery plan — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
Machines
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.Merge check at
0b4cd46bJudged: head
0b4cd46b3f04merged into trunkda6d038e07c0; read beside it: mesh-catalog7f77ce663a9e, mesh-controller-mainda6d038e07c0, mesh-host6469e8238443, mesh-tools7412c5b6c9c5mesh/merge-gate: ERROR — the mesh as it is could not be raised, so the change cannot be judged against it (4 of 4 machines compose on the mesh and not in the gate); the first: a machine (f35) composes on the mesh and not as the gate raised it from the snapshot: the private network cannot be computed: whether f35 answers "mesh-addressing" cannot be read: this kind of record lives on the bus, and this process has not opened the bus: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus (modules: mesh-controller)mesh/repo-check: FAIL — its merge-check.sh failed: --- FAIL: TestAnAssignmentThatBlocksAnotherMachineSaysWhichAndWhy (0.34s); and TestConvergingIsRefusedOnAPreviewThatWouldBeStale, TestTheFlipHoldsTheNodeWhileItSends, TestAPlanCutFromAMergeOfABackedUpModuleAsksItsBackupAndNotItsTierUntilItIsDone, TestAFailedWalkWalksItsEarlierMergesAlone, TestARepositoryMadeAgainUnderItsNameIsNotTheModulesSource and 395 moreDelivery plan — builds mesh-controller → novox; no bus step
Run by the build seat on ace as
build-1792323739962081324(builds --log build-1792323739962081324).Merge check at
0b4cd46bJudged: head
0b4cd46b3f04merged into trunkda6d038e07c0; read beside it: mesh-catalog7f77ce663a9e, mesh-controller-mainda6d038e07c0, mesh-host6469e8238443, mesh-tools7412c5b6c9c5mesh/merge-gate: ERROR — the mesh as it is could not be raised, so the change cannot be judged against it (4 of 4 machines compose on the mesh and not in the gate); the first: a machine (f35) composes on the mesh and not as the gate raised it from the snapshot: the private network cannot be computed: whether f35 answers "mesh-addressing" cannot be read: this kind of record lives on the bus, and this process has not opened the bus: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus (modules: build-agent, mesh-controller)mesh/repo-check: FAIL — its merge-check.sh failed: --- FAIL: TestAnAssignmentThatBlocksAnotherMachineSaysWhichAndWhy (1.02s); and TestConvergingIsRefusedOnAPreviewThatWouldBeStale, TestTheFlipHoldsTheNodeWhileItSends, TestAPlanCutFromAMergeOfABackedUpModuleAsksItsBackupAndNotItsTierUntilItIsDone, TestAFailedWalkWalksItsEarlierMergesAlone, TestARepositoryMadeAgainUnderItsNameIsNotTheModulesSource and 395 moreDelivery plan — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
Run by the build seat on ace as
build-1792323924401214012(builds --log build-1792323924401214012).Merge check at
cbc6bac8Judged: head
cbc6bac8c070merged into trunkda6d038e07c0; read beside it: mesh-catalog7f77ce663a9e, mesh-controller-mainda6d038e07c0, mesh-host6469e8238443, mesh-tools7412c5b6c9c5mesh/merge-gate: ERROR — the mesh as it is could not be raised, so the change cannot be judged against it (4 of 4 machines compose on the mesh and not in the gate); the first: a machine (f35) composes on the mesh and not as the gate raised it from the snapshot: the private network cannot be computed: whether f35 answers "mesh-addressing" cannot be read: this kind of record lives on the bus, and this process has not opened the bus: this control plane has no MESH_BUS_NATS, so it cannot reach the mesh's bus (modules: build-agent, mesh-controller)mesh/repo-check: FAIL — its merge-check.sh failed: --- FAIL: TestTheGrantsStepSendsTheUserListAndNothingElse (0.53s); and TestADeliveryGroupsHeadsAreComposedTogether, TestIssue285AModuleOnTheBusComposesInTheGate, TestMergesHeardWhileAnotherHolderHasThePlansAreRecordedAndCarried, TestALastSendIsReadFromTheSendAndTheReport, TestIssue285AMachineTheGateCannotRaiseIsAnErrorNeverAPass and 4 moreDelivery plan — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
Run by the build seat on ace as
build-1792324330116343529(builds --log build-1792324330116343529).Merge check at
68db18bdJudged: head
68db18bdfc1bmerged into trunkda6d038e07c0; read beside it: mesh-catalog7f77ce663a9e, mesh-controller-mainda6d038e07c0, mesh-host6469e8238443, mesh-tools7412c5b6c9c5mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller)mesh/repo-check: PASS — its merge-check.sh passedDelivery plan — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
Run by the build seat on shanks as
build-1792326164287115277(builds --log build-1792326164287115277).