chore(ci): configure slt shutdown timeout to 10s #22147
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
In some CI runs we find that connections cannot be shutdown in the grace period of 30s for
docker stop
. As a result, there's no chance for the diagnose step (#19787) to be run.risingwave/ci/scripts/common.sh
Lines 25 to 37 in aeac64b
This PR configures shutdown timeout to 10s to leave some time, by bump
sqllogictest
to 0.28.3 to include risinglightdb/sqllogictest-rs#265.Also fi x #22095 for CI image.
Checklist
Documentation
Release note