| 2014-01-30 22:21:58 |
Sean Dague |
description |
The following non-overlapping requirements change https://git.openstack.org/cgit/openstack/requirements/commit/?id=ee07adf62d874266be433bf1c4c2073f4460f661 broke the gate because there is a small lag in the pypi.openstack.org mirror job |
If we change a global-requirement in a non overlapping way... like
psutil < 1.0
to
psutil > 1.1
We cause a lot of failures in the gate.
The reason is that the requirements change is co-gating. So requirement enters gate.
Everything behind that requirement is told to use the new thing. It can't, it's not in the mirror, and only the requirements job is allowed to punch through the mirror.
Changes behind the requirements change will then fail, over and over again. Gate carnage will ensue. Until eventually the requirements change merges, triggers a mirror rebuild, and that then updates the mirror.
We should probably either prevent this in requirements, or we should come up with a way to let projects punch holes in the mirror if they are in a window where requirements change is going on.
message:"Could not find a version that satisfies the requirement psutil>1.1.0" AND filename:console.html
The following non-overlapping requirements change https://git.openstack.org/cgit/openstack/requirements/commit/?id=ee07adf62d874266be433bf1c4c2073f4460f661 broke the gate because there is a small lag in the pypi.openstack.org mirror job |
|
