I'm now also having this problem in docker. I was able to build and run tests on a feature branch (TINKERPOP-1774) a few days ago but got the problems when I yesterday rebased on master. I just tried to find out which commits could have introduced the problem by going back to an older commit that worked but now it even fails for commits from over 2 weeks ago.
Am 31.07.2018 um 20:06 schrieb Stephen Mallette: > I don't know what I did to fix it but my local environment builds again > (updated all kinda things in no particular order....ugh, rage updating) - > docker is still hosed for me > > On Tue, Jul 31, 2018 at 11:08 AM Stephen Mallette <[email protected]> > wrote: > >> master >> >> On Tue, Jul 31, 2018 at 11:04 AM Robert Dale <[email protected]> wrote: >> >>> what branch are you building? >>> >>> Robert Dale >>> >>> >>> On Tue, Jul 31, 2018 at 11:03 AM Stephen Mallette <[email protected]> >>> wrote: >>> >>>> now 3.5 doesn't even work for me. docker doesn't work either :( >>>> >>>> On Tue, Jul 31, 2018 at 7:38 AM Stephen Mallette <[email protected]> >>>> wrote: >>>> >>>>> As of this morning I noticed that gremlinpython doesn't build anymore >>> on >>>>> python 3.4 - I get that awful: >>>>> >>>>>> Python.h: No such file or directory compilation terminated. >>>>> I upgrade to 3.5 and it works fine - anyone know why? and what does >>> this >>>>> mean? do we also need to manage 3.4 and 3.5 builds? can we stop >>> worrying >>>>> about 3.4 builds and support? >>>>> >>>>> >>>>> >>>>>
