On 2020-04-18 18:54:33 +0200 (+0200), Radosław Piliszek wrote:
On Sat, Apr 18, 2020 at 6:01 PM Jeremy Stanley <fungi@yuggoth.org> wrote: [...]
What I would consider a problem with the job is if the constraints file specified one version of a package but a different version of that package got installed instead. If *that's* what's happening (though skimming the logs I don't see any evidence of it) then I agree something is wrong and we should seek to fix it. I did at least double-check that the entries you've left in lower-constraints.txt match those pip installed according to tox/lower-constraints-1.log so it looks to me like its working as designed.
Nah, it's surely not happening. The point was really about coverage and what we want from lower-constraints really (as OpenStack community).
In another subthread, Andreas has pointed out an example where the lower constraints job was actually ignoring mismatched requirements under some circumstances, which does seem buggy. If we want to keep these jobs, we should probably find a way to make them fail on unsatisfiable constraints sets. Subsequent investigation has, however, led me to suspect that the effort involved in establishing and maintaining a coherent set of lower constraints for many projects is currently untenable. -- Jeremy Stanley