ci: smoke test with/out optional dependencies, mark more tests

[wpbonelli]

• close Testing without optional dependencies #1905
  • run smoke tests with all, some and no optional dependencies on nightly schedule
  • in partial dependency availability case, remove 3 randomly chosen dependencies every day
• mark some tests requiring optional dependencies
• only check crs deprecations if pyproj available

[codecov]

Codecov Report

Merging #1918 (424d814) into develop (ed3a0cd) will increase coverage by 0.0%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           develop   #1918     +/-   ##
=========================================
  Coverage     72.6%   72.6%             
=========================================
  Files          257     257             
  Lines        56210   57585   +1375     
=========================================
+ Hits         40835   41835   +1000     
- Misses       15375   15750    +375     

see 72 files with indirect coverage changes

[mwtoews]

Looks good so far. It adds about 5 mins to the smoke tests. It seems the smoke test does not upload it's coverage, it probably should to see the changes.

[wpbonelli]

@mwtoews I wonder if it may be worth randomizing the choice of dependencies to test without. I added a mechanism to do so and moved optional dependency testing to nightly schedule. Let me know if this seems unreasonable.

[mwtoews]

I like the idea to randomize optional deps, as there are potential combinations that may cause issues. We can see how it goes. If it becomes too much of a maintenance burden, then the randomization can be disabled. And I'd agree it doesn't make sense to upload an unstable coverage report.

[mwtoews]

It's probably better to keep the smoke tests short, so moving optional tests to their own workflow seems the right way. However, I don't see any tests from optional.yml.

[wpbonelli]

I put optional.yml on a nightly schedule and set to choose a different random 3 dependencies every day, hopefully that should not be too burdensome to stay on top of and we also avoid bloating regular CI.

[mwtoews]

That's why it's not triggered with pull requests. A schedule should work well.

[mwtoews]

Thanks!