bencher4 fialing own py3 builds
Own nightly builds on p3.5 are failing numerous cpyext tests. The problem seems to be related to the _cffi_backend module somehow hitting an assert at import, but I cannot reproduce the problem locally. I have tried many things on the unicode-utf8-py3 branch to solve the problem, but to no avail. See the last 3 or 4 commits on that branch. Any help would be greatly appreciated. Perhaps we should retire bencher4 and find another build machine, one that we can control a bit more? Matti
Hi Matti, On 27 August 2018 at 18:38, Matti Picus <matti.picus@gmail.com> wrote:
It reproduces if we run both test_buffer and test_translate together (py.test test_buffer.py test_translate.py).
Perhaps we should retire bencher4 and find another build machine, one that we can control a bit more?
It wouldn't be a bad idea. Note that we should check again if it would be OK to reinstall bencher4 in a way that we fully control (including giving accounts to people at our discretion), which would save us the trouble of looking elsewhere. But maybe it still isn't possible to do that... A bientôt, Armin.
On Mon, Aug 27, 2018 at 6:38 PM Matti Picus <matti.picus@gmail.com> wrote:
. Perhaps we should retire bencher4 and find another build machine, one that we can control a bit more
another thing we could try to have more repeatable builds is to use docker containers; for example, some time ago I used this approach to debug an issue which appeared only on 32bit builds: https://github.com/antocuni/dockerpypy This is orthogonal to using a machine on which we have more control of course. Probably the best is to have full control on the machine AND use docker containers :)
Hi Matti, On 27 August 2018 at 18:38, Matti Picus <matti.picus@gmail.com> wrote:
It reproduces if we run both test_buffer and test_translate together (py.test test_buffer.py test_translate.py).
Perhaps we should retire bencher4 and find another build machine, one that we can control a bit more?
It wouldn't be a bad idea. Note that we should check again if it would be OK to reinstall bencher4 in a way that we fully control (including giving accounts to people at our discretion), which would save us the trouble of looking elsewhere. But maybe it still isn't possible to do that... A bientôt, Armin.
On Mon, Aug 27, 2018 at 6:38 PM Matti Picus <matti.picus@gmail.com> wrote:
. Perhaps we should retire bencher4 and find another build machine, one that we can control a bit more
another thing we could try to have more repeatable builds is to use docker containers; for example, some time ago I used this approach to debug an issue which appeared only on 32bit builds: https://github.com/antocuni/dockerpypy This is orthogonal to using a machine on which we have more control of course. Probably the best is to have full control on the machine AND use docker containers :)
participants (3)
-
Antonio Cuni -
Armin Rigo -
Matti Picus