Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Starting clover distributed tests binds only to 127.0.0.1 and tests never start

Am trying to start clover distributed tests. When I run the command "mvn clean clover:setup -Dtest=TestClassName test -Dclover.distributed.coverage=numClients=1 -Dclover.distributed.coverage=host=<my actual ip address> -Dclover.server=true -Dclover.initstring=/functional_regression/target/clover/clover.db" the test does not wait for the clients to connect and just continues.

 

Instead when I use "mvn clean clover:setup -Dtest=TestClassName test -Dclover.distributed.coverage=numClients=1 -Dclover.server=true -Dclover.initstring=/functional_regression/target/clover/clover.db", the test waits for client to connect, but at this point the clover server is bound to 127.0.0.1 due to which the remote client cannot connect to the server and hence the tests never start.

 

Am I doing something incorrectly?

2 answers

0 votes

When you provide clover.distributed.coverage system properties twice, you simply override values. 

 

If you want to config multiple properties for distributed coverage you shall use as a separator. 

 

Please take a look at the code

Was able to solve this my adding the ip in the pom's plugin configuration instead of giving it in the command line. This way, the process binds to the right IP as well as waits for clients to connect. Sample configuration that I used

<plugin>
<groupId>org.openclover</groupId>
<artifactId>clover-maven-plugin</artifactId>
<version>4.4.0</version>
<configuration>
<distributedCoverage>
<host>1.2.3.4</host>
<port>1198</port>
<numClients>1</numClients>
<timeout>10000</timeout>
</distributedCoverage>
</configuration>
</plugin>

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira

Jira Cloud Performance Improvements

Hello everyone, I am a product manager in the Jira Cloud team focused on making sure our customers have a delightful experience using our products. Towards that goal, one of the areas which is extr...

167 views 2 9
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you