Fix flaky unit test on merge-triggered CI runs (#7)
CI / build-and-scan (push) Successful in 2m24s
CI / build-and-scan (push) Successful in 2m24s
- entrypoint.sh: bound the target connectivity check with `-w 2` (the only unbounded step in the startup path) - tests/entrypoint.bats: widen wait_for_log's budget from 5s to 10s Merge-triggered runs land on a colder runner (Docker cache evicted by other repos' scheduled jobs since the PR was last tested) than PR-check runs, and the first backgrounded entrypoint.sh in the suite was occasionally landing just past the old 5s window — always passed on rerun once warm.
This commit is contained in:
+1
-1
@@ -145,7 +145,7 @@ fi
|
||||
|
||||
log "[~] Testing connection to target..."
|
||||
# Test if we can reach the target before starting socat
|
||||
if ! nc -z "$TARGET_HOST" "$TARGET_PORT" 2>/dev/null; then
|
||||
if ! nc -z -w 2 "$TARGET_HOST" "$TARGET_PORT" 2>/dev/null; then
|
||||
log "[!] Cannot connect to $TARGET_HOST:$TARGET_PORT - socat will retry automatically"
|
||||
else
|
||||
log "[✓] Connection to $TARGET_HOST:$TARGET_PORT is working"
|
||||
|
||||
Reference in New Issue
Block a user