{"push_id":864120179,"size":1,"distinct_size":1,"ref":"refs/heads/no_more_jvm_leaks","head":"937338215525c1a66102ceafd7905813c1561b3a","before":"6fad821d80ef68358444430cd4b62da148840435","commits":[{"sha":"937338215525c1a66102ceafd7905813c1561b3a","author":{"email":"ea3cd978650417470535f3a4725b6b5042a6ab59@iernst.net","name":"Ryan Ernst"},"message":"Build: Use ant exec for starting elasticsearch in integ tests\n\nCurrently elasticsearch in integ tests is started using an ant task on\nwindows, or gradle exec on everything else. However, gradle exec has\nsome flaws, one being Ctrl-C does not run finalizedBy tasks, which means\ninterrupting integ tests will leak a jvm. This change makes all systems\nuse ant exec. One caveat is, if there is any output by the jvm, we lose\nit in ant bit heaven. But this is no different than what we had with\ngradle. In the future, we should look at using a separate thread to\npump streams from the elasticsearch process.\n\ncloses #14701","distinct":true,"url":"https://api.github.com/repos/rjernst/elasticsearch/commits/937338215525c1a66102ceafd7905813c1561b3a"}]}