narendly commented on issue #1319: URL: https://github.com/apache/helix/issues/1319#issuecomment-685000167
Some general logistics are documented in https://github.com/apache/helix/wiki on the right sidebar. As for running tests, we follow standard practices for maven projects. There are some failing tests though, so what we want to do is 1. Build the project at the top-level project path (where the parent pom.xml is): mvn clean install package -DskipTests 2. Run tests for separate modules (e.g. /helix-core, /zookeeper-api, /helix-rest, /helix-common, etc) Usually these 4 modules cover everything. Other modules have some failing tests, so I wouldn't be too concerned about those. With the exception of /helix-core, you should see all tests pass. For helix-core, we see as many as 3-4 failing tests depending on the machine (we are currently trying to stabilize tests). At that point, we run these tests individually using the following mvn command: mvn test -Dtest=<your test name> Usually when the failed tests are run individually, they pass. If they don't that means something went wrong. It would also be helpful for us to know which tests are failing exactly as well. You could document that in your pull request draft as well. If this is helpful, you're more than welcome to add this piece of information on the wiki page sidebar for future contributors. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
