Skip to content
This repository has been archived by the owner on Dec 16, 2024. It is now read-only.

Integration tests sometimes fail with Endpoint request timed out #427

Closed
lukehoban opened this issue Mar 12, 2018 · 1 comment
Closed

Integration tests sometimes fail with Endpoint request timed out #427

lukehoban opened this issue Mar 12, 2018 · 1 comment
Assignees
Milestone

Comments

@lukehoban
Copy link
Contributor

We have started frequently seeing the containers test fail with the following:

aws_test.go:232: GET https://ys6gq6ipi1.execute-api.us-east-2.amazonaws.com/stage/ [504/application/json]: {"message": "Endpoint request timed out"}

The other endpoints on this HttpAPI don't fail, but this one endpoint does frequently fail.

The one difference between this endpoint and the others is that it tries to make an HTTP request to one of the cloud.Services. It seems that this connection must be timing out (or taking more than 30seconds - causing the HttpEndpoint to time out).

My best guess is that the containers are not ready to start accepting requests yet at the time this HttpEndpoint it invoked. I suspect this is because our change to add wait_for_steady_state to ECS service only handled the Update case, not the Create case. And possibly because we are now creating resource not in program order - the ECS service is getting created closer in time to when the ExtraRuntimeValidation happens, leading to occasional test failures.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants