Change Details

Since fairly recently, our builds (if not all) are broken [1]. In this case, it's related to a new major pytest version which dropped the support of one of the fixture we use in all our modules. We started pinning some of our modules to work around this. This task tracks the remaining work to do the same everywhere. [1] https://jenkins.softwareheritage.org/view/swh-draft/

Since fairly recently, our builds (if not all) are broken [1]. This is due to two external pytest modules we are using that are importing private pytest modules that were removed: - pytest-postgresql < 4.0.0 - pytest-redis The issue has been fixed in pytest-postgresql >= 4.0.0 but not in pytest-redis yet. Currently we cannot use pytest-postgresql >= 4.0.0 as it now uses psycopg3 but our codebase is still based on psycopg2. To currently work around this, we started pinning some of our modules. This task tracks the remaining work to do the same on the remaining broken modules. [1] https://jenkins.softwareheritage.org/view/swh-draft/

Since fairly recently, our builds (if not all) are broken [1]. In this case, it's related to a new majorThis is due to two external pytest version which dropped the supmodules we are using that are import ofing private one of the fixture we use in all our modules.pytest modules that were removed: We started pinning some of our modules to work around this. This task tracks the- pytest-postgresql < 4.0.0 - pytest-redis The issue has been fixed in pytest-postgresql >= 4.0.0 but not in pytest-redis yet. Currently we cannot use pytest-postgresql >= 4.0.0 as it now uses psycopg3 but our codebase is still based on psycopg2. To currently work around this, we started pinning some of our modules. This task tracks the remaining work to do the same everywhereon the remaining broken modules. [1] https://jenkins.softwareheritage.org/view/swh-draft/