Oh sry somehow I missed a detail there, it was the virtualenv use case where I need to do the pip install. The docker approach went smoothily. I recall two test cases where I need to install packages, one is from the gcp operator tests and the other is a celery executor test( sry I can't remember the exact test names).
(One more little thing: `./breeze --build-docs` seems to fail, I've being using `./scripts/ci/ci_docs.sh` instead. And wanna use this opportunity to complain that debugging doc building error is really a headache :) ) On Thu, Aug 29, 2019 at 4:29 AM Jarek Potiuk <jarek.pot...@polidea.com> wrote: > Fantastic. Thanks. Do you recall which tests/packages they were? I'd love > to see whats's the root cause. We are using the same image in CI and the > tests pass, so I wonder what could be the reason for that. > > On Thu, Aug 29, 2019 at 4:13 AM Kevin Yang <yrql...@gmail.com> wrote: > > > Was looking forward to this since last meet up in bay area. Tried both > the > > docker solution and the virtualenv IDE( PyCharm) solution today and it > was > > great. Great job Jarek and thank you so much. > > > > (One minor thing that may just be problem on my side: some tests complain > > about missing package so I did a `pip install -e ".[all]"` and it went > > smoothily afterwards) > > > > > > Cheers, > > Kevin Y > > > > On Wed, Aug 28, 2019 at 12:04 PM Felix Uellendall <felue...@pm.me.invalid > > > > wrote: > > > > > Great job Jarek! Thanks. I am looking forward to try it out as soon as > I > > > am back from holiday :) > > > > > > Felix > > > > > > Sent from ProtonMail mobile > > > > > > -------- Original Message -------- > > > On Aug 28, 2019, 10:34, Jarek Potiuk wrote: > > > > > > > Just FYI. We had some "teething" problems (of course) at the workshop > > but > > > > fixes to it are already merged to master (thanks Kaxil for the > review)! > > > > > > > > J. > > > > > > > > On Wed, Aug 28, [2019](tel:2019) at 2:17 AM Chao-Han Tsai < > > > milton0...@gmail.com> wrote: > > > > > > > >> Thanks Jarek for the hard work. It really improved the airflow > > > development > > > >> experience a lot. > > > >> I remember the struggling I experienced to reproduce CI bug locally > > and > > > I > > > >> am > > > >> glad that those days are now gone. This really lowered the barrier > to > > > >> contribute to Airflow and > > > >> I look forward to more people joining the airflow community! > > > >> > > > >> Great work. > > > >> > > > >> On Tue, Aug 27, [2019](tel:2019) at 3:08 PM Sergio Kef < > > > sergio...@gmail.com> wrote: > > > >> > > > >> > Amazing! congrats and thank you. > > > >> > > > > >> > > > > >> > On Tue, 27 Aug [2019](tel:2019) at 22:25, Jarek Potiuk < > > > jarek.pot...@polidea.com> > > > >> > wrote: > > > >> > > > > >> > > Hello everyone, > > > >> > > > > > >> > > After a long time in the making I merged "Breeze" environment > > which > > > is > > > >> a > > > >> > > swiss-knife of everything testing in Airflow. It should make it > > even > > > >> > easier > > > >> > > to contribute to Airflow (easier to test your changes locally > > while > > > >> > > development in general). > > > >> > > > > > >> > > There is a fairly comprehensive documentation in > > > >> > > https://github.com/apache/airflow/blob/master/BREEZE.rst that > you > > > can > > > >> > > follow to get started and start using it. > > > >> > > > > > >> > > Accidentally (or not :)) we have a workshop today in NYC ( > > > >> > > > > https://www.meetup.com/NYC-Apache-Airflow-Meetup/events/264141360/) > > > >> > where > > > >> > > I > > > >> > > will show breeze and have a number of new users using it - this > > > might > > > >> > > result in some incremental fixes/improvements. > > > >> > > > > > >> > > I expect some small teething problems over the next few days > and I > > > will > > > >> > be > > > >> > > watching all channels to help to solve them. Feel free to ping > me > > in > > > >> case > > > >> > > you try to use Breeze and have problems - slack is probably best > > in > > > >> such > > > >> > > case. > > > >> > > > > > >> > > J > > > >> > > > > > >> > > -- > > > >> > > > > > >> > > Jarek Potiuk > > > >> > > Polidea <https://www.polidea.com/> | Principal Software > Engineer > > > >> > > > > > >> > > M: [+48 660 796 129](tel:+48660796129) > > > <[+48660796129](tel:+48660796129)> > > > >> > > [image: Polidea] <https://www.polidea.com/> > > > >> > > > > > >> > > > > >> > > > >> > > > >> -- > > > >> > > > >> Chao-Han Tsai > > > >> > > > > > > > > -- > > > > > > > > Jarek Potiuk > > > > Polidea <https://www.polidea.com/> | Principal Software Engineer > > > > > > > > M: [+48 660 796 129](tel:+48660796129) > > <[+48660796129](tel:+48660796129)> > > > > [image: Polidea] <https://www.polidea.com/> > > > > > -- > > Jarek Potiuk > Polidea <https://www.polidea.com/> | Principal Software Engineer > > M: +48 660 796 129 <+48660796129> > [image: Polidea] <https://www.polidea.com/> >
