test(hermes): track agent base repoint to in-cluster multi-arch mirror
test_gateway_image_honors_ui_model_and_caps_reasoning still pinned the old arm64-only docker.io base (nousresearch/hermes-agent@sha256:47d4bd4c...). The agent image moved to the multi-arch mirror base (harbor-core.harbor.svc.cluster.local/mirror/hermes-agent@sha256:9c841866...) in 8a710845 for the two-leg build; the test wasn't updated, so it was a latent red only the webui/quality lane runs. Point the assertion at the current base. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BvMSXH8VH2tMWXanb8SJdf
This commit is contained in:
parent
342677dde7
commit
4908e1ea37
@ -168,8 +168,8 @@ def test_sandbox_shares_only_the_tenant_workspace_without_credentials():
|
||||
def test_gateway_image_honors_ui_model_and_caps_reasoning():
|
||||
dockerfile = (ROOT / "dockerfiles" / "Dockerfile.hermes-agent").read_text()
|
||||
assert (
|
||||
"FROM nousresearch/hermes-agent@sha256:"
|
||||
"47d4bd4cc420b70e40ed75efdade373e45b86b7382d4013a054208982bb6ba08"
|
||||
"FROM harbor-core.harbor.svc.cluster.local/mirror/hermes-agent@sha256:"
|
||||
"9c841866021c54c4596849f6135717e8a4d52ba510b7f52c50aef1de1a283973"
|
||||
) in dockerfile
|
||||
assert "_resolve_request_route" in dockerfile
|
||||
assert 'allowed_providers = {"atlas-switchyard"}' in dockerfile
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user