pantsbuild / actions

Useful GitHub Actions that work with the Pants build system
Apache License 2.0
12 stars 14 forks source link

intermittent failure: No matching distribution found for setuptools<58 #20

Closed estraph closed 1 year ago

estraph commented 1 year ago

Today I had a failure of the init-pants action (version @main) in our CI. I retried shortly after and it succeeded. I wonder what would cause this to fail intermittently? The error occurred at the pants --version call when bootstrapping pants:

Run pants --version
  pants --version
  shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}
  env:
    pythonLocation: /opt/hostedtoolcache/Python/3.11.3/x64
    PKG_CONFIG_PATH: /opt/hostedtoolcache/Python/3.11.3/x64/lib/pkgconfig
    Python_ROOT_DIR: /opt/hostedtoolcache/Python/3.11.3/x64
    Python2_ROOT_DIR: /opt/hostedtoolcache/Python/3.11.3/x64
    Python3_ROOT_DIR: /opt/hostedtoolcache/Python/3.11.3/x64
    LD_LIBRARY_PATH: /opt/hostedtoolcache/Python/3.11.3/x64/lib
    PANTS_CONFIG_FILES: pants.ci.toml
Bootstrapping Pants 2.15.0 using cpython 3.9.15
Installing pantsbuild.pants==2.15.0 into a virtual environment at /home/runner/.cache/nce/e947b027d236a97e80c898f86405dec4785e8b482758e80af7ef24129029f799/bindings/venvs/2.15.0
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 2.1/2.1 MB 59.7 MB/s eta 0:00:00
ERROR: Could not find a version that satisfies the requirement setuptools<58 (from versions: 63.4.3)
ERROR: No matching distribution found for setuptools<58
Install failed: Command '['/home/runner/.cache/nce/e947b027d236a97e80c898f86405dec4785e8b482758e80af7ef24129029f799/bindings/venvs/2.15.0/bin/python', '-sE', '-m', 'pip', '--disable-pip-version-check', '--no-python-version-warning', '--log', PosixPath('/home/runner/.cache/nce/e947b027d236a97e80c898f86405dec4785e8b482758e80af7ef24129029f799/bindings/venvs/2.15.0/pants-install.log'), 'install', '--quiet', '--find-links', 'file:///home/runner/.cache/nce/e947b027d236a97e80c898f86405dec4785e8b482758e80af7ef24129029f799/bindings/find_links/2.15.0/214abc14/index.html', '-U', 'pip==22.3.1', 'setuptools<58', 'wheel']' returned non-zero exit status 1.
More information can be found in the log at: /home/runner/.cache/nce/e947b027d236a97e80c898f86405dec4785e8b482758e80af7ef24129029f799/bindings/logs/install.log

Error: Isolates your Pants from the elements.

Please select from the following boot commands:

<default>: Detects the current Pants installation and launches it.
bootstrap-tools: Introspection tools for the Pants bootstrap process.
pants: Runs a hermetic Pants installation.
pants-debug: Runs a hermetic Pants installation with a debug server for debugging Pants code.
update: Update scie-pants.

You can select a boot command by passing it as the 1st argument or else by setting the SCIE_BOOT environment variable.

ERROR: Failed to establish atomic directory /home/runner/.cache/nce/e947b027d236a97e80c898f86405dec4785e8b482758e80af7ef24129029f799/locks/install-e377c19e560680b66eebbb7b25f2c8cf37985e132ee56b579371b97f64bd8b4b. Population of work directory failed: Boot binding command failed: exit status: 1
Error: Process completed with exit code 1.
benjyw commented 1 year ago

What was in that log file - /home/runner/.cache/nce/e947b027d236a97e80c898f86405dec4785e8b482758e80af7ef24129029f799/bindings/logs/install.log ?

benjyw commented 1 year ago

I imagine maybe a temporary network flake or PyPI glitch.

Are you using a custom self-hosted index or proxy to PyPI? Did this happen more than once?

estraph commented 1 year ago

What was in that log file - /home/runner/.cache/nce/e947b027d236a97e80c898f86405dec4785e8b482758e80af7ef24129029f799/bindings/logs/install.log ?

Unfortunately I couldn't retrieve it, so I don't know. :-(

Are you using a custom self-hosted index or proxy to PyPI? Did this happen more than once?

It only happened once, and no, no proxy or self-hosted index.

If I'm the only one who's seen this then I'm happy to dismiss it as a fluke, just thought I'd raise it in case there's something else going on.

benjyw commented 1 year ago

Thanks for the report! If it happens again please try to grab the logfile, and reopen this ticket. For now I'll assume a PyPI hiccup.