You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
e2e: the leak-guard allowlist and the suite docs assume every suite is a chainsaw-test.yaml #4659
The e2e selectors now see every layout Chainsaw runs (#4630): chainsaw-test.yaml, chainsaw-test.yml, numbered step files, and a Test nested below a suite directory. Three places still assume the first layout only.
hack/e2e-chainsaw/_lib/leak-guard.sh, lg_allowlist_validate, accepts only <suite>/chainsaw-test.y*ml entries, so a step-file or nested suite cannot be put on the allowlist and fails validation loudly.
hack/e2e-chainsaw/README.md says each suite has a chainsaw-test.yaml.
docs/agents/e2e-testing.md calls the Proxmox suite the one disabled suite, but hack/e2e-chainsaw/backup/ also holds only a chainsaw-test.yaml.disabled.
Fix shape: validate allowlist entries against the same discovery rule the selectors use, and describe the layouts once in the README with the doc pointing at it. Drop the "one suite" count rather than fixing it.
hack/e2e-chainsaw-run.sh refuses a top-level test with the globs chainsaw-test.y*ml and [0-9]*-*.y*ml, which are wider than Chainsaw's own step-file pattern. It fails closed (stops the run), so this is a precision issue, not a coverage hole.
One more instance of the same drift: hack/e2e-chainsaw/README.md has no entries for the backup, kafka-metadata and kubernetes-proxmox suites (#4678 adds monitoring).
Fix in #4972 for the allowlist validation (same discovery rule as select-e2e.sh, with unit tests for every layout) and the docs. Two items are left as they are, with the reasons in the PR: the backup directory is gone from main, so the "one parked suite" sentence is correct now, and the runner's top-level globs are wider than Chainsaw's pattern but fail closed.
Activity
lexfrei commentedon Oct 1, 2026
Two more selector edges of the same kind, found while finishing #4658, both unchanged from main:
examples/backups/whose name matches no suite (for exampleexamples/backups/common/helpers.sh) selects nothing. ci: the e2e selectors miss Chainsaw step-file suites and loose files under examples/backups #4630 covered only files placed directly inexamples/backups/, plus_lib/.hack/e2e-chainsaw-run.shrefuses a top-level test with the globschainsaw-test.y*mland[0-9]*-*.y*ml, which are wider than Chainsaw's own step-file pattern. It fails closed (stops the run), so this is a precision issue, not a coverage hole.lexfrei commentedon Oct 1, 2026
One more instance of the same drift:
hack/e2e-chainsaw/README.mdhas no entries for thebackup,kafka-metadataandkubernetes-proxmoxsuites (#4678 addsmonitoring).themoriarti commentedon Oct 19, 2026
Fix in #4972 for the allowlist validation (same discovery rule as
select-e2e.sh, with unit tests for every layout) and the docs. Two items are left as they are, with the reasons in the PR: thebackupdirectory is gone from main, so the "one parked suite" sentence is correct now, and the runner's top-level globs are wider than Chainsaw's pattern but fail closed.fix(e2e): validate the leak allowlist against every suite layout
fix(e2e): validate the leak allowlist against every suite layout (coz…
fix(e2e): validate the leak allowlist against every suite layout
fix(e2e): validate the leak allowlist against every suite layout (#4972)