-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Travis CI currently broken on some Python 3.5 environments #2779
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
The error is produced by tox-dev/tox#556 which is supposed to give more meaningful error messages fixing tox-dev/tox#121 - looks like here it covers the actual problem in a different way. Seems hard to report a sensible error from there. Just to make sure that this is not a tox regression: could you try this with tox 2.7? |
Hmmm strange, it fails with:
For some reason the pytest development version is showing up as |
I don't think it is related to Also from the logs in the description of travis-ci/travis-ci#8363, they are using the system's tox so it was not a new tox release which caused the problem. |
O.k. thanks - just wanted to be sure, as that error message is 2.8+ |
FWIW I had some similar issue with qutebrowser, and specifying |
@nicoddemus i suspect this is related to having collected enough commits since the last tag, that travis no longer includes a tag in the recent history without tag, the git describe is wrong |
This problem seems to be related to pyenv. It is mentioned in pyenv/pyenv-virtualenv#202. @gangefors points out a solution in their comment, which may help. Though I guess Travis should fix this. |
Thanks @bittner. Python 3.5 was being used in a few secondary test environments and those were failing, so we got around this by testing those secondary environments with Python 3.6 instead |
Fixed by #2785 |
@nicoddemus I think we need to reopen this bug, see https://travis-ci.org/pypa/virtualenv/jobs/283366066 I read it clear: it defines python3.6 as needed, but the installed version does not install python3.6 command so tox fails, translating to a total failure. I bet that over 95% of Python projects are using tox, and we cannot blame tox for not finding the CLI. |
@ssbarnea I'm not sure:
This should be |
See travis-ci/travis-ci#4990 (comment) and travis-ci/travis-ci#8363 (comment) for related follow-ups. The fix we applied in the behave-django project for that looks like this: python: 3.6
...
before_install:
# work around https://github.com/travis-ci/travis-ci/issues/8363
- pyenv global system 3.5
... Hope that helps. This is clearly a Travis image issue. They have to set up pyenv correctly. |
this still does not help, i have
|
@ysolovyov Does this reflect a problem re "Travis CI currently broken on some Python 3.5 environments"? I'm not sure. (What if you simply use |
For everyone landing here and looking for a solution to the Python/Travis issue: I recommend switching to tox-travis and the native Travis build matrix capabilities. That does away with all the ugly workarounds. See django-apptemplates for an implementation example (with an extensive build matrix and build stages). |
Uh oh!
There was an error while loading. Please reload this page.
Affects all
py35-*
environments,py35
works fine. So every tox environment which setsbasepython = python3.5
.Example failure:
Extracting the string literal from the message:
Which is the same error reported in travis-ci/travis-ci#8363.
Already tried this workaround but it failed with an strange problem:
The text was updated successfully, but these errors were encountered: