On Fri, Nov 20, 2009 at 1:52 PM, Jim Fulton wrote:
> On Fri, Nov 20, 2009 at 1:36 PM, Tres Seaver wrote:
...
I just checked in a stupid test to ensure that repozo can be imported.
- --- src/ZODB/scripts/tests.py (revision 105913)
+++ src/ZODB/scripts/tests.py (working copy)
Merged.
Jim
On Fri, Nov 20, 2009 at 5:45 PM, Chris Withers wrote:
> Jim Fulton wrote:
>>>
>>> It seems a bit bizarre that exceptions are logged at INFO rather than
>>> ERROR...
>>
>> Agreed. A simple fix and test on a branch would be appreciated.
>
> Done:
>
> http://svn.zope.org/ZODB/branches/
Jim Fulton wrote:
> Well, not really fair enough. I just looked at the change that Chris
> made. It has a bug
> that would be caught by your test if anyone tried to port repozo to
> Python 3.
Which alternate reality are you talking about here? ;-)
> I'm going to back out these changes.
Wow.
Jim Fulton wrote:
> On Fri, Nov 20, 2009 at 1:52 PM, Jim Fulton wrote:
>> On Fri, Nov 20, 2009 at 1:36 PM, Tres Seaver wrote:
> ...
> I just checked in a stupid test to ensure that repozo can be imported.
>
> - --- src/ZODB/scripts/tests.py (revision 105913)
> +++ src/ZODB/scripts
Martin Aspeli wrote:
> - there were no tests for the existing code
There are tests, they're just manual and spew a lot of output even when
passing, but they do (as best I could tell) exercise the backup and
restore cycle quite heavily.
I ran these before and after to verify they didn't fail b
