Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
CI should fail if documentation does not build correctly
See original GitHub issueCurrent issues:
pyPESTO/pypesto/objective/objective.py:docstring of pypesto.objective.Objective:7: WARNING: Unexpected indentation.
pyPESTO/pypesto/objective/objective.py:docstring of pypesto.objective.Objective:8: WARNING: Block quote ends without a blank line; unexpected unindent.
pyPESTO/pypesto/objective/objective.py:docstring of pypesto.objective.Objective:13: WARNING: Unexpected indentation.
pyPESTO/pypesto/objective/objective.py:docstring of pypesto.objective.Objective:14: WARNING: Block quote ends without a blank line; unexpected unindent.
pyPESTO/pypesto/objective/objective.py:docstring of pypesto.objective.Objective:19: WARNING: Unexpected indentation.
pyPESTO/pypesto/objective/objective.py:docstring of pypesto.objective.Objective:20: WARNING: Block quote ends without a blank line; unexpected unindent.
pyPESTO/pypesto/objective/objective.py:docstring of pypesto.objective.Objective:27: WARNING: Definition list ends without a blank line; unexpected unindent.
pyPESTO/pypesto/objective/objective.py:docstring of pypesto.objective.Objective:35: WARNING: Unexpected indentation.
pyPESTO/pypesto/objective/objective.py:docstring of pypesto.objective.Objective:36: WARNING: Block quote ends without a blank line; unexpected unindent.
pyPESTO/pypesto/objective/objective.py:docstring of pypesto.objective.Objective.check_grad:15: WARNING: Definition list ends without a blank line; unexpected unindent.
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Troubleshooting CI/CD - GitLab Docs
If the wrong pipeline type ran, then the rules or only/except configuration should be checked to make sure the jobs are added to...
Read more >TeamCity On-Premises - Build Failure Conditions - JetBrains
The if the build process exit code is not zero condition allows failing a build if the build process doesn't exit successfully.
Read more >after_success failure doesn't fail build · Issue #758 · travis-ci ...
My build is (correctly) failing but it is not indicated as such. In the docs it says "The outcome of any of these...
Read more >Travis CI R package error in documentation - Stack Overflow
Are written using Rcpp / RcppArmadillo. Specifically, I receive the following warning from Travis CI: Functions or methods with usage in ...
Read more >Common Build Problems - Travis CI Docs
A very common cause when a test is suddenly breaking without any major code changes involved is a change in upstream dependencies. This...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
the docs build on master and, for testing, on develop changes. Thus, one would get notified as soon as the develop docs break. You (=maintainers) can also turn on e-mail notifications in case the docs build fails.
I guess this can be closed then…