Skip to content
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

BUG: pip install scipy not working in azure pipelines. gfortran files are not runnable #17187

Closed
patou01 opened this issue Oct 10, 2022 · 3 comments
Labels
Build issues Issues with building from source, including different choices of architecture, compilers and OS defect A clear bug or issue that prevents SciPy from being installed or used as expected

Comments

@patou01
Copy link

patou01 commented Oct 10, 2022

Describe your issue.

This morning while running our CI build for a project, the CI didn't succeed in installing the requirements, the culprit seems to be scipy.

I saw the version got raised to 1.9.2 yesterday, our last run was friday. I pinned to 1.9.1 and then our build succeeds. This is not really an issue for us, but maybe something broke.

Our configuration of the pipeline is as vanilla as I can make it (I haven't touched anything).

Our requirements were not pinned, so I'll pin them. They looked like this at the time of issue

argparse~=1.4.0
comtypes
control
dacite
dictdiffer~=0.9.0
docxtpl
gitpython
importlib_resources
jsonpickle
matplotlib
numpy
OpenOPC-Python3x
openpyxl
pandas~=1.3.4
paramiko
pre-commit
pylint
pytest
pywin32
pyyaml
scipy
selenium
setuptools
sphinx
sphinx-autodoc-defaultargs
sphinx-autodoc-typehints
sphinx-rtd-theme
sphinxcontrib-mermaid
suds-community

Reproducing Code Example

pool:
  vmImage: windows-latest

steps:
- task: UsePythonVersion@0
  inputs:
    versionSpec: '3.9'
    architecture: 'x86'
  displayName: 'Use Python 3.9 x86'

- checkout: self

- script: |
    pip install -e .
  displayName: 'Install library'

Error message

Collecting scipy
  Downloading scipy-1.9.2.tar.gz (42.1 MB)
     --------------------------------------- 42.1/42.1 MB 16.0 MB/s eta 0:00:00
  Installing build dependencies: started
    File "C:\hostedtoolcache\windows\Python\3.9.13\x86\lib\site-packages\pip\_vendor\pep517\in_process\_in_process.py", line 363, in <module>
      main()
    File "C:\hostedtoolcache\windows\Python\3.9.13\x86\lib\site-packages\pip\_vendor\pep517\in_process\_in_process.py", line 345, in main
      json_out['return_val'] = hook(**hook_input['kwargs'])
    File "C:\hostedtoolcache\windows\Python\3.9.13\x86\lib\site-packages\pip\_vendor\pep517\in_process\_in_process.py", line 130, in get_requires_for_build_wheel
      return hook(config_settings)
    File "C:\Users\VssAdministrator\AppData\Local\Temp\pip-build-env-zfq_wxab\overlay\Lib\site-packages\mesonpy\__init__.py", line 969, in get_requires_for_build_wheel
      with _project(config_settings) as project:
    File "C:\hostedtoolcache\windows\Python\3.9.13\x86\lib\contextlib.py", line 119, in __enter__
      return next(self.gen)
    File "C:\Users\VssAdministrator\AppData\Local\Temp\pip-build-env-zfq_wxab\overlay\Lib\site-packages\mesonpy\__init__.py", line 948, in _project
      with Project.with_temp_working_dir(
    File "C:\hostedtoolcache\windows\Python\3.9.13\x86\lib\contextlib.py", line 119, in __enter__
      return next(self.gen)
    File "C:\Users\VssAdministrator\AppData\Local\Temp\pip-build-env-zfq_wxab\overlay\Lib\site-packages\mesonpy\__init__.py", line 777, in with_temp_working_dir
      yield cls(source_dir, tmpdir, build_dir)
    File "C:\Users\VssAdministrator\AppData\Local\Temp\pip-build-env-zfq_wxab\overlay\Lib\site-packages\mesonpy\__init__.py", line 682, in __init__
      self._configure(reconfigure=bool(build_dir) and not native_file_mismatch)
    File "C:\Users\VssAdministrator\AppData\Local\Temp\pip-build-env-zfq_wxab\overlay\Lib\site-packages\mesonpy\__init__.py", line 713, in _configure
      self._meson(
    File "C:\Users\VssAdministrator\AppData\Local\Temp\pip-build-env-zfq_wxab\overlay\Lib\site-packages\mesonpy\__init__.py", line 696, in _meson
      return self._proc('meson', *args)
    File "C:\Users\VssAdministrator\AppData\Local\Temp\pip-build-env-zfq_wxab\overlay\Lib\site-packages\mesonpy\__init__.py", line 691, in _proc
      subprocess.check_call(list(args))
    File "C:\hostedtoolcache\windows\Python\3.9.13\x86\lib\subprocess.py", line 373, in check_call
      raise CalledProcessError(retcode, cmd)
  subprocess.CalledProcessError: Command '['meson', 'setup', '--native-file=C:\\Users\\VssAdministrator\\AppData\\Local\\Temp\\pip-install-7g8y88l9\\scipy_0f37be93b2084ecdaf3be83d94b0d550\\.mesonpy-native-file.ini', '-Ddebug=false', '-Doptimization=2', '--prefix=C:\\hostedtoolcache\\windows\\Python\\3.9.13\\x86', 'C:\\Users\\VssAdministrator\\AppData\\Local\\Temp\\pip-install-7g8y88l9\\scipy_0f37be93b2084ecdaf3be83d94b0d550', 'C:\\Users\\VssAdministrator\\AppData\\Local\\Temp\\pip-install-7g8y88l9\\scipy_0f37be93b2084ecdaf3be83d94b0d550\\.mesonpy-5nvmnz5l\\build']' returned non-zero exit status 1.
  [end of output]
  
  note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error

SciPy/NumPy/Python version information

1.9.2, 1.23.3, 3.9.13

@patou01 patou01 added the defect A clear bug or issue that prevents SciPy from being installed or used as expected label Oct 10, 2022
@j-bowhay j-bowhay added the Build issues Issues with building from source, including different choices of architecture, compilers and OS label Oct 10, 2022
@andyfaff
Copy link
Contributor

I've just tried pip installing scipy on a Windows 10 box. The install works and the tests pass.
It's telling that it's trying to install from source rather than the scipy-1.9.2-cp39-cp39-win_amd64.whl binary. Is this a 32 bit test run? Can you specifically get it to install that wheel?

@patou01
Copy link
Author

patou01 commented Oct 10, 2022

Crap. I think I'm an idiot. It's even been mentioned and I reacted on the issue here #16286 . Yeah we run 32 bits, and I guess "in the near future" back then is probably "now" today.

It seems the drop was not at 1.9, but has been done at 1.9.2 ?

Collecting pyyaml
  Downloading PyYAML-6.0-cp39-cp39-win32.whl (138 kB)
     -------------------------------------- 138.0/138.0 kB 8.5 MB/s eta 0:00:00
Collecting scipy
  Downloading scipy-1.9.1-cp39-cp39-win32.whl (34.6 MB)
     --------------------------------------- 34.6/34.6 MB 19.3 MB/s eta 0:00:00
Collecting selenium
  Downloading selenium-4.5.0-py3-none-any.whl (995 kB)
     ------------------------------------- 995.2/995.2 kB 21.0 MB/s eta 0:00:00

This is from my run last friday, so yeah, I need to pin scipy and that'll be good enough. I even mentioned back then that some would have issues because the failure message might not be very clear 😢 .

In 1.9.1, release files for 3.9 are
image

In 1.9.2, release files are
image

My bad I guess, thanks for the hint on architecture.

@andyfaff
Copy link
Contributor

No worries.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Build issues Issues with building from source, including different choices of architecture, compilers and OS defect A clear bug or issue that prevents SciPy from being installed or used as expected
Projects
None yet
Development

No branches or pull requests

3 participants