This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients christian.heimes, vstinner
Date 2020-04-03.00:55:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1585875310.01.0.727970021111.issue40163@roundup.psfhosted.org>
In-reply-to
Content
When OpenSSL moves a tarball, all our pre-commit CIs are broken and suddenly, all PRs can no longer be merged. We have first write PRs to update the configuration of our CI to use the newer OpenSSL version, merge these PRs, and then *all* pending PRs must be rebased on top of these merged PRS to retrieve the newer CI configuration.

There are currently 1085 pending PRs at https://github.com/python/cpython/pulls Well, for most of them, the CI already passed so we can merge them. But if a reviewer requires changes, the CI will re-run and then fail :-(

Moreover, fixing multissltests.py doesn't help neither, since again, PRs should be rebased to retrieve multissltests.py changes.

I hope that I'm wrong and the situation is not so bad.

--

Another solution would be to enhance our workflow to always rebase PRs on the development branch. Something like what https://mergify.io/ does.

I'm not sure what is the configuration of Azure Pipelines, GitHub actions and Travis CI. Would it be possible to make them rebase the PRs before running tests.
History
Date User Action Args
2020-04-03 00:55:10vstinnersetrecipients: + vstinner, christian.heimes
2020-04-03 00:55:10vstinnersetmessageid: <1585875310.01.0.727970021111.issue40163@roundup.psfhosted.org>
2020-04-03 00:55:10vstinnerlinkissue40163 messages
2020-04-03 00:55:09vstinnercreate