Skip to content

test(e2e): allow container startup before timeout #200

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
vishr merged 1 commit into from
Sep 20, 2026
Merged

test(e2e): allow container startup before timeout #200

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions e2e/testdata/postgres/ob.yml.tmpl
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -44,15 +44,16 @@ workloads:
# recorded timeout that `ob status` exposes. Its annual timer never fires
# during the suite; the test starts the service directly. The SLEEP input
# lets a later operator run succeed, which is the only thing that clears a
# recorded failure.
# recorded failure. The timeout leaves enough room for container startup and
# cleanup while remaining well below the deliberately wedged 30-second run.
timeout-chore:
role: job
image: public.ecr.aws/docker/library/busybox@sha256:9db7b59979c38555a39def84a31fb98b5296952f9e3afd4f6f11f05b07adfab0
command: ["sh", "-c", "sleep $SLEEP"]
data_effect: none
inputs:
SLEEP: {enum: ["0", "30"], default: "30"}
schedule: { cron: "0 0 1 1 *", timeout: 1s, catch_up: false }
schedule: { cron: "0 0 1 1 *", timeout: 5s, catch_up: false }
# Fails once, then succeeds: proves the in-firing retry and that the run
# record counts attempts. The marker lives on the host so the second
# attempt, a fresh container, can see the first one ran.
Expand Down