Open Stack

On 2021-09-22 18:02:40 +0200 (+0200), Balazs Gibizer wrote:
[...]
> As the issue affects even the recent stable branches this would
> effectively mean we lose all the lower-constraints testing.

I've been strongly recommending dropping those jobs from all stable
branches as soon as the branch is created. They're inherently broken
by design, I did my best to explain that when the idea first arose,
they don't really test what they set out to and the cost of keeping
them functioning is disproportionately high. Many projects have
already gotten rid of them, they're not mandated by the PTI anyway.

> And if later the same thing happen with one of our upper
> requirements then we will to lose all the testing. I think we
> cannot simply say that we ignore the problem by turning off the
> job.

But that's not the current situation, right? I can come up with all
sorts of scenarios where we might break upper bounds testing, that's
merely one of them, we should evaluate our options for those on a
case by case basis as they arise since the nature of the conflict
will determine which solutions are viable and at what cost/benefit
ratios.

> Does it mean you suggest bumping the decorator dependency to 4.0.0?

In master, yes. On stable branches I recommend tossing the
lower-constraints.txt based jobs out the nearest window.
-- 
Jeremy Stanley
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 963 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20210922/08340a2c/attachment.sig>