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

How to properly run the tests? #99

Closed
svenstaro opened this Issue Dec 13, 2014 · 5 comments

Comments

Projects
None yet
2 participants
@svenstaro
Contributor

svenstaro commented Dec 13, 2014

Running tox locally for my python version yields 18 errors as compared to running tox on travis. What is different running tox locally as compared to travis that I would get errors here? How do I run the tests locally?

@sloria

This comment has been minimized.

Member

sloria commented Dec 13, 2014

@svenstaro Do you have each of the interpreters installed locally? Also, what errors are you seeing?

@sloria sloria added the question label Dec 13, 2014

@svenstaro

This comment has been minimized.

Contributor

svenstaro commented Dec 13, 2014

Running

$ tox --skip-missing-interpreters &> /tmp/log

gives me this: https://gist.github.com/ca7bb1b6a8c339052e27

@svenstaro

This comment has been minimized.

Contributor

svenstaro commented Dec 13, 2014

It seems like it's pulling in older versions of marshmallow which are obviously not compatible. I wonder why it does that since obviously we want to be testing the local version of marshmallow.

@svenstaro

This comment has been minimized.

Contributor

svenstaro commented Dec 13, 2014

Ah, my problem is that marshmallow does not expect the virtualenv to be in the same dir as the git repo. This kind of sucks for me, because I always put my env there, as in marshmallow/env. Would you mind if I fixed marshmallow to disregard the popular "env" name for the virtualenv inside the git root?

svenstaro added a commit to svenstaro/marshmallow that referenced this issue Dec 13, 2014

@svenstaro

This comment has been minimized.

Contributor

svenstaro commented Dec 13, 2014

I made a pr to fix the specific issues that I experienced here.

@sloria sloria closed this in ee6f605 Dec 20, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment