New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes to make tests pass with https://github.com/zopefoundation/ZODB/pull/66 #45
Conversation
Thanks. I would prefer not to merge as-is, but I will use it as a guideline for a different PR. Specifically, I think I will catch the list of disconnected/closed exceptions to handle checkAutoReconnect and add a separate test. Any thoughts about the test failures? I suppose it's part of the monkey-patch that got deleted. I may need to do some attribute/version checking to keep part of the patch around for existing ZODB versions. The |
I assume the test failures are due to the missing monkey patch. This is sad (and a little surprising, since the monkey patch is pretty close to what's already in ZODB4. |
I can try to dig into the details to come up with a definitive cause. |
Before digging to much, I'd restore the patch and see if the tests pass. I assume they will. At which point, you'll have to do some sniffing and conditionally apply the patch. Actually, I'll do that. Just a sec... |
That should fix the test failures. |
OK, IDK WTF coveralls |
Probably because "except ImportError:" blocks are ignored (as they're typically Py2/Py3 compatibility code). |
How about #46 instead? |
#46 LGTM |
You may not want to merge this as is. I had to comment out a
raise
in_rollback_load_connection
to makecheckAutoReconnect
pass. This is because sync is now called when a connection is opened.The most important change is to comment out the monkey patch, which you probably want to delete.
Also,
check16MObject
failed for me for mysql on master with released ZODB. Maybe this is an issue with my setup.