[prev in list] [next in list] [prev in thread] [next in thread] 

List:       pypy-dev
Subject:    Re: [pypy-dev] bencher4 fialing own py3 builds
From:       Antonio Cuni <anto.cuni () gmail ! com>
Date:       2018-08-29 10:08:40
Message-ID: CAHPg78xv3=-++Xta8iAqPJtu7bWigWCHxBZbxEXE0SJ+u2LcnQ () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


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 :)

[Attachment #5 (text/html)]

<div dir="ltr"><div class="gmail_default" style="font-size:small">On Mon, Aug 27, \
2018 at 6:38 PM Matti Picus &lt;<a \
href="mailto:matti.picus@gmail.com">matti.picus@gmail.com</a>&gt; \
wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" \
style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex">. Perhaps we should retire bencher4 and find <br> \
another build machine, one that we can control a bit \
more</blockquote><div><br></div><div class="gmail_default" \
style="font-size:small">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:  <a \
href="https://github.com/antocuni/dockerpypy">https://github.com/antocuni/dockerpypy</a></div><div \
class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" \
style="font-size:small">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 :)</div></div></div>



_______________________________________________
pypy-dev mailing list
pypy-dev@python.org
https://mail.python.org/mailman/listinfo/pypy-dev


[prev in list] [next in list] [prev in thread] [next in thread]