Skip to content
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

Travis fails to install pymongo under PyPy 1.2 #12

Closed
neithere opened this issue Dec 11, 2013 · 2 comments
Closed

Travis fails to install pymongo under PyPy 1.2 #12

neithere opened this issue Dec 11, 2013 · 2 comments
Assignees
Milestone

Comments

@neithere
Copy link
Owner

Everything is perfect locally on PyPy 1.2.1 but an obscure error in Travis (e.g. https://travis-ci.org/neithere/monk/jobs/15173648):

$ python --version
Python 2.7.3 (f3423a62cd09, Nov 12 2013, 16:09:06)
[PyPy 2.2.0 with GCC 4.6.3]
$ pip --version
pip 1.4.1 from /home/travis/virtualenv/pypy/site-packages (python 2.7)
$ pip install -r requirements/devel.txt --use-mirrors
Downloading/unpacking pymongo==2.6.3 (from -r requirements/basic.txt (line 1))
RPython traceback:
...
Fatal RPython error: KeyError
/home/travis/build.sh: line 147: 1273 Aborted pip install -r requirements/devel.txt --use-mirrors
The command "pip install -r requirements/devel.txt --use-mirrors" failed and exited with 134 during install.
Your build has been stopped.

Possible solutions:

  • wait for a more recent version of PyPy
    • and have failed builds all the time? no, thanks.
  • contact Travis team and/or try installing PyPy 1.2.0 locally and dig into that stuff
    • don't care & no time

Possible workarounds:

  • drop support for PyPy
    • despite 90% the core of the library works fine? bad idea.
  • do not test the MongoDB extension under PyPy
    • how to setup the pypy env in Travis? doesn't seem to support per-env configuration like tox
  • do not test the MongoDB extension at all in Travis CI
    • still can test it locally, OK
    • monk.mongomonk.ext.mongo
    • requirements/basic.txtrequirements/ext.txt (skip it in CI)
  • only test PyPy locally; do not include it in Travis
    • this is the simplest way.
@neithere
Copy link
Owner Author

Workaround implemented, closing. May reopen if something changes on Travis side.

malept added a commit to malept/snakemine that referenced this issue Dec 19, 2013
It currently fails and I don't know why:
https://travis-ci.org/malept/snakemine/jobs/15687631

It appears that other people have this problem:
neithere/monk#12
@lopuhin
Copy link

lopuhin commented Feb 15, 2014

Found the same problem, filed https://bugs.pypy.org/issue1694

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants