Hi Abhishek, Thanks a lot for your effort, test is very important for an open-source project. Does the test framework allow to do performance test? Any doc about that
------------------------------------------------------------------ 发件人：Abhishek Girish <agir...@apache.org> 发送时间：2022年3月24日(星期四) 10:40 收件人：dev <dev@drill.apache.org> 抄 送：agozhiy <agoz...@apache.org> 主 题：Re: [VOTE] Adopt the Drill Test Framework from MapR Hi all, I'm fully supportive of this. Years back, I led the effort to open-source this framework - for very similar reasons. It was well received, but we realized it not being part of the official Drill repo was not letting it realize it's full potential and hence remained on the sidelines. It remains heavily used inside MapR/HPE, but isn't part of our pre-commit or pre-release criteria. We discussed making the test framework part of the apache/drill repo, but that wasn't ideal, as it would have significantly added to the overall repo size and footprint. After looking at the Arrow Project, I had similar ideas as James now, to create a set of repos - one for the test framework (apache/drill-test-framework), one for a Jenkins env (apache/drill-jenkins) and such. Only I didn't do anything about it then! I discussed the current proposal with Anton & James - on ways to proceed. Transferring the existing test framework repo ownership to Apache would have been ideal, but it appears it's not straightforward. So I have to abandon that plan. I think we should proceed with the plan of pushing a clone of mapr/drill-test-framework to apache/drill-test-framework. And in fact, I already did :) https://github.com/apache/drill-test-framework is now live! We'll plan to archive mapr/drill-test-framework and move all future activity to apache/drill-test-framework This is a big milestone. But there is more to be done (including for example, creating the Jenkins repo - which can be very useful to schedule & operate tests). Regards, Abhishek On Fri, Mar 18, 2022 at 6:49 AM James Turton <dz...@apache.org> wrote: > Hi Cong Luo > > Yes, this is the same project as DRILL-8120. Anton Gozhiy is actively > working on the test framework, I'm not sure if there are others too. I > agree that an introduction would be helpful. Maybe in the next > community meetup someone who is familiar with the test framework, like > Anton or Abhishek, can introduce the rest of us in the Drill dev > community to it, so that we can all start adding and maintaining tests, > and benefiting from it. > > A related point is that I went and looked at the specs of the VMs that > the ASF allocates to projects and we'd need a special motivation to get > more than one VM with 1GiB of RAM. Meanwhile I think that the full test > framework would like to run with resources than that, and probably > against a cluster. So I suspect that we can find some other use for the > small VM from the ASF, and one or more of our corporate sponsors can run > the test framework in an elastic way in one of the clouds (create a > cluster, then destroy all allocated instances once the tests have run). > > James > > On 2022/03/18 13:09, luoc wrote: > > Hi all, > > > > If the new repository is created, I hope this is the new progress with > DRILL-8120 <https://issues.apache.org/jira/browse/DRILL-8120>. > > > > Then, can test framework contributors answer the following questions? > > > > 1. Who are the active contributors to this test framework? > > > > 2. Are we planning to add more contributors (and how do we implement it)? > > > > 3. Can the contributors outline the design idea and function set of the > test framework here? > > > > Again, thanks to Charles's company and HPE team for supporting Apache > Drill. > > > > Thanks. > > > >> 2022年3月18日 下午12:56，Paul Rogers <par0...@gmail.com> 写道： > >> > >> Abhishek used to have that thing running like a charm. Great to see it > >> getting attention again. > >> > >> +1 > >> > >> - Paul > >> > >> On Thu, Mar 17, 2022 at 2:03 AM James Turton <dz...@apache.org> wrote: > >> > >>> Hi dev community! > >>> > >>> Many of you need no introduction to the test framework developed by > MapR > >>> > >>> https://github.com/mapr/drill-test-framework > >>> > >>> . For those who don't know, the test framework contains around 10k > tests > >>> often exercising scenarios not covered by Drill's unit tests. Just > weeks > >>> ago it revealed a regression in a Drill 1.20 RC and saved us from > >>> shipping with that bug. The linked repository has been dormant for > going > >>> on two years but I am aware of bits of work that have been done on the > >>> test framework since, and today Anton is actively dusting off and > >>> updating it. Since the codebase is under the Apache 2.0 license, we are > >>> free to bring a copy into the Drill project. I've created a new > >>> (currently empty) possible home for the test framework at > >>> > >>> https://github.com/apache/drill-test-framework > >>> > >>> Before I proceed to push a clone there, please vote if you support or > >>> oppose our adoption of the test framework. > >>> > >>> P.S. I have also sent a message to a contact at HPE just in case they > >>> might be aware of some concern applicable to our copying this repo but, > >>> given the license applied, I cannot see that there will be be one. > >>> Should anything get raised (and we'd decided to proceed) I would, of > >>> course, pause so that we can discuss. > >>> > >>> Regards > >>> James > >>> > > > >
