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.

Sign up for GitHub

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

Jump to bottom

move over to using trusty #223

Merged
merged 7 commits into from
Mar 31, 2016
Merged

move over to using trusty #223

merged 7 commits into from
Mar 31, 2016

Conversation

psi29a
Copy link
Member

@psi29a psi29a commented Mar 28, 2016

No description provided.

@psi29a psi29a self-assigned this Mar 28, 2016
@psi29a psi29a added this to the v0.20.0 milestone Mar 28, 2016
@psi29a
Copy link
Member Author

psi29a commented Mar 28, 2016

This switches us away from docker to using a full VM using trusty. With all the things we do with WE, it is easier for us to do our job with a full VM.

@psi29a
Copy link
Member Author

psi29a commented Mar 29, 2016

Yay, python3.4 tests are testing...

but this came up, someone fix it! :P

  File "/home/travis/build/Mindwerks/worldengine/tests/serialization_test.py", line 9, in <module>
    from sets import Set
ImportError: No module named 'sets'

@coveralls
Copy link

Coverage Status

Changes Unknown when pulling b1f20be on trusty into * on master*.

@coveralls
Copy link

Coverage Status

Changes Unknown when pulling b1f20be on trusty into * on master*.

@coveralls
Copy link

Coverage Status

Changes Unknown when pulling b1f20be on trusty into * on master*.

@coveralls
Copy link

Coverage Status

Changes Unknown when pulling e5e8d81 on trusty into * on master*.

@coveralls
Copy link

Coverage Status

Changes Unknown when pulling 7954222 on trusty into * on master*.

@psi29a
Copy link
Member Author

psi29a commented Mar 30, 2016

Damn you pypy, so close!

ImportError: No module named google

@psi29a
Copy link
Member Author

psi29a commented Mar 30, 2016

Yay, tests are running!

@coveralls
Copy link

Coverage Status

Changes Unknown when pulling 077afc4 on trusty into * on master*.

@psi29a
Copy link
Member Author

psi29a commented Mar 30, 2016

They fail on pypy of course, this needs fixing.

h5py doesn't run on pypy.

@psi29a
Copy link
Member Author

psi29a commented Mar 30, 2016

@ftomassetti is this OK?

@coveralls
Copy link

Coverage Status

Changes Unknown when pulling 1488c82 on trusty into * on master*.

@coveralls
Copy link

Coverage Status

Changes Unknown when pulling bed3c37 on trusty into * on master*.

@psi29a
add Cython support and backported gdal
68b869c 
reorderingg

try 2

add a

say yes to everything

try forcing it again

try 3

try 4

try just gdal

what does aptitude tells us

try  not being quite?

possibly found the problem

try again with purge apt-get

try getting pypy inline

fix set problem for python3

try removing pypy then installing pypy from our repo

which pypy?

try 4

try to remove travis pypy

alles

try 5
@psi29a
try protobuf for pypy
803fb59
@psi29a
try pyflakes
dbbdc2d
@psi29a
try manifest, push py34 to active failure
6587080
@psi29a
promot pyflakes and manifest
f04feba
@coveralls
Copy link

Coverage Status

Changes Unknown when pulling f04feba on trusty into * on master*.

@psi29a
Copy link
Member Author

psi29a commented Mar 31, 2016

OK, merging in.

This means that any future updates have to pass python27, python34, pyflakes and manifest. This will helps keep WE stable.

@psi29a psi29a merged commit f0e6879 into master Mar 31, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees

@psi29a psi29a

Labels
technical
Projects
None yet
Milestone
v0.20.0
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@psi29a @coveralls