Hi Anton, It should not be a machine issue, since you have the container got started. I would say give it around 5 - 10 minutes, it would throw out connection time out error log. This usually happens when the integration tests can't connect to the container. As you may notice, in the tests we don't hard code the container IP and port, and we get it dynamically from the TestContainer framework. Which mean, for some reason, the framework couldn't allocate IP and port for the container. At this moment I don't have a quick fix, but if it happens to several dev, we can file a Jira to their dashboard, or get rid of it.
P.S. try this gradlew `./gradlew :sdks:java:io:amazon-web-services:test` Thanks, On Sat, Jul 20, 2019 at 6:33 AM Elliotte Rusty Harold <elh...@ibiblio.org> wrote: > I've seen this myself trying to run tests in Linux (Goobuntu). > > On Fri, Jul 19, 2019 at 1:15 PM Anton Kedin <ke...@google.com> wrote: > > > > Hi dev@, > > > > Does anyone know if there's anything extra needed to run > `DynamoDBIOTest`? If I do `./graldew > :sdks:java:io:amazon-web-services:build --debug` it passes few tests during > `:test` but then seems to sit on `DynamoDBIOTest` forever. No errors, last > meaningful log is `INFO: Container localstack/localstack:0.8.6 started`. > Happens on different machines, both on master and release-2.14.0 branches. > > > > Any pointers? > > > > Regards, > > Anton > > > > -- > Elliotte Rusty Harold > elh...@ibiblio.org >
