Make requirements, test requirements more explicit; add `[test]` pip extra
(factored out of #612)
@ryan-williams If you can address the comment in the PR, we can merge this in.
just rebased and addressed the comment, gonna try to resuscitate a few of these, thanks for your patience
Just rebased this, not sure what this failure in "R tests on macos-latest" is about:
==> Pouring checkbashisms--2.21.7.all.bottle.tar.gz
installer: Package name is gfortran
installer: Installing at base path /
installer: The install was successful.
/usr/bin/sudo hdiutil detach /Volumes/gfortran-8.2-Mojave
hdiutil: couldn't unmount "disk2" - Resource busy
Error: Failed to get R 4.1.1: Failed to get R 4.1.1: Failed to umount /Volumes/gfortran-8.2-Mojave: Error: The process '/usr/bin/sudo' failed with exit code 16
🍺 /usr/local/Cellar/checkbashisms/2.21.7: 6 files, 72.2KB
I think the above was a spurious failure, fwiw; I tweaked this PR once more to alphabetize requirements-test.txt, mostly just to get the CI to run again, and it passed.
So, this should be ready for another look if anyone has time.
thanks @savingoyal 🙏 looks like this is good to merge?
Testing[44] @ 5da5e674c9a4f1cca2acbb4383799da09e7387c4
Testing[44] @ 5da5e674c9a4f1cca2acbb4383799da09e7387c4
Testing[44] had 3 FAILURES.
Not sure how to parse "Testing[44] had 3 FAILURES." above. Where does that CI run?
@ryan-williams : I am using your PR as a guinea pig for some tests we run internally. The CI is not accessible so don't worry about the message (it's a good comment though -- I will modify the message to indicate that the message can be ignored mostly). As you can see, it's not yet fully working (it worked fine when using branches from this repo but not so much from a fork (yet)).