Add new waiting strategy and timeout guards to Exasol container creation#27941
Conversation
577ada2 to
b394e4c
Compare
440c4f3 to
edcab9c
Compare
2e8c138 to
8921de0
Compare
|
@pj-spoelders the build isn't quite green. if this is not related to this PR, please rebase |
8921de0 to
e3b66a8
Compare
|
I've rebased @findepi |
6642a90 to
d690fb1
Compare
c6fbbfa to
5be8578
Compare
@pj-spoelders The default timeout is 30s (StartupCheckStrategy.timeout), right? How does this change (30s → 10s) resolve the hanging issue? |
5be8578 to
d44b0c3
Compare
It is the |
c7b810c to
ce06b7b
Compare
c30d80b to
54f81e9
Compare
aa9cb27 to
7422422
Compare
1f2f751 to
66e022f
Compare
66e022f to
81e716c
Compare
|
Looks like all comments addressed, LGTM |
81e716c to
e72896e
Compare
|
Thank you @pj-spoelders for your work! |
Description
Update to waiting strategies used for the Exasol docker container to come up for the product tests:
We've replaced the old port waiting strategy with a curl script that checks if Exasol is up and properly responding.
We've also added a timeout guard to both waiting strategies: This should solve the issue with product tests hanging if the database doesn't properly start.
Additional context and related issues
This was done in light of: #27339
Release notes
(x) This is not user-visible or is docs only, and no release notes are required.
( ) Release notes are required. Please propose a release note for me.
( ) Release notes are required, with the following suggested text: