-
Notifications
You must be signed in to change notification settings - Fork 390
TST: Using GitHub Actions for CI testing #1691
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
Conversation
fa4ad57 to
f88cc41
Compare
|
Coveralls on GitHub reports 85%, but on TravisCI it reports 90% which is the reason for the drop once I removed the TravisCI builds. |
|
Was that a bug or did we suddenly stop running some important config? Or do we have code we can remove because we're not supporting some combination we were hacking around? |
|
It looks like we are now testing a new file: |
f88cc41 to
5f2528e
Compare
Adding the yaml configuration file to use GitHub Actions for testing.
Removing TravisCI due to the flaky builds sometimes reporting failures.
aef68e2 to
f78d6ef
Compare
Adding source distribution build and PyPI release actions.
f78d6ef to
bbcf26b
Compare
QuLogic
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Best to just start testing with it.
Adding the yaml configuration file to use GitHub Actions for testing.
Rationale
TravisCI may no longer be supporting open-source the way it previously did with free resources.
Implications
New test integration platform and needing to learn the GitHub Actions yaml language and platform.