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

macOS and Windows environments on travis tests #28

Closed
james-large opened this issue Feb 26, 2020 · 1 comment · Fixed by #50
Closed

macOS and Windows environments on travis tests #28

james-large opened this issue Feb 26, 2020 · 1 comment · Fixed by #50
Labels
build / ci Continuous integration, unit testing & package distribution enhancement New feature or request

Comments

@james-large
Copy link
Contributor

For completeness, these test envs should be added too, however they would be non-trivial.

Versioning between operating systems is of course one issue. See here, as of writing macOS supports up to tf 2.0, but not 2.1 (on cpu, that is)

Windows should be able to support any version, but windows envs on travis are less feature-rich. It should be possible in principle, https://docs.travis-ci.com/user/reference/windows/

Alternatively, docker/equivalent environments could be setup and used within the travis tests to alleviate some of these problems. #27

Investigation into other open-source projects and how they do multi-os tests would be good

@james-large james-large added the enhancement New feature or request label Feb 26, 2020
@mloning mloning linked a pull request Apr 24, 2020 that will close this issue
2 tasks
@mloning mloning added the build / ci Continuous integration, unit testing & package distribution label May 8, 2020
@mloning
Copy link
Contributor

mloning commented May 8, 2020

Closed by #50

@mloning mloning closed this as completed May 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
build / ci Continuous integration, unit testing & package distribution enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants