All I can think of is that there must be some strange bug in the devtools toolchain we're using, possibly triggered by some kernel versions and not others (since that's the main thing that docker containers fail to isolate processes from).
If that's right though then I'm not sure it's worth trying to track down the exact details -- we're using the devtools-2 release, while upstream is on devtools-6. And the only reason we're still using this toolchain is that it's the last version to support CentOS 5, which is EOLed, and we'll be abandoning CentOS 5 and devtools-2 as soon as someone has a chance to put together manylinux2. On Wed, Aug 23, 2017 at 5:59 AM, Lele Gaifax <l...@metapensiero.it> wrote: > Hi all, > > the (interim?) solution I found is using a different CI service to build the > Python 3.6 wheels. This[1] seems to prove that there something strange going > on in the Travis CI service, as the very same source, compiled within the same > manylinux1 Docker image, does not exhibit the problem I explained in this > thread. > > Thanks&bye, lele. > > [1] https://gitlab.com/metapensiero/python-rapidjson/-/jobs/30065688 > -- > nickname: Lele Gaifax | Quando vivrò di quello che ho pensato ieri > real: Emanuele Gaifas | comincerò ad aver paura di chi mi copia. > l...@metapensiero.it | -- Fortunato Depero, 1929. -- Nathaniel J. Smith -- https://vorpus.org _______________________________________________ Wheel-builders mailing list Wheel-builders@python.org https://mail.python.org/mailman/listinfo/wheel-builders
