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

PEP 561 test failures due to pyinfo break wheel builds on macOS #13174

Closed
JukkaL opened this issue Jul 18, 2022 · 0 comments · Fixed by #13176
Closed

PEP 561 test failures due to pyinfo break wheel builds on macOS #13174

JukkaL opened this issue Jul 18, 2022 · 0 comments · Fixed by #13176
Labels
bug mypy got something wrong priority-0-high

Comments

@JukkaL
Copy link
Collaborator

JukkaL commented Jul 18, 2022

Traceback from https://github.com/mypyc/mypy_mypyc-wheels/runs/7376619798?check_suite_focus=true (also reproduces locally on macOS):

  ______________________________ testTypedPkgSimple ______________________________
  [gw1] darwin -- Python 3.10.0 /private/var/folders/24/8k48jl6d249_n_qfxwsl6xvm0000gn/T/tmpl3v_i2pp/bin/python
  data: /Users/runner/work/mypy_mypyc-wheels/mypy_mypyc-wheels/mypy/test-data/unit/pep561.test:14:
  ../tmpl3v_i2pp/lib/python3.10/site-packages/mypy/test/testpep561.py:31: in run_case
      test_pep561(test_case)
  ../tmpl3v_i2pp/lib/python3.10/site-packages/mypy/test/testpep561.py:142: in test_pep561
      out, err, returncode = mypy.api.run(cmd_line)
  mypy/api.py:69: in run
      ???
  mypy/api.py:58: in _run
      ???
  mypy/api.py:69: in <lambda>
      ???
  mypy/main.py:96: in main
      ???
  mypy/main.py:173: in run_build
      ???
  mypy/build.py:154: in build
      ???
  mypy/build.py:186: in _build
      ???
  mypy/modulefinder.py:844: in compute_search_paths
      ???
  mypy/modulefinder.py:748: in get_search_dirs
      ???
  /Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/subprocess.py:420: in check_output
      return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
  /Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/subprocess.py:524: in run
      raise CalledProcessError(retcode, process.args,
  E   subprocess.CalledProcessError: Command '['/var/folders/24/8k48jl6d249_n_qfxwsl6xvm0000gn/T/tmp1l0jvq71/bin/python', '/private/var/folders/24/8k48jl6d249_n_qfxwsl6xvm0000gn/T/tmpl3v_i2pp/lib/python3.10/site-packages/mypy/pyinfo.py', 'getsearchdirs']' returned non-zero exit status 1.

I have checked that this is a side effect of #13161.

@JukkaL JukkaL added bug mypy got something wrong priority-0-high labels Jul 18, 2022
JukkaL added a commit that referenced this issue Jul 18, 2022
We run mypy/pyinfo.py as a script, and this means that mypy/types.py
could be picked up instead of the stdlib `types` module, which clearly
doesn't work. This seems to happen at least on macOS, and it broke
PEP 561 tests.

The workaround was accidentally removed as part of #13161.

This should fix #13174 and help with the wheel builds.
JukkaL added a commit that referenced this issue Jul 18, 2022
…#13176)

We run mypy/pyinfo.py as a script, and this means that mypy/types.py
could be picked up instead of the stdlib `types` module, which clearly
doesn't work. This seems to happen at least on macOS, and it broke
PEP 561 tests.

The workaround was accidentally removed as part of #13161.

This should fix #13174 and help with the wheel builds.
JukkaL added a commit that referenced this issue Jul 18, 2022
…#13176)

We run mypy/pyinfo.py as a script, and this means that mypy/types.py
could be picked up instead of the stdlib `types` module, which clearly
doesn't work. This seems to happen at least on macOS, and it broke
PEP 561 tests.

The workaround was accidentally removed as part of #13161.

This should fix #13174 and help with the wheel builds.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug mypy got something wrong priority-0-high
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant