You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Downstream CI is failing with the following errors:
RuntimeError
Invalid hashes (sha256:bdbb3d96c4581f56d99a30d8d71391c11536930f13df92f6a7a7cca07a98c1de) for ruamel.yaml (0.17.10) using archive ruamel.yaml-0.17.10-py3-none-any.whl. Expected one of sha256:106bc8d6dc6a0ff7c9196a47570432036f41d556b779c6b4e618085f57e39e67, sha256:ffb9b703853e9e8b7861606dfdab1026cf02505bade0653d1880f4b2db47f815.
at /var/lib/jenkins/workspace/OCP_Test_Lib_Pull_Request@2/scenario/lib64/python3.9/site-packages/poetry/installation/executor.py:628 in _download_link
624│ )
625│ )
626│
627│ if archive_hashes.isdisjoint(hashes):
→ 628│ raise RuntimeError(
629│ "Invalid hashes ({}) for {} using archive {}. Expected one of {}.".format(
630│ ", ".join(sorted(archive_hashes)),
631│ package,
632│ archive.name,
• Installing unittest-xml-reporting (3.0.4)
Downstream CI is failing with the following errors:
Symtoms look similar to this poetry issue python-poetry/poetry#4523
What is odd is that the latest builds are failing with this error using poetry-1.1.11-py2.py3-none-any.whl and poetry_core-1.0.7-py2.py3-none-any.whl
But the last successful build that ran on October 28th installed the same poetry packages
The text was updated successfully, but these errors were encountered: