Skip to content

fix pyenv mismatch dependencies error #652

@KazuCocoa

Description

@KazuCocoa

The problem

Newer pyenv led the below error: https://dev.azure.com/AppiumCI/Appium%20CI/_build/results?buildId=18323&view=logs&j=fdfef792-cd22-58da-42f1-ee1af92af3d5&t=ca24a7e5-3187-586e-43cb-3ad2ce8bdf93

[ResolutionFailure]:   File "/home/vsts/work/1/s/.tox/py/lib/python3.9/site-packages/pipenv/resolver.py", line 743, in _main
[ResolutionFailure]:       resolve_packages(pre, clear, verbose, system, write, requirements_dir, packages, dev)
[ResolutionFailure]:   File "/home/vsts/work/1/s/.tox/py/lib/python3.9/site-packages/pipenv/resolver.py", line 704, in resolve_packages
[ResolutionFailure]:       results, resolver = resolve(
[ResolutionFailure]:   File "/home/vsts/work/1/s/.tox/py/lib/python3.9/site-packages/pipenv/resolver.py", line 685, in resolve
[ResolutionFailure]:       return resolve_deps(
[ResolutionFailure]:   File "/home/vsts/work/1/s/.tox/py/lib/python3.9/site-packages/pipenv/utils.py", line 1369, in resolve_deps
[ResolutionFailure]:       results, hashes, markers_lookup, resolver, skipped = actually_resolve_deps(
[ResolutionFailure]:   File "/home/vsts/work/1/s/.tox/py/lib/python3.9/site-packages/pipenv/utils.py", line 1098, in actually_resolve_deps
[ResolutionFailure]:       resolver.resolve()
[ResolutionFailure]:   File "/home/vsts/work/1/s/.tox/py/lib/python3.9/site-packages/pipenv/utils.py", line 876, in resolve
[ResolutionFailure]:       raise ResolutionFailure(message=str(e))
[pipenv.exceptions.ResolutionFailure]: Warning: Your dependencies could not be resolved. You likely have a mismatch in your sub-dependencies.
  You can use $ pipenv install --skip-lock to bypass this mechanism, then run $ pipenv graph to inspect the situation.
  Hint: try $ pipenv lock --pre if it is a pre-release dependency.
ERROR: Disabling PEP 517 processing is invalid: project specifies a build backend of setuptools.build_meta in pyproject.toml

ERROR: InvocationError for command /home/vsts/work/1/s/.tox/py/bin/pipenv lock --pre --clear (exited with code 1)
____________

#651 is a workaround.

Environment

  • Appium version (or git revision) that exhibits the issue:
  • Last Appium version that did not exhibit the issue (if applicable):
  • Desktop OS/version used to run Appium:
  • Node.js version (unless using Appium.app|exe):
  • Mobile platform/version under test:
  • Real device or emulator/simulator:
  • Appium CLI or Appium.app|exe:

Details

If necessary, describe the problem you have been experiencing in more detail.

Link to Appium Logs

Create a GIST which is a paste of your full Appium logs, and link them here.

Code To reproduce issue

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions