Container-based Trusty: pypy and pypy3 are not installed; attempting download

[jwilk]

pypy3 builds in container-based Trusty fail with:

pypy3 is not installed; attempting download
bzip2: (stdin) is not a bzip2 file.
tar: Child returned status 2
tar: Error is not recoverable: exiting now

The command "sudo tar xjf -.tar.bz2 --directory /" failed and exited with 2 during .

Full build log: https://travis-ci.org/jwilk/anorack/jobs/175361126

[flacjacket]

Just to bump this, I have the same problem with both pypy and pypy3 in the container trusty beta.

[BanzaiMan]

Hello. Does pypy work?

[BanzaiMan]

It does not. https://travis-ci.org/BanzaiMan/travis_production_test/jobs/195343264

[asottile]

Here's a workaround we're using:

https://github.com/Yelp/venv-update/blob/19c18924afb55d23333150bf3bdb66da995b046f/.travis.yml#L12

[BanzaiMan]

Actually, I am thinking of reverting this. It is difficult to guess what version pypy should point to.

pypy and pypy3 do not match up with python's naming convention, and having to account for it is not a good idea.

[ssokolow]

I'd be happy with anything that lets me test "some reasonably recent PyPy and some reasonably recent PyPy3" in addition to the various CPython versions.

[asottile]

Even the cpython names aren't terribly well defined either. travis-ci regularly upgrades patch versions which break cached virtualenvs (such as 3.6.0 -> 3.6.1)

At least for pypy, it's still going to target "python2.7" -- version updates there (at least in my mind) are akin to the same patch versions that happen all the time with cpython versions in travis-ci

[BanzaiMan]

I'm closing this. Due to the naming ambiguity. There will be other means of specifying PyPy versions consistently.

[asottile]

I'm not sure this should be closed, it's a clear regression from the precise images

[BanzaiMan]

pypy and pypy3 are not names we can support consistently going forward.

Please use pypy-x.y.

[BanzaiMan]

We'll update the documentation shortly.

[asottile]

python: 3.6 also isn't a consistent name to support either and the docs reflect nothing of this change (and this will break lots of builds)

[BanzaiMan]

It is true. But 3.6.0 is a consistent name with respect to the definitions in https://github.com/pyenv/pyenv/tree/master/plugins/python-build/share/python-build, and we can infer 3.6 to mean "the latest MAJOR.MINOR" release of "3.6.x".

pypy-x.y is similar, but pypy is not.

[asottile]

Why can't pypy refer to the latest release of pypy? Since all pypy target the "python 2.7 api" they're all pretty compatible

[BanzaiMan]

Hmm. Maybe. I'll give it more thought. Thanks.

[BanzaiMan]

pypy and pypy3 should now work on all infrastructures. If you continue to see the problem, do let us know.

[asottile]

@BanzaiMan still seeing issues: https://travis-ci.org/pre-commit/pre-commit-hooks/jobs/257658233

[asottile]

(fwiw, I reported this earlier in #8081 but it was closed without fix)

[BanzaiMan]

The python: pypy3 still does not work.

[asottile]

@BanzaiMan my link is pypy missing in the default python environment (it was present in the precise images -- this will likely break lots of python projects as they get upgraded)

[BanzaiMan]

@asottile Having python: pypy and python: pypy3 is different from those runtimes pre-installed. tox requires pre-installation.

[asottile]

@BanzaiMan correct. For dist: precise, both pypy and pypy3 are preinstalled. Neither are in dist: trusty which is a regression that will likely break lots of builds as they get automatically migrated to trusty. This is what I was getting at in #8081

[BanzaiMan]

@asottile As I mentioned in #8081, we will continue that issue with #8160.

[asottile]

#8160 is a different issue. Their configuration has python: pypy3: https://travis-ci.org/MartyMacGyver/DirTreeDigest/jobs/257614214/config

[BanzaiMan]

I've repackaged pypy3.5-5.8.0 and pypy2.7-5.8.0 archives, so that python: pypy3 and python: pypy (respectively) work.

[BanzaiMan]

@asottile You're right about that. My apologies.

[asottile]

@BanzaiMan could you please reopen #8081 until it is fixed?

[KOLANICH]

There are problems wjth the following URIs:

https://s3.amazonaws.com/travis-python-archives/binaries/ubuntu/14.04/x86_64/python-3.7.tar.bz2
https://s3.amazonaws.com/travis-python-archives/binaries/ubuntu/14.04/x86_64/pypy3-nightly.tar.bz2
https://s3.amazonaws.com/travis-python-archives/binaries/osx/10.11/x86_64/python-3.4.tar.bz2
https://s3.amazonaws.com/travis-python-archives/binaries/osx/10.11/x86_64/python-3.5.tar.bz2
https://s3.amazonaws.com/travis-python-archives/binaries/osx/10.11/x86_64/python-3.6.tar.bz2
https://s3.amazonaws.com/travis-python-archives/binaries/osx/10.11/x86_64/pypy3.tar.bz2
https://s3.amazonaws.com/travis-python-archives/binaries/osx/10.11/x86_64/pypy3-nightly.tar.bz2

[adamcharnock]

@BanzaiMan, it seems that the following URL is once again unavailable:

https://s3.amazonaws.com/travis-python-archives/binaries/ubuntu/14.04/x86_64/python-3.7.tar.bz2