-
Notifications
You must be signed in to change notification settings - Fork 106
Integration test suite is broken #47
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
Comments
skwashd
added a commit
to skwashd/aws-lambda-runtime-interface-emulator
that referenced
this issue
Sep 4, 2021
The integration tests were failing due to multiple issues. Multiple tests were using the same container name (`testing`), which meant some of the tests weren't running. Now each container has a unique name. The same port (9000) was being used for multiple tests. This wasn't showing as an issue as these tests also used the same container name. The ports are now unique per test, with them being number sequentially to avoid any conflicts. Only some of the running containers were terminated when the suite finished executing. This caused many tests to not run properly on subsequent invocation of the suite. Now all containers are terminated when the tests complete. The timeout tests weren't waiting for the container be ready. This was caused by the order of operations being wrong, with the sleep step occurring after the request to the endpoint, not before. This commit fixes aws#47.
Closed
Fixed by the linked PR. Let us know if you're still experiencing these issues. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The tests aren't running properly because of duplicated container names. Further subsequent invocations create further failures because the tear down step is missing some of the containers.
Despite these failures being noted in the console, the test suite only catches one of the failures on the first run. On the second run there are more errors, but the suite passes.
First Invocation
Second Invocation
The text was updated successfully, but these errors were encountered: