GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | |||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | |||
GeezerVison is showing github.com — bpo-38291: Reset DeprecationWarning filters in test_typing io and re by Fidget-Spinner · Pull Request #26811 · python/cpython Conversation
|
|
🤖 New build scheduled with the buildbot fleet by @Fidget-Spinner for commit 5190297 🤖 If you want to schedule another build, you need to add the ":hammer: test-with-buildbots" label again. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
I suppose we went too quick here? I’m not sure what this does (it’s been a long time since I played with warnings) but if this is blocking other PRs I am happy to merge it.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Luckily this isn't blocking other PRs, buildbot failures only block releases AFAIK. As Sebastian mentioned on the bpo issue, it's an Azure pipelines problem. The specific pipeline is only run after a commit is made. Even with the This fix wasn't clear to me too, until I read this part of the warnings docs: |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
@gvanrossum: Please replace |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.