Repository navigation
Drop unused MCP edge inputs from Pod, VM and Firecracker tests - #16220
Merged
Merged
Conversation
Contributor
This was referenced Nov 13, 2026
agentydragon
added a commit
that referenced
this pull request
Nov 13, 2026
Records the source663 milestone: real TokenReview admission negatives and History outage/catch-up in the native Sampler test; six selected targets pass 25 Python JUnit cases plus Go startup, and all required checks pass in 10m01s from workflow creation. Earlier source91f observations remain explicitly historical; no matched speedup or gate/frequency promotion is claimed. Adds reviewed evidence for merged devel PRs #16218/#16220, the managed-VM kernel fault and automatic VM-suite re-execution tracked in #16222, actual Bazel profile limits, read-only KVM colocation feasibility, and the partial historical replay with both failed attempts preserved. No live infrastructure change. Validation: final assets passed RBE browser validation at 18b344e4-e593-4d13-bca2-b9bf3715430c: four desktop/mobile light/dark cases, 76 screenshots, live OS theme switching, expanded selectors/plan/cohort, zero errors or skips. Four representative final images inspected; all 11 packaged/browser-fetched/final asset SHA256 values match. Only the architecture report namespace changes; shared navigation and assets are preserved. Live publication will be verified separately after merge.
Open
5 of 6 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pod scenarios, VM and Firecracker fixtures render and import MCP-edge even though their scenarios do not use external Connections. This gives MCP-edge source changes an unnecessary dependency path into three costly deployment suites.
Give those fixtures a
NO_MCP_EDGEprofile and exclude its OCI image from their declared inputs. Keep Actions, all retained rendered resources, scenario bodies and test frequency. Default, Dispatcher, deletion, real-model and MCP acceptance retain the full service. Renderer tests require every retained object to match the full profile and verify that default/MCP fixtures still include the edge.Normal hooks pass. Required PR CI validates this independent backport. On architecture source
91f72591a1, the unchanged Pod/full-VM/both Firecracker cases passed required CI; a source-pinned synthetic selector comparison selected 15 rather than 18 tests, removing exactly these three suites while retaining MCP acceptance. That is graph evidence for one footprint, not a measured CI-time saving or a representative workload frequency.This leaves the architecture branch's native contracts, case concurrency, Secret cadence, reconnect-budget and candidate split experiments in #16102; none is needed for this input cut. Revert this profile change to restore full fixture/image ownership if a retained scenario acquires an MCP dependency.