Re: [DISCUSS] KAFKA-4345: Run decktape test for each pull request

2016-11-08 Thread Raghav Kumar Gautam
On Mon, Nov 7, 2016 at 3:20 PM, Ewen Cheslack-Postava wrote: > On Mon, Nov 7, 2016 at 10:30 AM Raghav Kumar Gautam > wrote: > > > Hi Ewen, > > > > Thanks for the feedback. Answers are inlined. > > > > On Sun, Nov 6, 2016 at 8:46 PM, Ewen Cheslack-Postava > > > wrote: > > > > > Yeah, I'm all for

Re: [DISCUSS] KAFKA-4345: Run decktape test for each pull request

2016-11-07 Thread Ewen Cheslack-Postava
On Mon, Nov 7, 2016 at 10:30 AM Raghav Kumar Gautam wrote: > Hi Ewen, > > Thanks for the feedback. Answers are inlined. > > On Sun, Nov 6, 2016 at 8:46 PM, Ewen Cheslack-Postava > wrote: > > > Yeah, I'm all for getting these to run more frequently and on lighter > > weight infrastructure. (By th

Re: [DISCUSS] KAFKA-4345: Run decktape test for each pull request

2016-11-07 Thread Raghav Kumar Gautam
Hi Ewen, Thanks for the feedback. Answers are inlined. On Sun, Nov 6, 2016 at 8:46 PM, Ewen Cheslack-Postava wrote: > Yeah, I'm all for getting these to run more frequently and on lighter > weight infrastructure. (By the way, I also saw the use of docker; I'd > really like to get a "native" doc

Re: [DISCUSS] KAFKA-4345: Run decktape test for each pull request

2016-11-06 Thread Ewen Cheslack-Postava
Yeah, I'm all for getting these to run more frequently and on lighter weight infrastructure. (By the way, I also saw the use of docker; I'd really like to get a "native" docker cluster type into ducktape at some point so all you have to do is bake the image and then spawn containers on demand.) A

Re: [DISCUSS] KAFKA-4345: Run decktape test for each pull request

2016-11-03 Thread Becket Qin
Thanks for the explanation, Raghav. If the workload is not a concern then it is probably fine to run tests for each PR update, although it may not be necessary :) On Thu, Nov 3, 2016 at 10:40 AM, Raghav Kumar Gautam wrote: > Hi Becket, > > The tests would be run each time a PR is created/update

Re: [DISCUSS] KAFKA-4345: Run decktape test for each pull request

2016-11-03 Thread Raghav Kumar Gautam
Hi Becket, The tests would be run each time a PR is created/updated this will look similar to https://github.com/apache/storm/pulls. Ducktape tests take about 7-8 hours to run on my laptop. For travis-ci we can split them in groups and run them in parallel. This was done in the POC run which took

Re: [DISCUSS] KAFKA-4345: Run decktape test for each pull request

2016-11-03 Thread Becket Qin
Thanks Raghav, +1 for the idea in general. One thing I am wondering is when the tests would be run? Would it be run when we merge a PR or it would be run every time a PR is created/updated? I am not sure how long do the tests in other projects take. For Kafka it may take a few hours to run all th

Re: [DISCUSS] KAFKA-4345: Run decktape test for each pull request

2016-11-03 Thread Harsha Chintalapani
Thanks, Raghav . I am +1 for having this in Kafka. It will help identify any potential issues, especially with big patches. Given that we've some tests failing due to timing issues can we disable the failing tests for now so that we don't get any false negatives? Thanks, Harsha On Tue, Nov 1, 201

[DISCUSS] KAFKA-4345: Run decktape test for each pull request

2016-11-01 Thread Raghav Kumar Gautam
Hi, I want to start a discussion about running ducktape tests for each pull request. I have been working on KAFKA-4345 to enable this using docker on travis-ci. Pull request: https://github.com/apache/kafka/pull/2064 Working POC: https://travis-ci