Sure thing. Will do.
On Sat, Feb 1, 2020 at 12:10 AM Saisai Shao <sai.sai.s...@gmail.com> wrote: > > Thanks for the fix. Would you please create a separate PR about this issue? > It should be enough to create a "minor" GH PR directly without JIRA issue. > > Best regards, > Saisai > > Wing Yew Poon <wyp...@cloudera.com.invalid> 于2020年1月31日周五 上午6:33写道： > > > I updated python-api/setup.py to include > > > > 'mock~=3.0.5', > > > > in requirements. > > That got the CI passing on my PR, > > https://github.com/apache/incubator-livy/pull/275. > > > > On Thu, Jan 30, 2020 at 12:02 PM Wing Yew Poon <wyp...@cloudera.com> > > wrote: > > > > > > Resending ... > > > > > > On Wed, Jan 29, 2020 at 9:26 PM Wing Yew Poon <wyp...@cloudera.com> > > wrote: > > > > > > > > Hi, > > > > I ran into a CI failure in the python-api unit tests. (See > > > > https://travis-ci.org/apache/incubator-livy/builds/643685980.) > > > > From what I can tell, something is pulling in mock 4.0.0b1 (in > > > > pre-release according to https://pypi.org/project/mock/#history) > > > > instead of 3.0.5, and a method signature has changed in mock.py. > > > > Any guidance on how I can get around this? > > > > Thanks, > > > > Wing Yew > > > > > > From https://pypi.org/project/mock/#history it appears that mock > > > 4.0.0b1 showed up Jan 29, 2020, which is why this failure only just > > > started happening. > >
