DOC: fixing examples that caused remote test failures #2721
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov Report
@@ Coverage Diff @@
## main #2721 +/- ##
=======================================
Coverage 65.74% 65.74%
=======================================
Files 233 233
Lines 17844 17844
=======================================
Hits 11732 11732
Misses 6112 6112 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
keflavich
approved these changes
Apr 28, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This should fix most examples in the documentation. The remaining failures are due to genuine upstream problems and all have their tracking issues opened.
Besides these, there are a few more remote-data tests failing in the main test suite, I leave those for a future PR.