Skip to content

Start testing using GitHub Actions #19036

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

Merged
merged 8 commits into from
Dec 3, 2020
Merged

Conversation

QuLogic
Copy link
Member

@QuLogic QuLogic commented Nov 28, 2020

PR Summary

I don't think we've gotten back any reply from Travis yet. This ports Linux and macOS builds over to GitHub Actions; it takes roughly the same build time overall, though the queue might be shorter. I'm not entirely sure whether I used the right keys for caching or if it's really very effective yet.

I believe interactive backend tests are running though, so this should restore our code coverage results.

PR Checklist

  • Has pytest style unit tests (and pytest passes).
  • Is Flake 8 compliant (run flake8 on changed files to check).
  • [n/a] New features are documented, with examples if plot related.
  • Documentation is sphinx and numpydoc compliant (the docs should build without error).
  • Conforms to Matplotlib style conventions (install flake8-docstrings and run flake8 --docstring-convention=all).
  • [n/a] New features have an entry in doc/users/next_whats_new/ (follow instructions in README.rst there).
  • [n/a] API changes documented in doc/api/next_api_changes/ (follow instructions in README.rst there).

This is currently Linux-only, and skips caching and code coverage.
This was ignored on Travis for some time.
On Travis, NumPy was already installed and happened to be 1.16.4,
roundabout our desired minimum version. On GitHub Actions, NumPy is not
installed and gets installed later, since it was never specified in the
command with the pins.

Also, add minimum Pillow to the pins.
@QuLogic QuLogic added this to the v3.3.4 milestone Nov 28, 2020
@QuLogic
Copy link
Member Author

QuLogic commented Nov 28, 2020

Test coverage is up 0.81%, though library coverage is down 5% since the build on #17524? It looks like that drop may be because C code was added back into the count.

@QuLogic QuLogic force-pushed the actions branch 3 times, most recently from bb8d25a to 36b73cc Compare November 28, 2020 07:14
@jklymak
Copy link
Member

jklymak commented Dec 3, 2020

@QuLogic I'm fine with you self-merging this if we don't hear from @tacaswell. Looks good, but I'm not an expert on the testing infrastructure.

@tacaswell tacaswell merged commit 4d3b10e into matplotlib:master Dec 3, 2020
@QuLogic QuLogic deleted the actions branch December 3, 2020 19:54
@lumberbot-app
Copy link

lumberbot-app bot commented Dec 3, 2020

Owee, I'm MrMeeseeks, Look at me.

There seem to be a conflict, please backport manually. Here are approximate instructions:

  1. Checkout backport branch and update it.
$ git checkout v3.3.x
$ git pull
  1. Cherry pick the first parent branch of the this PR on top of the older branch:
$ git cherry-pick -m1 4d3b10ed75fd0d89a5a7d3f54a7e69cc643216d6
  1. You will likely have some merge/cherry-pick conflict here, fix them and commit:
$ git commit -am 'Backport PR #19036: Start testing using GitHub Actions'
  1. Push to a named branch :
git push YOURFORK v3.3.x:auto-backport-of-pr-19036-on-v3.3.x
  1. Create a PR against branch v3.3.x, I would have named this PR:

"Backport PR #19036 on branch v3.3.x"

And apply the correct labels and milestones.

Congratulation you did some good work ! Hopefully your backport PR will be tested by the continuous integration and merged soon!

If these instruction are inaccurate, feel free to suggest an improvement.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants