-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
DOC: Making the build fail if the doc build fails #24292
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
Conversation
Hello @datapythonista! Thanks for submitting the PR.
|
.travis.yml
Outdated
|
||
# In allow_failures | ||
- dist: trusty | ||
env: | ||
- JOB="3.6, doc" ENV_FILE="ci/deps/travis-36-doc.yaml" DOC=true |
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.
leave all of this
i am not convinced this build is actually reliable enough to change this
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.
You'll know better, I just thought that it'd be a good idea to make it break the build for a while, to see if it's actually reliable. Other than taking too long, does it fails with false positives often for any reason?
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.
let's make that an independent change.
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.
fair enough, reverted that part
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.
BTW, the travis build here is only failing when the sphinx build is completely failing, not when there is an error in the doc build. So that shouldn't happen too often.
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, the doc build is failing on travis now. But I am wondering if this is because of "fatal: No such remote: origin".
In that case, we should either fix that to not try to push the docs the github repo on PRs, or revert this PR, as it will currently always fail on PRs.
Codecov Report
@@ Coverage Diff @@
## master #24292 +/- ##
==========================================
- Coverage 92.28% 92.22% -0.06%
==========================================
Files 162 162
Lines 51827 51824 -3
==========================================
- Hits 47827 47795 -32
- Misses 4000 4029 +29
Continue to review full report at Codecov.
|
Codecov Report
@@ Coverage Diff @@
## master #24292 +/- ##
=======================================
Coverage 92.28% 92.28%
=======================================
Files 162 162
Lines 51827 51827
=======================================
Hits 47827 47827
Misses 4000 4000
Continue to review full report at Codecov.
|
thanks @datapythonista |
The doc build is failing silently if sphinx fails. This PR makes the CI red when something goes wrong building the docs.
CC: @jreback
It has been tested here: https://travis-ci.org/pandas-dev/pandas/jobs/468243202