Hi Geode community,
We are trying to set up a CI loop in our Geode fork. We have started with the
tests that are run for every pull requests, but we are having problems to
replicate what is done in the Apache Geode repository, so any help will be
appreciated.
We are not using concour, but we are trying to run the same commands that are
run at the end.
In the case of distributedTests, if we run them we have problems saying that
there are ports in use, which are not present if we run the tests independently
( I mean running for example "geode-core:distributedTest",
"geode-cq:distributedTest" instead of just "distributedTest"). So we think we
are missing something regarding the configuration of the VM where the tests are
executed. We have seen there is a custom image used in google cloud (
--image-family="${IMAGE_FAMILY_PREFIX}${WINDOWS_PREFIX}geode-builder" ), is it
documented somewhere which are the requirements or configuration of that image?
We have seen in the CI configuration
(https://github.com/apache/geode/blob/develop/ci/pipelines/shared/jinja.variables.yml)
that the requirement for distributedTests are 96 cpus & 180GB RAM. We can use
only 24 cpus and 128GB RAM, but we have seen the tests are executed using the
"dunitParallelForks" parameter to control how many docker containers are run in
parallel, so we suppose we should modify this parameter.
Where can we check how are these containers created and controlled?
Thanks in advance!
Alberto B.
