This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author kj
Recipients JelleZijlstra, dgelessus, docs@python, gvanrossum, kj, levkivskyi, miss-islington, srittau
Date 2021-06-21.10:15:46
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1624270546.31.0.0546876098384.issue38291@roundup.psfhosted.org>
In-reply-to
Content
> Overall it looks as if the the Azure pipeline should be fixed, though. It's not ideal that the tests pass while running the PR, but not in other situations.

I agree. This specific test only seems to run *after* a commit is made. I don't see a way to run this test on a PR, even the `test-with-buildbots` test doesn't seem to trigger it.

> Also, the warnings suppression is not really obvious.

Yup, it's hidden away in the docs here, so I was rather lost too: https://docs.python.org/3/library/warnings.html#testing-warnings

Anyways, I'm not actually sure that the PR will fix it. AFAICS, the only way to test it is to commit it and let the buildbot run ;). I can't reproduce it locally.
History
Date User Action Args
2021-06-21 10:15:46kjsetrecipients: + kj, gvanrossum, srittau, docs@python, levkivskyi, JelleZijlstra, miss-islington, dgelessus
2021-06-21 10:15:46kjsetmessageid: <1624270546.31.0.0546876098384.issue38291@roundup.psfhosted.org>
2021-06-21 10:15:46kjlinkissue38291 messages
2021-06-21 10:15:46kjcreate