On 10 March 2017 at 05:51, Jason Brown <jasedbr...@gmail.com> wrote: > A nice convention we've stumbled into wrt to patches submitted via Jira is > to post the results of unit test and dtest runs to the ticket (to show the > patch doesn't break things). > [snip] > As an example, should contributors/committers run dtests and unit tests on > *some* machine (publicly available or otherwise), and then post those > results to the ticket?
Yes please. I'm a supporter that nothing should get committed without it passing both unit and dtests. That any SHA in trunk or any release branch that fails unit or dtests is automatically uncommitted (reverted). I was under the impression that the point of tick-tock was to move the code towards a stable master approach. And that the lesson learn that restricting any release to only have one patch version is: regardless of how good the developers and CI system is; a pretty poor way of trying to build a stable product. So from tick-tock to 4.0, I was really hoping it meant keeping all the stable master and CI improvements obtained throughout the tick-tock cycle while re-adding the discipline of ongoing patch versions to supported releases. (While being realistic to resources available.) Unfortunately without access to DS' cassci the best that i could do is this: https://issues.apache.org/jira/browse/CASSANDRA-13307?focusedCommentId=15962001&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15962001 And running dtests on ASF's Jenkins was a 30hr turn around. :panda_face: Is there any hope here for us that don't have access to cassci? ~mck
