-
Notifications
You must be signed in to change notification settings - Fork 31
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
Run tox in travis instead of Docker #219
Conversation
Happy to use travis for the testing or even move to GitHub actions, but I'd like to keep the dockerfile for testing. (Certainly having the tox.ini tied to the dockerfile has annoyed me in the past, but let's find a way to have both) |
Do you want to keep the existing |
For the target of |
0ed6ac7
to
d25fdb8
Compare
I've force pushed to revert the deletion of the Dockerfile, we can discuss that separately #221 |
Docker output 👍
Native (OSX) with this setup:
gives:
but not it does require removing the manylinux wheel which meant I had to run with Otherwise, 👍 |
Following @joshmoore example I also tried, with less success:
|
Is tox working for you on omero-py? |
I also got the same error when running in my |
The manylinux line needs an exception so that it doesn't run on Mac. |
Hmm - Running
|
a769ab7
to
b741354
Compare
Can you try now? |
Yep - looks good 👍
|
So probably the only downside is that the Docker is no longer being built. Assuming that will be handled via #221, merging. |
Are there any advantages to running the tests with tox and Docker? To me it seems to make things more difficult, especially if we want to start testing multiple Python versions.
Extracted from #218