Skip to content
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.

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

Integration Test on AMD64 Keeps Failing #3998

Closed
STRRL opened this issue Apr 4, 2023 · 3 comments
Closed

Integration Test on AMD64 Keeps Failing #3998

STRRL opened this issue Apr 4, 2023 · 3 comments
Assignees
Labels
component/tests type/bug Something isn't working

Comments

@STRRL
Copy link
Member

STRRL commented Apr 4, 2023

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:

image

What did you expect to see?

What did you see instead?

Output of chaosctl

@STRRL STRRL self-assigned this Apr 4, 2023
@g1eny0ung g1eny0ung added type/bug Something isn't working component/tests labels Apr 6, 2023
@g1eny0ung
Copy link
Member

g1eny0ung commented Apr 6, 2023

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.

@STRRL
Copy link
Member Author

STRRL commented Apr 12, 2023

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.

@STRRL STRRL closed this as completed Apr 12, 2023
@g1eny0ung
Copy link
Member

Definitely yes, maybe later in next month, I would have more time on it.

That would be great! 🙌🏼

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/tests type/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants