An error occurred fetching the project authors.
- 25 Nov, 2008 1 commit
-
-
Jim Fulton authored
return values. This in turn simplified the client and server software. Added code to select different client and server stubs and input handlers depening on whether the Z309 or earlier protocols are used. ZODB 3.8 clients can now talk to ZODB 3.9 servers and the other way around.
-
- 15 Nov, 2008 1 commit
-
-
Jim Fulton authored
requires passing a test object. With this, it appears that I can run tests in parallel without getting extra spurious errors.
-
- 18 Feb, 2008 1 commit
-
-
Jim Fulton authored
mode.
-
- 12 May, 2005 1 commit
-
-
Tim Peters authored
ZEO/tests/zeoserver.py, log(): repair broken interface between old logging code and the use of Python's logging package. ZODB/tests/TransactionalUndoStorage.py, _exercise_info_indices(): Jeez Louise, the new tests I added for undoInfo+undoLog work fine in ZODB, but break the ZRS tests(!). They close the DB "too soon", and in one of the ZRS scenarios that leaves a recovering secondary without a primary to recover from.
-
- 11 Mar, 2005 1 commit
-
-
Tim Peters authored
-
- 02 Jun, 2004 1 commit
-
-
Jim Fulton authored
-
- 25 Apr, 2004 1 commit
-
-
Gintautas Miliauskas authored
to zLOG other than a few comments. This definitely broke the log analyzers pretty bad.
-
- 27 Feb, 2004 1 commit
-
-
Martijn Faassen authored
-
- 14 Jan, 2004 1 commit
-
-
Jeremy Hylton authored
I don't really understand why this change and the last one to runzeo.py have their apparent effects, but the tests work and the -m option to runzeo.py works.
-
- 07 Oct, 2003 1 commit
-
-
Jeremy Hylton authored
-
- 06 Oct, 2003 1 commit
-
-
Fred Drake authored
-
- 02 Oct, 2003 1 commit
-
-
Jeremy Hylton authored
-
- 15 Sep, 2003 1 commit
-
-
Jeremy Hylton authored
Please make all future changes on the Zope-2_7-branch instead.
-
- 05 Jun, 2003 1 commit
-
-
Jeremy Hylton authored
-
- 30 May, 2003 2 commits
-
-
Jeremy Hylton authored
After the merge, I made several Python 2.1 compatibility changes for the auth code.
-
Jeremy Hylton authored
-
- 29 May, 2003 2 commits
-
-
Jeremy Hylton authored
-
Jeremy Hylton authored
-
- 23 May, 2003 1 commit
-
-
Jeremy Hylton authored
Update the ZEO tests to use the new configuration language. Remove files from old configuration approach.
-
- 28 Feb, 2003 1 commit
-
-
Barry Warsaw authored
-
- 27 Jan, 2003 1 commit
-
-
Jeremy Hylton authored
Explicitly close sockets to make tests run faster.
-
- 09 Jan, 2003 2 commits
-
-
Jeremy Hylton authored
-
Jeremy Hylton authored
storage. This provides a minimal test of the server close functionality.
-
- 07 Jan, 2003 3 commits
-
-
Barry Warsaw authored
-
Barry Warsaw authored
(i.e. via ctrl-C) before it has a chance to make the killer connect, these zeoserver processes will eventually go away (and clean up their temp files).
-
Jeremy Hylton authored
-
- 03 Jan, 2003 2 commits
-
-
Jeremy Hylton authored
-
Fred Drake authored
-
- 16 Dec, 2002 1 commit
-
-
Barry Warsaw authored
storage's artifacts. Some tests expect to reconnect in read-only mode to a previously created storage.
-
- 13 Dec, 2002 2 commits
-
-
Barry Warsaw authored
which doesn't put .loop() in the package namespace. Use the full dotted path to the function.
-
Barry Warsaw authored
-
- 12 Dec, 2002 1 commit
-
-
Barry Warsaw authored
makes little sense to call the server script `winserver.py'. That's gone now, in favor of this zeoserver.py script. Changes include: main(): Accept a -C option pointing to a temp file containing a ZConfig storage section. This reads the file and creates the so described storage, then removes the temp config file. It creates an administrative server which opens an `admin' port which is used to os._exit() this process, with the following protocol. The first time the admin port is connected to, an ack character is sent from zeoserver. This is necessary to coordinate the tests so that they are assured the server is running and responding before it tries to do more. Otherwise, some tests were vulnerable to timing bugs where the shutdown connect happened before the server was ready to accept them. The second connect exits the server process just like before. Copious log entries are written. This script also cleans up after the storages are closed, by calling the storage's .cleanup() method if it exists (FileStorage and the Berkeley storages both implement this method).
-