Jean-Paul Calderone b462d294a5 Try it in a working environment ... ?

2019-09-13 13:00:35 -04:00

..

config.yml

Try it in a working environment ... ?

2019-09-13 13:00:35 -04:00

create-virtualenv.sh

try telling the virtualenv to use pypy

2019-06-25 18:51:11 -04:00

Dockerfile.centos

Tell the rest of the platforms to keep using whatever "python2.7" is.

2019-06-25 19:07:00 -04:00

Dockerfile.debian

Tell the rest of the platforms to keep using whatever "python2.7" is.

2019-06-25 19:07:00 -04:00

Dockerfile.fedora

Tell the rest of the platforms to keep using whatever "python2.7" is.

2019-06-25 19:07:00 -04:00

Dockerfile.pypy

just pypy

2019-06-25 18:53:34 -04:00

Dockerfile.slackware

Tell the rest of the platforms to keep using whatever "python2.7" is.

2019-06-25 19:07:00 -04:00

Dockerfile.ubuntu

Tell the rest of the platforms to keep using whatever "python2.7" is.

2019-06-25 19:07:00 -04:00

fix-permissions.sh

Fix the permissions ... twice. Thanks, COPY.

2019-04-06 10:00:19 -04:00

populate-wheelhouse.sh

tor and i2p were already implied by test

2019-08-14 09:04:39 -04:00

prepare-image.sh

try telling the virtualenv to use pypy

2019-06-25 18:51:11 -04:00

run-build-locally.sh

Factor steps out for use by machine executer

2018-06-15 14:21:33 -04:00

run-tests.sh

Take a shot at really timing out the PyPy job.

2019-08-13 15:57:29 -04:00

secret-env-cipher

Re-generate with a new key because I leaked the old one

2019-04-03 14:18:19 -04:00

setup-virtualenv.sh

this was vaguely helpful sort of not really

2019-06-26 08:50:13 -04:00