-
-
Notifications
You must be signed in to change notification settings - Fork 32.2k
bpo-35683: Improve Azure Pipelines steps #11493
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
Conversation
The full APPX test was only in the PR build for testing. The idea is to run it against commits only to avoid adding extra time to PRs while still having a way to check whether we've broken various parts of the distro. For anyone who doesn't know, you can view CI build status at https://github.com/python/cpython/commits/master (including all the buildbots :) ) |
I was just pointed at this and I thought it might be worth mentioning that we updated the |
@reaperhulk Not at all, since the container isn't actually suitable for our needs anyway (nor was the previous one in the build files, which is why I left it referenced). We probably need to set up our own container with the right dependencies for building and testing CPython itself - the base definition for manylinux containers goes past this point, so any derived ones are going to be missing things. They're fine for building binaries (I assume), but not for running our entire test suite. |
GH-11651 is a backport of this pull request to the 3.7 branch. |
|
This is a false positive/race condition, a re-run is successful: https://buildbot.python.org/all/#/builders/116/builds/993 Something in
|
Yeah, the standard manylinux image intentionally deletes some libraries that cpython needs to build (because we don't want the particular versions we used to accidentally become something package maintainers depending on). |
https://bugs.python.org/issue35683