You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
error: timed out waiting for the condition on pods/localstack-5bf996bf57-jxktr
Most failures are due to timeouts (60s) when bootstrapping the LocalStack. A straightforward way to fix this is to increase the timeout duration.
But since I remember that the previous integration tests were also often wrong (unstable), we should consider overhauling the integration tests to make them as practical as possible.
I am going to close this issue because it was recovered. Maybe there is something like networking or computing platform changed behind GitHub Action, and then it recovered.
Most failures are due to timeouts (60s) when bootstrapping the LocalStack. A straightforward way to fix this is to increase the timeout duration.
Yeah, I noticed that. But It seems the Integration Tests have been recovered without any code changes.
But since I remember that the previous integration tests were also often wrong (unstable), we should consider overhauling the integration tests to make them as practical as possible.
Definitely yes, maybe later in next month, I would have more time on it.
Bug Report
What version of Kubernetes are you using?
N/A
What version of Chaos Mesh are you using?
N/A
What did you do? / Minimal Reproducible Example
I noticed that Integration Tests faced continues failing recent days:
What did you expect to see?
What did you see instead?
Output of chaosctl
The text was updated successfully, but these errors were encountered: