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
Trigger a build building Python, managing the requirements with pip and pipenv
Check build logs
Logs state that the build failed because the hashes of the dependencies do not match up with the ones in the pipfile.lock file
Expected behavior
Build is successful
Logs
...
An error occurred while installing pip-shims==0.5.3 ; python_version >= '2.7' and python_version not in '3.0, 3.1, 3.2, 3.3, 3.4' --hash=sha256:05b00ade9d1e686a98bb656dd9b0608a933897283dc21913fad6ea5409ff7e91 --hash=sha256:16ca9f87485667b16b978b68a1aae4f9cc082c0fa018aed28567f9f34a590569! Will try again.
...
[pipenv.exceptions.InstallError]: ERROR: THESE PACKAGES DO NOT MATCH THE HASHES FROM THE REQUIREMENTS FILE. If you have updated the package versions, please update the hashes. Otherwise, examine the package contents carefully; someone may have tampered with them
...
Platform (please complete the following information):
OS: Linux x86
Additional context
N/A
The text was updated successfully, but these errors were encountered:
Describe the bug
One of our builds suddenly started failing on a build after a change in an unrelated file.
aws/codebuild/standard:5.0-22.10.27 works, aws/codebuild/standard:5.0-23.02.16 fails
To Reproduce
Steps to reproduce the behavior:
pipfile.lock
fileExpected behavior
Build is successful
Logs
Platform (please complete the following information):
Additional context
N/A
The text was updated successfully, but these errors were encountered: