| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
Ah, somehow I missed that you had already noticed this. I'm fine with actually fixing it, like you do in gh-119675 (which I haven't actually looked at yet). However, it looks like we actually don't need no_rerun for datetime's CapiTest any more, so the change in this PR might be the right first step, regardless of whether or not we make no_rerun work with test classes. |
Sorry, something went wrong.
|
🤖 New build scheduled with the buildbot fleet by @ericsnowcurrently for commit 80b9bc5 🤖 If you want to schedule another build, you need to add the 🔨 test-with-refleak-buildbots label again. |
Sorry, something went wrong.
…120180) The tests were accidentally disabled by 2da0dc0, which didn't handle classes correctly. I considered updating no_rerun() to support classes, but the way test_datetime.py works would have made things fairly messy. Plus, it looks like the refleaks we had encountered before have been resolved.
…120180) The tests were accidentally disabled by 2da0dc0, which didn't handle classes correctly. I considered updating no_rerun() to support classes, but the way test_datetime.py works would have made things fairly messy. Plus, it looks like the refleaks we had encountered before have been resolved.
| Back | FazBrowse Home | New Git URL |
The tests were accidentally disabled by 2da0dc0, which didn't handle classes correctly.
I considered updating no_rerun() to support classes, but the way test_datetime.py works would have made things fairly messy. Plus, it looks like the refleaks we had encountered before have been resolved.