I have trouble compiling using gradlew build. It c...
# troubleshootb
brief-lizard-77958
11/15/2021, 2:11 PMI have trouble compiling using gradlew build. It completes everything successfully up to metadata iotest. It fails for
ElasticSearchSystemMetadataServiceTest. setup
From the report in metadata-io folder:
org.testcontainers.containers.ContainerLaunchException: Container startup failed
Full log of the report for ElasticSearchSystemMetadataServiceTest in the attached html file.
I have datahub running (using quickstart.sh) in the background and everything is working properly.
Is it possible that this is related to not having enough resources (CPU) to perform the build?
✅ 1
m
miniature-tiger-96062
11/15/2021, 4:24 PMHi Andrew,
It is possible that you are running into issues with resources with docker so please try increasing the resources. We do have a recommendation but I see that docker quickstart is working fine for you. A good starting point is -
Copy code
2 CPUs, 8GB RAM, 2GB Swap area, and 10GB disk space.miniature-tiger-96062
11/15/2021, 4:26 PMAnother thing you could try is to run with build with -x test options that will build the modules and not run tests. Later you can do the build for the specific submodule you are working on (including the tests).
b
brief-lizard-77958
11/15/2021, 4:29 PMGreat answer. Thank you very much
brief-lizard-77958
11/16/2021, 11:34 AMI increased my CPU resources by a lot but still got the same failure on build at the metadata tests. Omitting metadata iotest makes the build finish successfully. There doesn't seem to be any change in functionality - everything works as expected. Is it possible that if I change the code and compile like this that some parts of the application won't work properly?
m
mammoth-bear-12532
11/23/2021, 5:16 PM
@brief-lizard-77958: if you are not modifying the
metadata-iometadata-io:testb
brief-lizard-77958
11/23/2021, 7:00 PM@mammoth-bear-12532 Good to know, thanks!
2 Views