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

Move tests to GitHub Actions #36

Merged
merged 7 commits into from
Mar 19, 2021
Merged

Move tests to GitHub Actions #36

merged 7 commits into from
Mar 19, 2021

Conversation

jrbourbeau
Copy link
Contributor

This PR takes a crack at moving the current CI builds that run on Travis CI to GitHub Actions

xref #32

@@ -0,0 +1,15 @@
name: Cancel
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This workflow will cancel duplicate CI builds. For example, when rapidly pushing commits to a PR, if there are CI builds still running from an older commit they will be cancelled

Comment on lines +11 to +12
os: [windows-latest, ubuntu-latest, macos-latest]
python-version: [3.6, 3.7, 3.8, 3.9]
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I went ahead and added a Python 3.9 build as well as windows and macOS builds

Comment on lines 5 to 10
# Dask 2021.3.0 introduced a regression which broke xhistogram.
# This regression should be fixed in the next Dask release and we
# should remove the dask version pinning below.
# see https://github.com/dask/dask/pull/7391
# and https://github.com/xgcm/xhistogram/issues/27
- dask!=2021.3.0
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

From #34

# see https://github.com/dask/dask/pull/7391
# and https://github.com/xgcm/xhistogram/issues/27
- dask!=2021.3.0
- numpy=1.16
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Instead of testing NumPy 1.16 and 1.17 on Python 3.6, the changes here test NumPy 1.16 on Python 3.6 and NumPy 1.17 on Python 3.7. My guess is this isn't a big deal, but let me know if we should changes what's here

@codecov
Copy link

codecov bot commented Mar 18, 2021

Codecov Report

Merging #36 (77bc8e3) into master (2c221ed) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master      #36   +/-   ##
=======================================
  Coverage   94.41%   94.41%           
=======================================
  Files           3        3           
  Lines         215      215           
  Branches       58       58           
=======================================
  Hits          203      203           
  Misses          8        8           
  Partials        4        4           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2c221ed...77bc8e3. Read the comment docs.

@rabernat
Copy link
Contributor

This is amazing @jrbourbeau! You're like an open source superhero! 🦸

Is merging #34 what caused the conflicts? I'm happy to revert that, since this supersedes it.

@jrbourbeau
Copy link
Contributor Author

No worries, just needed to merge master. I think this should be good to go now

@rabernat rabernat merged commit bb1fa23 into xgcm:master Mar 19, 2021
@jrbourbeau jrbourbeau deleted the gha-tests branch March 19, 2021 14:24
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.

2 participants