Repository navigation
test: centralize Varnish runtime diagnostics in E2E harness - #136
Merged
jonbaldie merged 1 commit intoOct 7, 2026
Merged
Conversation
Add a shared Varnish container lookup, expose assert_no_vcl_errors to scenario assertions, and include VSL records when Compose fixtures fail. The unsafe-location scenario uses the no-pattern assertion because its VSL contains no other VCL_Error records. Closes #128
jonbaldie
deleted the
fleet/ci-52a62331b424414b9ed39cae87e085a0-1-8376b8d2c5a1
branch
October 7, 2026 06:42
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.
Closes #128
Summary
assert_no_vcl_errors <context> [pattern]and refactor the unsafe-location scenario to use it.Verification
make test-compose-fixture-lifecycle,make test-purge,make test-hostile-unsafe-location, andmake test-hostile-unsafe-location-canary.assert_no_vcl_errorsand showed theban(): Expected && between conditionsVSL record.COMPOSE_PARALLEL_LIMIT=1 make -j1 test test-e2e-hardstopped at the existingtest-smoke-runtime-interfacetarget: its 5-second startup probe killed adocker runthat took about 10 seconds to exit after printing the expected invalid-listen error. The gate did not reach the harness tests.