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

deepspeed v0.13.0 #49

Conversation

regro-cf-autotick-bot
Copy link
Contributor

It is very likely that the current package version for this feedstock is out of date.

Checklist before merging this PR:

  • Dependencies have been updated if changed: see upstream
  • Tests have passed
  • Updated license if changed and license_file is packaged

Information about this PR:

  1. Feel free to push to the bot's branch to update this PR if needed.
  2. The bot will almost always only open one PR per version.
  3. The bot will stop issuing PRs if more than 3 version bump PRs generated by the bot are open. If you don't want to package a particular version please close the PR.
  4. If you want these PRs to be merged automatically, make an issue with @conda-forge-admin,please add bot automerge in the title and merge the resulting PR. This command will add our bot automerge feature to your feedstock.
  5. If this PR was opened in error or needs to be updated please add the bot-rerun label to this PR. The bot will close this PR and schedule another one. If you do not have permissions to add this label, you can use the phrase @conda-forge-admin, please rerun bot in a PR comment to have the conda-forge-admin add it for you.

Dependency Analysis

Please note that this analysis is highly experimental. The aim here is to make maintenance easier by inspecting the package's dependencies. Importantly this analysis does not support optional dependencies, please double check those before making changes. If you do not want hinting of this kind ever please add bot: inspection: false to your conda-forge.yml. If you encounter issues with this feature please ping the bot team conda-forge/bot.

Analysis by grayskull shows a discrepancy between it and the the package's stated requirements in the meta.yaml.

Packages found by grayskull but not in the meta.yaml:

  • accelerator

Packages found in the meta.yaml but not found by grayskull:

  • git
  • libaio
  • py-cpuinfo
  • pytorch ==cuda
  • pynvml
  • hjson-py
  • packaging >=20.0
  • tqdm
  • py-cpuinfo
  • numpy
  • psutil
  • pytorch
  • pydantic

This PR was created by the regro-cf-autotick-bot. The regro-cf-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. Feel free to drop us a line if there are any issues! This PR was generated by https://github.com/regro/cf-scripts/actions/runs/7591369181, please use this URL for debugging.

@conda-forge-webservices
Copy link
Contributor

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@regro-cf-autotick-bot regro-cf-autotick-bot mentioned this pull request Jan 24, 2024
3 tasks
@weiji14 weiji14 marked this pull request as draft January 24, 2024 02:14
@weiji14
Copy link
Member

weiji14 commented Jan 24, 2024

Getting this error on the CPU (i.e. no CUDA) builds, e.g. at https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=861659&view=logs&j=3b077b59-19b3-5c3c-d9ea-4f2d359714ca&t=873fce9e-f439-5f0c-2760-c9c359f8480a&l=223:

Processing $SRC_DIR
  Added file://$SRC_DIR to build tracker '/tmp/pip-build-tracker-204_bpwb'
  Running setup.py (path:$SRC_DIR/setup.py) egg_info for package from file://$SRC_DIR
  Created temporary directory: /tmp/pip-pip-egg-info-s074oq1h
  Traceback (most recent call last):
    File "<string>", line 2, in <module>
    File "<pip-setuptools-caller>", line 34, in <module>
    File "/home/conda/feedstock_root/build_artifacts/deepspeed_1705717078997/work/setup.py", line 37, in <module>
      from op_builder import get_default_compute_capabilities, OpBuilder
    File "/home/conda/feedstock_root/build_artifacts/deepspeed_1705717078997/work/op_builder/__init__.py", line 48, in <module>
      module = importlib.import_module(f".{module_name}", package=op_builder_dir)
    File "/home/conda/feedstock_root/build_artifacts/deepspeed_1705717078997/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_p/lib/python3.10/importlib/__init__.py", line 126, in import_module
      return _bootstrap._gcd_import(name[level:], package, level)
    File "/home/conda/feedstock_root/build_artifacts/deepspeed_1705717078997/work/op_builder/xpu/__init__.py", line 6, in <module>
      from .cpu_adam import CPUAdamBuilder
    File "/home/conda/feedstock_root/build_artifacts/deepspeed_1705717078997/work/op_builder/xpu/cpu_adam.py", line 6, in <module>
      from .builder import SYCLOpBuilder
    File "/home/conda/feedstock_root/build_artifacts/deepspeed_1705717078997/work/op_builder/xpu/builder.py", line 16, in <module>
      from deepspeed.ops.op_builder.builder import OpBuilder, TORCH_MAJOR, TORCH_MINOR
    File "/home/conda/feedstock_root/build_artifacts/deepspeed_1705717078997/work/deepspeed/__init__.py", line 10, in <module>
      import torch
  ModuleNotFoundError: No module named 'torch'
  error: subprocess-exited-with-error
  
  × python setup.py egg_info did not run successfully.
  │ exit code: 1
  ╰─> See above for output.

Seems to be related to microsoft/DeepSpeed#4984, where torch is required as a build time dependency. They've reverted the behavior at microsoft/DeepSpeed#5001, so we could just go with v0.13.1 at #50.

@weiji14 weiji14 closed this in #50 Jan 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants