Stabilize e2e #65
Merged
Stabilize e2e #65
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
abicky
force-pushed
the
stabilize-e2e
branch
9 times, most recently
from
0f7170c to
496c21b
Compare
Signed-off-by: Takeshi Arabiki <takeshi.arabiki@datachain.jp>
To prevent geth containers from getting stuck Signed-off-by: Takeshi Arabiki <takeshi.arabiki@datachain.jp>
yoshidan
approved these changes
May 13, 2025
siburu
approved these changes
May 13, 2025
Contributor
Author
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR resolves the following CI failures as you can see in the PR #64.
As a rule of thumb, they seems to be caused by unhealthy geth processes, so I have added health checks and a autoheal container to automatically restart containers where such a process is running.
ProviderError: transaction indexing is in progress
IBCClient deployment gets stuck