Hi Sandro,

On 08/06/22 at 21:21 -0400, Sandro Tosi wrote:

Hello Lucas,
the Debian Python Team is in the process of updating pytest to a new
upstream release. Given the substantial number of packages depending
on it, we'd like to leverage the mass rebuild infrastructure to build
the reverse dependencies against pytest/7.1.2-1 in experimental.

I've opened a MR for adding the new mode at https://salsa.debian.org/lucas/collab-qa-tools/-/merge_requests/22 and
you can find attached the package list.

Thanks a lot in advance!

Results are available in:
http://qa-logs.debian.net/2022/06/09/

http://qa-logs.debian.net/2022/06/09/res.base.txt are the reference
results
http://qa-logs.debian.net/2022/06/09/res.pytest.txt are the results with
pytest from experimental
http://qa-logs.debian.net/2022/06/09/diff.pytest.txt are the differences http://qa-logs.debian.net/2022/06/09/pytest/ are the logs for all
packages in diff.pytest.txt

Note that 'pyranges' hung during test (or was extremely slow to
complete), and I had to kill it. So the log does not reflect what really happens.

Lucas

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi,

Am 15.06.22 um 21:22 schrieb Louis-Philippe Véronneau:

# Doesn't seem like a pytest regression, but I could be wrong?:
...
* sentry-python 1.4.3-1 (AssertionError: previous item was not torn down properly)

# Already fixed in the archive:

* monitoring-plugins-systemd 2.3.1-2

I've updated sentry-python last week to the current upstream version, so
this package can be count as fixed.

Current pygments requires pytest >= 7.0, I've uploaded 2.12.0 to
experimental.

--
Regards
Carsten

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Copy: debian-python@lists.debian.org (debian-python)

This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --------------h0MS3v7P8PiFBoGUC5svhaXI
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Thanks a lot for this rebuild, very useful.

I was told you needed a list of pytest regressions for you to fill bug reports. It's my first time doing this, so if I missed something you needed, please say so.

# Valid pytest regression, deprecated feature:

* asyncpg 0.25.0-1 (deprecated pytest feature: -k-)
* junitparser 2.5.0-2 (deprecated pytest feature: -k-)
* openlp 2.9.4-2 (deprecated pytest feature: -k-)
* python-astor 0.8.1-2 (deprecated pytest feature: -k-)
* python-aws-xray-sdk 0.95-2 (deprecated pytest feature: -k-)
* python-b2sdk 1.3.0-2 (deprecated pytest feature: -k-)
* python-easydev 0.12.0+dfsg-2 (deprecated pytest feature: -k-)
* python-h11 0.13.0-1 (deprecated pytest feature: -k-)
* python-jose 3.3.0+dfsg-2 (deprecated pytest feature: -k-)
* python-matrix-nio 0.19.0-2 (deprecated pytest feature: -k-)
* python-twitter 3.3-3 (deprecated pytest feature: -k-)
* sphinx-gallery 0.10.1-1 (deprecated pytest feature: -k-)
* spyne 2.14.0-1 (deprecated pytest feature: -k-)
* flask 2.0.1-2 (deprecated pytest feature: pytest.warns(None))
* photutils 1.4.0-3 (deprecated pytest feature: pytest.warns(None))
* python-ase 3.22.1-1 (deprecated pytest feature: pytest.warns(None))

# Probably a valid pytest regression, but I'm less sure:

* python-biom-format 2.1.10-4 (not sure what the problem is, seems like pytest) * python-httplib2 0.20.2-3 (not sure what the problem is, seems like pytest)
* python-pytest-subtests 0.6.0-1 (not sure what the problem is, seems like pytest)
* python-can 3.3.2.final~github-3 (AttributeError: pytest.approx() is not supported in a boolean context)
* python-protobix 1.0.2-11 (plugin distutils failed with: exit code=5)
* python-pykka 2.0.3-2 (AttributeError: module pytest has no attribute collect) * python-ratelimiter 1.2.0.post0-1 (AttributeError: module pytest has no attribute collect)
* python-pytest-xprocess 0.18.1-3 (pytest.PytestUnraisableExceptionWarning: Exception ignored)

# Doesn't seem like a pytest regression, but I could be wrong?:

