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
Updating astropy-helpers to latest v2.0dev #6140
Conversation
09ebe26
to
4aa15db
Compare
2dab050
to
deef1c3
Compare
I'm not sure where is this undefined reference: The other warnings seem to be due to #4927 and thus will need to be fixed before the release. |
9b0a13d
to
fc6876c
Compare
fc6876c
to
27d0289
Compare
See sphinx-gallery/sphinx-gallery#255 for potential fix to the See astropy/astropy-data#26 for potential fix to the "Invalid 'BLANK' keyword" and "[LON/LAT]POLE2" in test log. (The proper way is to fix the data like I did, but if desperate, we now know what files cause these warnings, so can just track them down in the doc and silence the warnings.) See #6261 for potential fix to the
|
3d927e4
to
523a45f
Compare
Update for today: I removed my Ripley ref fix in favor of #6252 and rebased against latest master. (Sorry if I messed up the commit history...) |
@pllim - Don't worry about the commit history here, at the end of the day all the sphinx fixing commit should go into another PR, and this will only contain the astropy helpers update. But currently it's more convenient to test the former here, too as it needs the fixes from the helpers. |
@bsipocz , I hunted down the R115 warning, which is caused by wrong EDIT: For completeness, here is why it failed -- Reference cannot be in the first sentence, because when the module members TOC is generated, it tries to find the link that is in another page. (Something like that.) |
f680c3f
to
8168ae8
Compare
8168ae8
to
8b17a35
Compare
Update: I understand all the warnings now. Some are fixed here and some need external fixes. See #6140 (comment) |
@pllim - I've restarted the build now that the data file updates are merged. |
OMG it's green -- https://travis-ci.org/astropy/astropy/jobs/245655085 |
@bsipocz , you said the warning fixes should go in a different PR, but how? Are you going to cherry pick, or am I going to copy-and-paste the code into a new branch? |
.travis.yml
Outdated
@@ -144,6 +145,10 @@ install: | |||
- git clone git://github.com/astropy/ci-helpers.git | |||
- source ci-helpers/travis/setup_conda.sh | |||
|
|||
# Use this until https://github.com/sphinx-gallery/sphinx-gallery/pull/255 | |||
# is merged. | |||
- if [[ $SETUP_CMD == *build_docs* ]]; then pip -q install git+https://github.com/pllim/sphinx-gallery.git@stat-iter-deprec#egg=sphinx-gallery; fi |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note: This fixes the deprecation warning from Sphinx for sure. This hack will have to stay until my PR over at sphinx-gallery
gets merged, which I have no control over. But feel free to suggest a more elegant hack.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
does this warning cause a sphinx failure? if it does, could we maybe use the functionality of #6223 to turn it off so not just travis, but local builds would pass without issues?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually I am not sure. The test log reported failure and the total number of warnings but did not say which ones counted. Should I undo this and see what happens?
@pllim - I planned to cherry-pick them, but let's have the helpers RC out first, so we don't just do a blind merge, but test it before that. |
Okay, I'll leave you to your magic then. 😄 |
bc4782e
to
2ffd31b
Compare
OK, so now I've removed all the sphinx fixes from here to #6272, and this PR goes back to test the helpers RC only. |
2ffd31b
to
769cd58
Compare
Merging this now with the helpers 2.0rc1, but we need to update to 2.0 before the release. |
@bsipocz - thanks for merging this! However, I noticed the following issue with this pull request:
Would it be possible to fix this? Thanks! If you believe the above to be incorrect (which I - @astrobot - very much doubt) you can ping @astrofrog |
Updating astropy-helpers to latest v2.0dev
DO NOT MERGE! This is a testing, placeholder PR until ah is released.EDIT: this PR now contains only the helpers update to 2.0rc1 and related docs changes. Can be merged once CI passes.
There were quite a few changes in the helpers, and thus I see only benefits of trying to test against the latest dev branch well before the feature freeze.
E.g. I expect a few docs issues with the new sphinx version, but we need this helpers to be able to test it.