Switched from Travis to Github Actions

[andamian]

#244

Few observations:

• I've tried to follow the astropy model and therefore I've moved most of the environment setup to tox. Now tests can be easily reproduced locally.
• I've removed test cases based on numpy version combinations. pyvo uses a very small subset of numpy functionality hence astropy it's the better place to deal with version dependencies.
• The matrix might be a bit of an overkill with running the regression tests on every OS. I've noticed they tend to be slower on Windows and MacOS so might want to skip those.
• I haven't received any feedback on the publish job so it's not included here.
• Can one of the admins enable Actions on this repo and protect master with it - thanks. In the meantime, the results of actions could be observed in my fork.

Looking forward to receiving your comments.

[cbanek]

Looks very reasonable to me! Of course, the proof is in the running. Thanks for handling this!

[cbanek]

Does this mean we won't have coverage per PR anymore?

[andamian]

If you refer to the needs: coverage line this is just how the dependencies are expressed, e.g. coverage needs to successfully run first. As a matter of fact, coverage is only needed for PRs and it should be run for new releases. Something to fine tune later maybe.

[tomdonaldson]

I agree with @cbanek. Much appreciation for doing this work, and it does seem reasonable. I'm not worried about it being perfect right now since it doesn't affect pyvo functionality. As this gets more exercise moving forward, we can make needed/desired changes then.

[bsipocz]

I've removed test cases based on numpy version combinations. pyvo uses a very small subset of numpy functionality hence astropy it's the better place to deal with version dependencies.

totally reasonable, here I would just test with a range of astropy versions that are supported. (the most critical one is to have a combination for the oldest supported versions of dependencies, and one for the latest and greatest one)

The matrix might be a bit of an overkill with running the regression tests on every OS. I've noticed they tend to be slower on Windows and MacOS so might want to skip those.

fully agree. There is also the option to run a more detailed matrix from cron, but I don't feel that would be necessary either.

I haven't received any feedback on the publish job so it's not included here.

haven't yet figured it out for astroquery, sorry about that

Can one of the admins enable Actions on this repo and protect master with it - thanks. In the meantime, the results of actions could be observed in my fork.

It all looks to be enabled to me, but it will only run once the config files land in master, there is no way to test this in this PR (doing it directly on the branch on your fork can be a way, but I would think merging this and ironing out any potential issues in a follow-up is more than reasonable)

[bsipocz]

some comments for follow-up PRs, I would think merge this now and adjust later.

[bsipocz]

at some point running tests with setup.py can be retired, too, in favour of directly running pytest, but it's OK for now.

[bsipocz]

astropy 4.0, 4.1, and now 4.2 are also out, so this could use some update

[andamian]

Thanks. I'll merge it now and follow up with another one after everyone gets an idea of how it works.