* humanfriendly 10.0-1 (upstream doesn't actually use pytest?)
* pyglet 1.5.14-2 (py3.9 OK, py3.10 fails)
* pyranges 0.0.111+ds-1 (py3.9 OK, py3.10 fails with Fatal Python error: Bus error)
* pytest-pylint 0.18.0-3 (AssertionError)
* python-qtpy 2.1.0-2 (TypeError: the 'package' argument is required to perform a relative import)
* sentry-python 1.4.3-1 (AssertionError: previous item was not torn down properly)

# Already fixed in the archive:

* monitoring-plugins-systemd 2.3.1-2

Cheers!

--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau
⢿⡄⠘⠷⠚⠋ pollo@debian.org / veronneau.org
⠈⠳⣄

--------------h0MS3v7P8PiFBoGUC5svhaXI--

-----BEGIN PGP SIGNATURE-----

iHUEARYKAB0WIQTKp0AHB6gWsCAvw830JXpQshz6hQUCYqoxXAAKCRD0JXpQshz6 hbvtAP475HHmC8kZcJxEfU4jo0edajRFYrcnsEgwruXQSE8MfQEAvMk9FRtbTyjm L+s2V0+q5biVtDKHKUkmac33IE0bQAQ=
=zlBP
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi,

On 15/06/22 at 15:22 -0400, Louis-Philippe V�ronneau wrote:

Thanks a lot for this rebuild, very useful.

I was told you needed a list of pytest regressions for you to fill bug reports.
It's my first time doing this, so if I missed something you needed, please say
so.

I was only asked for the rebuild itself, but can also file bugs
(however, given the small number of bugs to file, there's no big
advantage with me automating)

I would need a template similar to https://salsa.debian.org/lucas/collab-qa-data/-/blob/master/ftbfs.txt.liquid

# Valid pytest regression, deprecated feature:

* asyncpg 0.25.0-1 (deprecated pytest feature: -k-)
* junitparser 2.5.0-2 (deprecated pytest feature: -k-)
* openlp 2.9.4-2 (deprecated pytest feature: -k-)
* python-astor 0.8.1-2 (deprecated pytest feature: -k-)
* python-aws-xray-sdk 0.95-2 (deprecated pytest feature: -k-)
* python-b2sdk 1.3.0-2 (deprecated pytest feature: -k-)
* python-easydev 0.12.0+dfsg-2 (deprecated pytest feature: -k-)
* python-h11 0.13.0-1 (deprecated pytest feature: -k-)
* python-jose 3.3.0+dfsg-2 (deprecated pytest feature: -k-)
* python-matrix-nio 0.19.0-2 (deprecated pytest feature: -k-)
* python-twitter 3.3-3 (deprecated pytest feature: -k-)
* sphinx-gallery 0.10.1-1 (deprecated pytest feature: -k-)
* spyne 2.14.0-1 (deprecated pytest feature: -k-)
* flask 2.0.1-2 (deprecated pytest feature: pytest.warns(None))
* photutils 1.4.0-3 (deprecated pytest feature: pytest.warns(None))
* python-ase 3.22.1-1 (deprecated pytest feature: pytest.warns(None))

# Probably a valid pytest regression, but I'm less sure:

* python-biom-format 2.1.10-4 (not sure what the problem is, seems like pytest)
* python-httplib2 0.20.2-3 (not sure what the problem is, seems like pytest) * python-pytest-subtests 0.6.0-1 (not sure what the problem is, seems like pytest)
* python-can 3.3.2.final~github-3 (AttributeError: pytest.approx() is not supported in a boolean context)
* python-protobix 1.0.2-11 (plugin distutils failed with: exit code=5)
* python-pykka 2.0.3-2 (AttributeError: module pytest has no attribute collect)
* python-ratelimiter 1.2.0.post0-1 (AttributeError: module pytest has no attribute collect)
* python-pytest-xprocess 0.18.1-3 (pytest.PytestUnraisableExceptionWarning: Exception ignored)

# Doesn't seem like a pytest regression, but I could be wrong?:

They are probably worth investigating further: I actually did two
rebuilds (one with vanilla unstable, the other with unstable+pytest from experimental) => it's unlikely that they are NOT pytest regressions.

* humanfriendly 10.0-1 (upstream doesn't actually use pytest?)
* pyglet 1.5.14-2 (py3.9 OK, py3.10 fails)
* pyranges 0.0.111+ds-1 (py3.9 OK, py3.10 fails with Fatal Python error: Bus error)

I had to kill that one, it went in some sort of infinite loop. Probably
worth investigating manually.

* pytest-pylint 0.18.0-3 (AssertionError)
* python-qtpy 2.1.0-2 (TypeError: the 'package' argument is required to perform a relative import)
* sentry-python 1.4.3-1 (AssertionError: previous item was not torn down properly)

# Already fixed in the archive:

* monitoring-plugins-systemd 2.3.1-2

Lucas

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEE/t7ByzN7z1CfQ8IkORS1MvTfvpkFAmKqM8oACgkQORS1MvTf vpk9cQ//X6+Tc+SfWYX+4FYGSisgC1gJQXymiDuSYPiZU/WO1U58ANWFWYMg/Rsw ReDuFIcTnUk4mM+Z61iJwz9BVpYySW3n2yRIWBdMO58FUH3bpqQ2DpdMvFrejEL0 CPCyCulK9Xu3oT+V9fuPeUbU+tsJ6iIXdKXRZcvBljR3nVpOqrWeA7kp0sgSCSQ3 P9pM+EA5Pye5XouhNbHFAfT5tv/tn9wcyRJd3wxlNpo7QN0M5jBf8rBRgMTIFnPi oUTNA+PR/Kzh5fucSAM/2pLhVax5uCdRtU++PMPG539X7ylU+Rnku8b5CmU0qfOI eGmrXCb4ry428QMJwsS1aL3HiP681lKoWyOtCIhivFvpwQ1HFIXxoUkOv14N80x+ /GyYa9ML2yimvhOnFVAfXi1iqAABH9qX+TyerAYfCzHwM9kkNwYu+jmsPB61DeQr GhykXznsJ8wXLCOoyvWVlyLXGVCG/xUwdNPTakD9dvh3tdoyr9uf9dyC7yZF9Eq1 bxhJ90Au1EWXy7fpfqPXfrmYKHS6w01+6C9GkLGVxbR/sVK/0YRVoeXG25PAcKmo IY9TfY/TmDZTZQXzudqluPutVBcchAF7z8PK1e+cQygGxjyEyiuG8IYXKNiUwq99 i2JdMD4KCVpr7yr0vPG6UPnyZ4TWgY6qQqfZ6f8PY0HbWaVfArs=
=HcAx
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Wed, Jun 15, 2022 at 09:30:56PM +0200, Carsten Schoenert wrote:

Hi,
[...]

* monitoring-plugins-systemd 2.3.1-2

I've updated sentry-python last week to the current upstream version, so
this package can be count as fixed.

Current pygments requires pytest >= 7.0, I've uploaded 2.12.0 to experimental.

Hi Carsten,

Great, thanks. Since the pygments in testing fails on pytest 7.2.1,
and the version in experimental depends on pytest >= 7.0, we'll need
to do the following when we are ready to upload pytest 7.2.1 to
unstable:

* Mark pytest 7.2.1 as Breaks: pygments (<< 2.12.0)
* Upload pygments 2.12.0 to unstable

Otherwise the pygments in testing will prevent the migration of
pytest.

Best wishes,

Julian

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Thank you for your guidance.

I have filled all of the regressions you reported in the BTS:

https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=pytest7;users=debian-python@lists.debian.org

Cheers,

--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau
⢿⡄⠘⠷⠚⠋ pollo@debian.org / veronneau.org
⠈⠳⣄

On 2022-06-15 15 h 32, Lucas Nussbaum wrote:

Hi,

On 15/06/22 at 15:22 -0400, Louis-Philippe Véronneau wrote:

Thanks a lot for this rebuild, very useful.

I was told you needed a list of pytest regressions for you to fill bug reports.
It's my first time doing this, so if I missed something you needed, please say
so.

I was only asked for the rebuild itself, but can also file bugs
(however, given the small number of bugs to file, there's no big
advantage with me automating)

I would need a template similar to https://salsa.debian.org/lucas/collab-qa-data/-/blob/master/ftbfs.txt.liquid

# Valid pytest regression, deprecated feature:

* asyncpg 0.25.0-1 (deprecated pytest feature: -k-)
* junitparser 2.5.0-2 (deprecated pytest feature: -k-)
* openlp 2.9.4-2 (deprecated pytest feature: -k-)
* python-astor 0.8.1-2 (deprecated pytest feature: -k-)
* python-aws-xray-sdk 0.95-2 (deprecated pytest feature: -k-)
* python-b2sdk 1.3.0-2 (deprecated pytest feature: -k-)
* python-easydev 0.12.0+dfsg-2 (deprecated pytest feature: -k-)
* python-h11 0.13.0-1 (deprecated pytest feature: -k-)
* python-jose 3.3.0+dfsg-2 (deprecated pytest feature: -k-)
* python-matrix-nio 0.19.0-2 (deprecated pytest feature: -k-)
* python-twitter 3.3-3 (deprecated pytest feature: -k-)
* sphinx-gallery 0.10.1-1 (deprecated pytest feature: -k-)
* spyne 2.14.0-1 (deprecated pytest feature: -k-)
* flask 2.0.1-2 (deprecated pytest feature: pytest.warns(None))
* photutils 1.4.0-3 (deprecated pytest feature: pytest.warns(None))
* python-ase 3.22.1-1 (deprecated pytest feature: pytest.warns(None))

# Probably a valid pytest regression, but I'm less sure:

* python-biom-format 2.1.10-4 (not sure what the problem is, seems like pytest)
* python-httplib2 0.20.2-3 (not sure what the problem is, seems like pytest) >> * python-pytest-subtests 0.6.0-1 (not sure what the problem is, seems like pytest)
* python-can 3.3.2.final~github-3 (AttributeError: pytest.approx() is not supported in a boolean context)
* python-protobix 1.0.2-11 (plugin distutils failed with: exit code=5)
* python-pykka 2.0.3-2 (AttributeError: module pytest has no attribute collect)
* python-ratelimiter 1.2.0.post0-1 (AttributeError: module pytest has no attribute collect)
* python-pytest-xprocess 0.18.1-3 (pytest.PytestUnraisableExceptionWarning: Exception ignored)

# Doesn't seem like a pytest regression, but I could be wrong?:

They are probably worth investigating further: I actually did two
rebuilds (one with vanilla unstable, the other with unstable+pytest from experimental) => it's unlikely that they are NOT pytest regressions.

* humanfriendly 10.0-1 (upstream doesn't actually use pytest?)
* pyglet 1.5.14-2 (py3.9 OK, py3.10 fails)
* pyranges 0.0.111+ds-1 (py3.9 OK, py3.10 fails with Fatal Python error: Bus error)

I had to kill that one, it went in some sort of infinite loop. Probably
worth investigating manually.

* pytest-pylint 0.18.0-3 (AssertionError)
* python-qtpy 2.1.0-2 (TypeError: the 'package' argument is required to perform a relative import)
* sentry-python 1.4.3-1 (AssertionError: previous item was not torn down properly)

# Already fixed in the archive:

* monitoring-plugins-systemd 2.3.1-2

Lucas

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Fri, Jun 24, 2022 at 06:53:04PM -0400, Louis-Philippe V�ronneau wrote:

Thank you for your guidance.

I have filled all of the regressions you reported in the BTS:

https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=pytest7;users=debian-python@lists.debian.org

Thanks Louis-Philippe!

Best wishes,

Julian

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi,

Am 16.06.22 um 10:05 schrieb Julian Gilbey:
...

Great, thanks. Since the pygments in testing fails on pytest 7.2.1,
and the version in experimental depends on pytest >= 7.0, we'll need
to do the following when we are ready to upload pytest 7.2.1 to
unstable:

* Mark pytest 7.2.1 as Breaks: pygments (<< 2.12.0)

looking at the autopkgtest on the CI pygments is still failing while
testing with versions from testing. Mostly because I think as pytest < 7
(from testing) is used. All other versions differences are not critical
I guess. The following list of used packages are given by the different versions between testing and unstable.

testing: python3-lib2to3 all 3.9.12-1
testing: python3-distutils all 3.9.12-1
testing: python3-toml all 0.10.2-1
testing: python3-pytest all 6.2.5-3

unstable: python3-lib2to3 all 3.10.5-1
unstable: python3-distutils all 3.10.5-1
unstable: python3-tomli all 1.2.2-2
unstable: python3-pytest all 7.1.2-2

Currently python3-pytest hasn't an entry for breaking on pygments like
Julian was proposing. Maybe I'm still missing something.

--
Regards
Carsten

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi,

On Fri, Jul 08, 2022 at 09:33:10PM +0200, Carsten Schoenert wrote:

Hi,

Am 16.06.22 um 10:05 schrieb Julian Gilbey:
...

Great, thanks. Since the pygments in testing fails on pytest 7.2.1,
and the version in experimental depends on pytest >= 7.0, we'll need
to do the following when we are ready to upload pytest 7.2.1 to
unstable:

* Mark pytest 7.2.1 as Breaks: pygments (<< 2.12.0)

looking at the autopkgtest on the CI pygments is still failing while testing with versions from testing. Mostly because I think as pytest < 7 (from testing) is used. All other versions differences are not critical I guess. The following list of used packages are given by the different versions between testing and unstable.

Yes, indeed; as pygments depends on pytest >= 7 and the version
currently in testing breaks with pytest 7, pytest must declare Breaks: python3-pygments (<< 2.12.0). [Explanation: britney (?) tries each
package on its own when testing for migration: pytest can't migrate as
that would break pygments in testing, and pygments can't migrate as it
depends on the newer pytest. So we're stuck and neither will
migrate. But if pytest 7 declares a Breaks on pygments (<< 2.12.0),
then it will attempt to migrate both of them simultaneously.]

Best wishes,

Julian

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Le lundi 11 juillet 2022 à 18:37 +0100, Julian Gilbey a écrit :

[Explanation: britney (?) tries each
package on its own when testing for migration: pytest can't migrate
as that would break pygments in testing, and pygments can't migrate
as it depends on the newer pytest.  So we're stuck and neither will migrate.  But if pytest 7 declares a Breaks on pygments (<< 2.12.0),
then it will attempt to migrate both of them simultaneously.]

Well, after some time (60 days if I remember well), both packages will
get kicked out of testing, at which point there will be no more
objections to the unstable ones migrating to testing, and that will
happen.

Neither elegant nor fast, I admit.

J.Puydt

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)