Aleksei Sviridkin 65c183e311 fix(e2e): keep backup preflight failure evidence across attempts ...

The backup access preflight printed its port-forward capture only when
the port-forward never came up, and truncated its mc log at the top of
every attempt. On the path that fails in practice, a healthy
port-forward and an S3 round trip that never completes, the output was
the tail of the last attempt with nothing to say which stage it died
at, which reads as a successful upload followed by a hung download.

Print the port-forward capture alongside the mc log on the timeout
path, append the mc log across attempts, and record which of PUT, GET,
compare or DELETE each attempt reached.

Assisted-by: LLM
Signed-off-by: Aleksei Sviridkin <f@lex.la>

2026-09-14 22:59:37 +03:00

..

backup-access-preflight.sh

fix(e2e): keep backup preflight failure evidence across attempts

2026-09-14 22:59:37 +03:00

etcd-cleanup.sh

test(e2e): address review nits — shellcheck directive + ports-workaround TODO

2026-07-10 17:02:46 +05:00

etcd-probe.sh

test(etcd): stop losing the metrics probe's output to the attach race

2026-07-19 20:16:01 +03:00

pod-label-census.sh

fix(e2e): select catch pod logs by the nested release instance label

2026-08-05 16:46:50 +03:00

remediation-guard.sh

test(e2e): address review nits — shellcheck directive + ports-workaround TODO

2026-07-10 17:02:46 +05:00

run-kubernetes.sh

fix(e2e): make the OIDC teardown assertions fail closed

2026-09-07 16:31:08 +05:00

talos-image-cache.sh

test(e2e): stop blocking merges on the tenant node-join deadline

2026-08-21 12:52:42 +03:00