BUG: refguide check and CircleCI failures in master
See original GitHub issueDescribe your issue.
There are two new CI failures in master that started today.
Error message
refguide (e.g. gh-15325)
File "doc/source/tutorial/interpolate.rst", line 261, in /home/vsts/work/1/s/tools/../doc/source/tutorial/interpolate.rst
Failed example:
interpolate.sproot(tck)
Expected:
array([3.1416])
Got:
array([1.05630421e-17, 3.14159265e+00])
/home/vsts/work/1/s/tools/refguide_check.py:662: DeprecationWarning: elementwise comparison failed; this will raise an error in the future.
if want == got:
CircleCI build_docs (e.g. gh-15326)
waiting for workers...
/home/circleci/repo/build/testenv/lib/python3.8/site-packages/scipy/signal/windows/_windows.py:docstring of scipy.signal.windows._windows.bohman:33: WARNING: Exception occurred in plotting scipy-signal-windows-bohman-1
from /home/circleci/repo/doc/source/reference/generated/scipy.signal.windows.bohman.rst:
Traceback (most recent call last):
File "/home/circleci/repo/venv/lib/python3.8/site-packages/matplotlib/sphinxext/plot_directive.py", line 517, in _run_code
exec(code, ns)
File "<string>", line 16, in <module>
RuntimeWarning: divide by zero encountered in log10
/home/circleci/repo/build/testenv/lib/python3.8/site-packages/scipy/signal/windows/_windows.py:docstring of scipy.signal.windows._windows.cosine:36: WARNING: Exception occurred in plotting scipy-signal-windows-cosine-1
from /home/circleci/repo/doc/source/reference/generated/scipy.signal.windows.cosine.rst:
Traceback (most recent call last):
File "/home/circleci/repo/venv/lib/python3.8/site-packages/matplotlib/sphinxext/plot_directive.py", line 517, in _run_code
exec(code, ns)
File "<string>", line 16, in <module>
RuntimeWarning: divide by zero encountered in log10
SciPy/NumPy/Python version information
master
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Troubleshooting Unexplained Build Failures - CircleCI
Things to check when your build has failed.
Read more >All builds fail with 'Circle Bug' - CircleCI Discuss
Hey Circle dudes, Since yesterday all of my builds have been failing with the following error message: Looks like we had a bug...
Read more >Automatically identify which code changes caused errors
We will execute our build on CircleCI, run the application, then generate a test error. This will send a test error to Rollbar...
Read more >`circleci build` fails after updating circleci command (0.0.5610 ...
example: https://github.com/ikuwow/query_ok/blob/master/.circleci/config. ... or directory Error: Exited with code 1 Step failed Task failed.
Read more >Some checks were not successful - Build Environment
Как исправить ошибка сборки - ваши тесты не пройдены на CircleCI [Mod Edit for translation] How to fix a build error - your...
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
Copying the warnings here:
These are coming from
f2py
-generated docstrings, which are ending up inbuild/scipy/linalg/_flapackmodule.c
. There isn’t anything we can do to fix this I think, so let’s pin to numpy1.21.5
in the doc build and see if it can be fixed in1.22.1
.The fix for the lapack issues will be in numpy
1.22.1
.