Skip to content

Conversation

@felixdivo
Copy link
Collaborator

I added some more test platforms, most notably OSX tests for Python 3.6-dev, 3.7-dev and nighly. I also changed the Travis CI file to allow nightly Python builds to fail, but they are still tested and the results can be viewed.

Now, there are generally more comments in .travis.yml. For someone reviewing this, I would kindly ask them to read the comments in there and decide whether the chosen approach for OSX support & disallowing/allwoing dev/nightly builds was OK.

For the failing tests, see #243. I think they are not directly connected to the changes in this PR.

@felixdivo
Copy link
Collaborator Author

"Squash and merge" would probably be best for this since I needed many small commits to test the Travis CI script.

@felixdivo felixdivo requested a review from hardbyte February 10, 2018 17:08
@christiansandberg
Copy link
Collaborator

The default cyclic transmission is a bit problematic since it depends on available CPU resources to work reliably. Travis' OS X machines are probably choked.

@felixdivo
Copy link
Collaborator Author

felixdivo commented Feb 12, 2018

That's true, but it's not about this issue. BTW: The problem exists on Linux as well, as linked in #243.

@hardbyte hardbyte merged commit 7afacef into develop Feb 13, 2018
@hardbyte hardbyte deleted the more-tests branch February 13, 2018 21:52
@hardbyte hardbyte added this to the 2.1 Release milestone Feb 18, 2018
boris-wenzlaff pushed a commit to boris-wenzlaff/python-can that referenced this pull request Mar 23, 2018
* added osx to travis test targets
* Improve test failure messages
* Make timing tests more forgiving for travis
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

Successfully merging this pull request may close these issues.

4 participants