8000 Circle CI and Appveyor fails on master · Issue #11089 · scikit-learn/scikit-learn · GitHub
[go: up one dir, main page]

Skip to content

Circle CI and Appveyor fails on master #11089

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

Closed
qinhanmin2014 opened this issue May 12, 2018 · 10 comments · Fixed by #11106
Closed

Circle CI and Appveyor fails on master #11089

qinhanmin2014 opened this issue May 12, 2018 · 10 comments · Fixed by #11106
Labels
Blocker Build / CI Easy Well-defined and straightforward way to resolve help wanted

Comments

@qinhanmin2014
Copy link
Member

Open an issue for the latest Circle failure on master.

Unexpected failing examples:
/home/circleci/project/examples/applications/plot_tomography_l1_reconstruction.py failed leaving traceback:
Traceback (most recent call last):
  File "/home/circleci/project/examples/applications/plot_tomography_l1_reconstruction.py", line 115, in <module>
    proj_operator = build_projection_operator(l, l / 7.)
  File "/home/circleci/project/examples/applications/plot_tomography_l1_reconstruction.py", line 95, in build_projection_operator
    proj_operator = sparse.coo_matrix((weights, (camera_inds, data_inds)))
  File "/home/circleci/miniconda/envs/testenv/lib/python3.6/site-packages/scipy/sparse/coo.py", line 150, in __init__
    self._shape = check_shape((M, N))
  File "/home/circleci/miniconda/envs/testenv/lib/python3.6/site-packages/scipy/sparse/sputils.py", line 281, in check_shape
    new_shape = tuple(operator.index(arg) for arg in args)
  File "/home/circleci/miniconda/envs/testenv/lib/python3.6/site-packages/scipy/sparse/sputils.py", line 281, in <genexpr>
    new_shape = tuple(operator.index(arg) for arg in args)
TypeError: 'numpy.float64' object cannot be interpreted as an integer
@qinhanmin2014 qinhanmin2014 added Easy Well-defined and straightforward way to resolve Build / CI Blocker help wanted labels May 12, 2018
@rth
Copy link
Member
rth commented May 15, 2018

Yes, it's quite a strange failure. After quickly looking into it I wasn't able to determine what triggered it. In any case master...rth:fix-plot_tomography_l1_reconstruction could be a start, but it's not sufficient to fix it.

Also now Appevyor is also failing on master,

Collecting futures (from wheelhouse_uploader->-r build_tools/appveyor/requirements.txt (line 15))
58  Downloading https://files.pythonhosted.org/packages/4a/f4/418e844d868e34638486732417fb82b05031910059d88b86aaea9c70f699/futures-3.1.2.tar.gz
59    Complete output from command python setup.py egg_info:
60    This backport is meant only for Python 2.
61    It does not work on Python 3, and Python 3 users do not need it as the concurrent.futures package is available in the standard library.
62    For projects that work on both Python 2 and 3, the dependency needs to be conditional on the Python version, like so:
63    extras_require={':python_version == "2.7"': ['futures']}
64    
65    ----------------------------------------
66

I think that should be fixable by pinning futures==3.1.1

and raising this issue upstream. Upstream issue ogrisel/wheelhouse-uploader#24

@qinhanmin2014
Copy link
Member Author
qinhanmin2014 commented May 15, 2018

And we even get strange errors on Circle like this (See e.g., https://circleci.com/gh/scikit-learn/scikit-learn/23087):

!pdfTeX error: pdflatex (file ./logo.png): libpng: internal error
 ==> Fatal error occurred, no output PDF file produced!
Latexmk: Index file 'user_guide.idx' was written
Collected error summary (may duplicate other messages):
  pdflatex: Command for 'pdflatex' gave return code 256
Latexmk: Use the -f option to force complete processing,
 unless error was exceeding maximum runs of latex/pdflatex.
Latexmk: Errors, so I did not complete making targets
Makefile:33: recipe for target 'user_guide.pdf' failed
make[1]: *** [user_guide.pdf] Error 12
make[1]: Leaving directory '/home/circleci/project/doc/_build/latex'
Makefile:79: recipe for target 'latexpdf' failed
make: *** [latexpdf] Error 2
Exited with code 2

So we now have 2 kinds of Circle failures and 1 Appveyor failure. I'm wondering what's happening these days in the upstream projects. ping @lesteve for more insight.

@qinhanmin2014 qinhanmin2014 changed the title Circle CI fails on master Circle CI and Appveyor fails on master May 15, 2018
@rth
Copy link
Member
rth commented May 15, 2018

I'm wondering what's happening these days in the upstream projects.

Probably maintainers taking time off in May + software entropy )

@lesteve
Copy link
Member
lesteve commented May 16, 2018

#11100 should fix plot_tomography, I haven't looked at the others ...

@lesteve
Copy link
Member
lesteve commented May 17, 2018

OK I am going to close this one, everything seems fine (both AppVeyor and CircleCI) on the last push into master.

@lesteve lesteve closed this as completed May 17, 2018
@lesteve
Copy link
Member
lesteve commented May 17, 2018

Actually there is still the latexmk error in CircleCI ...

@lesteve lesteve reopened this May 17, 2018
@glemaitre
Copy link
Member

The error is a bit weird. It seems that the Tinyclues logo is not a png anymore.

@glemaitre
Copy link
Member

The relevant line is:

<use Tinyclues-PNG-logo.png>libpng error: Not a PNG file

!pdfTeX error: pdflatex (file ./logo.png): libpng: internal error

@rth
Copy link
Member
rth commented May 17, 2018

More investigation showed that the issue is with the AFPy logo: logo.png comes from www.afpy.org/logo.png (see https://github.com/AFPy/site/issues/29 for more details).

Tinyclues came before it in the list of includes and it is fine.

@lesteve
Copy link
Member
lesteve commented May 18, 2018

Thanks for the investigation @rth! Just FYI I opened #11106 which should fix the problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Blocker Build / CI Easy Well-defined and straightforward way to resolve help wanted
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants
0