Skip to content

[BUGFIX] Wait longer for database readiness #94

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
sbuerk merged 1 commit into from
Jul 30, 2026
Merged

[BUGFIX] Wait longer for database readiness #94

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
11 changes: 9 additions & 2 deletions Build/Scripts/runTests.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,10 +10,13 @@ fi
waitFor() {
local HOST=${1}
local PORT=${2}
# 60 rather than 10 seconds: mysql:8.0 needs 12-13s under docker to
# initialise a fresh data directory, about twice as long as under podman,
# so an 11 second budget aborted the functional mysql suites at random.
local TESTCOMMAND="
COUNT=0;
while ! nc -z ${HOST} ${PORT}; do
if [ \"\${COUNT}\" -gt 10 ]; then
if [ \"\${COUNT}\" -gt 60 ]; then
echo \"Can not connect to ${HOST} port ${PORT}. Aborting.\";
exit 1;
fi;
Expand All @@ -23,7 +26,11 @@ waitFor() {
"
${CONTAINER_BIN} run ${CONTAINER_COMMON_PARAMS} --name wait-for-${SUFFIX} ${XDEBUG_MODE} -e XDEBUG_CONFIG="${XDEBUG_CONFIG}" ${IMAGE_PHP} /bin/sh -c "${TESTCOMMAND}"
if [[ $? -gt 0 ]]; then
kill -SIGINT -$$
# Not "kill -SIGINT -$$": the SIGINT trap is only installed when CI is
# not "true", so in CI the signal was a no-op, the run continued and the
# test suite connected to a database that was not listening.
cleanUp
exit 1
fi
}

Expand Down