Path: csiph.com!1.us.feeder.erje.net!3.us.feeder.erje.net!3.eu.feeder.erje.net!feeder.erje.net!weretis.net!feeder8.news.weretis.net!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod From: Julian Gilbey Newsgroups: linux.debian.maint.python Subject: Re: Updating pytest Date: Wed, 08 Jun 2022 13:50:01 +0200 Message-ID: References: X-Mailbox-Line: From debian-python-request@lists.debian.org Wed Jun 8 11:47:35 2022 Old-Return-Path: X-Amavis-Spam-Status: No, score=-7.21 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, LDO_WHITELIST=-5, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate: -4.6 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Mailing-List: archive/latest/19992 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/YqCMR+mbRar4IN2v@d-and-j.net Approved: robomod@news.nic.it Lines: 79 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: Paul Wise , debian-python X-Original-Date: Wed, 8 Jun 2022 12:47:19 +0100 X-Original-Message-ID: X-Original-References: <67901ea5dde4c2e29b186562ff5bd807f06208a8.camel@debian.org> Xref: csiph.com linux.debian.maint.python:14164 On Tue, Jun 07, 2022 at 03:49:37PM -0400, Sandro Tosi wrote: > > Sandro: you managed the numpy transition, it seems. What is involved > > in something like this? I would imagine something like: > > > > (1) Upload pytest 7.x to experimental > > i took care of this just now, uploading pytest/7.1.2 to experimental > (and i've messed up the branches on salsa, so i've committed my > changes to `experimental2`) I've just looked at https://release.debian.org/britney/pseudo-excuses-experimental.html - it's encouraging that there have only been a handful of failures on amd64. There have been a few more on arm64, but they seem mostly insignificant or transient. Here are the failing tests: 1. finalcif: it seems like an update to python3-gemmi has broken this package 2. fpylll: The failures are happening in the current unstable version as well. 3. glyphslib: The failures are happening in the current unstable version as well. 4. junitparser: This looks like it might be due to the new version of pytest. 5. jupyter-client: The arm64 failure looks likely to be transient 6. monitoring-plugins-systemd: This looks like it might be due to the new version of pytest - it's not finding any tests. 7. nibabel: This is a new warning I haven't seen before: there's a ResourceWarning about an unclosed file, which is putting a message on stderr and causing the test to fail. 8. pytest-pylint: This looks like it may be due to the new version of pytest, but I'm not sure. 9. pytest-twisted: Bizarre; it's failing to find the testdir fixture; pytest 7.x does not claim to have deprecated this, so something is weird here. 10. python-ase: not sure why the pytest.warns call raises an error rather than just a warning. But this is certainly a pytest 7.x issue. I'm not sure how best to rewrite the code in these tests; different calls are now needed in the two cases (pytest.warns(...) in the first case, warnings.catch_warnings() in the second, perhaps?). 11. python-async-lru: this throws an error to stderr: Future exception was never retrieved future: ZeroDivisionError No idea what that's about. 12. python-b2sdk: this fails to select any tests, so presumably a pytest 7.x issue. 13. python-email-validator: interesting error on arm64, suggesting the test needs fixing (but not pytest 7.x related) 14. python-etelemetry: looks like it is a pytest 7.x issue (change in keywords for skipping?) 15. python-httplib2: similar to python-etelemetry 16. python-parameterized: this looks likely to be a pytest 7.x issue; the meaning of missing_tests has perhaps changed? Would need to look at the code more carefully to understand this. 17. python-pytest-subtests: this is a pytest 7.x issue; the package has been updated upstream And that's it, so it really doesn't seem too bad. Best wishes, Julian