Prathamesh Musale 787806d6fa fix: wait_for_log_output should ignore "No logs available" responses ... The k8s logs command returns "No logs available" or "Pods not running" when containers aren't ready yet. Since these are non-empty strings, wait_for_log_output() was treating them as success, causing the subsequent content check to fail. Also fix unquoted echo glob expansion. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>		2026-04-02 08:11:03 +00:00
..
container-registry	fix: wait_for_log_output should ignore "No logs available" responses	2026-04-02 08:11:03 +00:00
database	fix: add --perform-cluster-management to k8s test scripts	2026-04-02 06:47:22 +00:00
deploy	fix: resolve stack path from repo root + update deploy test	2026-03-20 15:14:47 +00:00
external-stack	Add --update option to deploy create	2026-01-29 08:25:05 -06:00
fixturenet-laconicd	Update fixturenet-laconicd stack for renaming changes (#891)	2024-07-25 08:50:15 +00:00
k8s-deploy	fix: imagePullPolicy for kind, job images, duplicate registry call, test namespace	2026-04-01 23:34:51 +00:00
k8s-deployment-control	fix: wait_for_log_output should ignore "No logs available" responses	2026-04-02 08:11:03 +00:00
laconic-network	Apply pre-commit linting fixes	2026-01-20 23:16:44 -05:00
mainnet-eth	Apply pre-commit linting fixes	2026-01-20 23:16:44 -05:00
scripts	Add Job and secrets support for k8s-kind deployments (#995)	2026-03-11 03:56:21 +00:00
smoke-test	rename laconic-sdk to registry-sdk (#897)	2024-07-31 08:01:02 +00:00
webapp-test	Fix invalid docker command in webapp-test	2026-01-24 16:39:00 -05:00