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

Update & fix travis build/test process #458

Open
suntzu86 opened this issue Apr 15, 2016 · 0 comments
Open

Update & fix travis build/test process #458

suntzu86 opened this issue Apr 15, 2016 · 0 comments
Assignees

Comments

@suntzu86
Copy link
Contributor

suntzu86 commented Apr 15, 2016

Our tests/build is failing on Travis for unknown reasons (e.g., import errors from scipy/numpy internals). My guess is due to dependency on out of date packages (or too new packages) or even old linux version.

We should get this back in a working state.

While we're here, the MOE build process on travis takes a ridiculously long time due to building numpy & scipy from scratch. I let this slide in the past and relied solely on local testing due to it being so slow... which kind of circumvents the point.

Some more things to do:

  • build requirements.txt automatically from setup.py. this should be done by constructing a temporary virtualenv, installing moe, and freezing
    • this should be a "requirements" target in the makefile. depends on setup.py. test should depend on it.
  • use wheels, pypi as much as possible. taking some 30min to build MOE is nuts
  • consider venv-update and/or pip-faster: https://github.com/Yelp/venv-update (wont help with build times, but still handy for developers)
    • this makes virtualenvs a natural/automatic part of working with MOE (no more people skipping that step)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant