Closed estraph closed 1 year ago
What was in that log file - /home/runner/.cache/nce/e947b027d236a97e80c898f86405dec4785e8b482758e80af7ef24129029f799/bindings/logs/install.log ?
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?
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.
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.
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 thepants --version
call when bootstrapping pants: