{"push_id":836829000,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"fa1359fd43ce963a74ee67a2ac80014fc6ae1372","before":"0c47ad4402bbf4779ab9f77869bdbc780c61d1b7","commits":[{"sha":"fa1359fd43ce963a74ee67a2ac80014fc6ae1372","author":{"email":"317a993f1126881a6019d7e476a07af7fa3e05fe@digium.com","name":"Matt Jordan"},"message":"asterisk/sipp: Add option to SIPpScenarioSequence to control stopping reactor\n\nBy default, SIPpScenarioSequence will stop the TestCase object reactor when the\nfinal SIPp scenario in the sequence has finished. In some cases, however,\nparticularly when the SIPp scenarios are being used to drive a more complex set\nof tests, this isn't desireable. Instead, the test is stopped based on more\ncomplex criteria outside of the SIPp scenario's knowledge.\n\nThis patch adds a new option to the SIPpScenarioSequence constructor that\ninforms it to stop the reactor when all scenarios have executed. By default,\nthis option is set to True for backwards compatibility reasons.\n\nChange-Id: I4811f25ec1a9c77bbd122de43e4e228d7f5a9c2a","distinct":true,"url":"https://api.github.com/repos/asterisk/testsuite/commits/fa1359fd43ce963a74ee67a2ac80014fc6ae1372"}]}