-
Notifications
You must be signed in to change notification settings - Fork 12
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
CI breakage for the reproducible wheels using extensions #253
Comments
kushaldas
changed the title
CI breage for the reproducible wheels using extensions
CI breakage for the reproducible wheels using extensions
Jul 7, 2021
kushaldas
added a commit
that referenced
this issue
Jul 9, 2021
This PR adds a new container and also uses it in the CircleCI to test reproducible wheels and Debian packages. The container is based on standard Debian Buster, thus having the same version of Python and environment.
kushaldas
added a commit
that referenced
this issue
Jul 9, 2021
This PR adds a new container and also uses it in the CircleCI to test reproducible wheels and Debian packages. The container is based on standard Debian Buster, thus having the same version of Python and environment.
kushaldas
added a commit
that referenced
this issue
Jul 9, 2021
This PR adds a new container and also uses it in the CircleCI to test reproducible wheels and Debian packages. The container is based on standard Debian Buster, thus having the same version of Python and environment.
1 task
sssoleileraaa
added a commit
that referenced
this issue
Jul 27, 2021
Fixes #253 adds reproducible testing container
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Our CI for reproducible wheels is using CircleCI's Python 3.7 container image. Which installs the latest Python from source, thus it has a different version of Python and also totally different CFLAGS.
https://circleci.com/api/v1.1/project/github/freedomofpress/securedrop-debian-packaging/8970/output/102/0?file=true&allocation-id=60e3091a6147e451fc8f1ff6-0-build%2F52B5BD2F contains one such example failure.
Below are the values from container:
And here are the values from a standard Debian Buster system
The text was updated successfully, but these errors were encountered: