On Fri, 30 Jun 2006, Bryan Stearns wrote:
Andi, do you think there's any utility to running after each test? (Seems like running once at the end would tell us if any test corrupted the repository; doing it for each test wouldn't add anything, since once it's corrupt, it's likely to stay that way.)
In DEBUG mode, or without -O, values are being checked during assignment and check() is being run upon quitting. I believe John is the one who made both of these things happen so you may want to coordinate with him about adding more such things.
Running check() after every test has the benefit that we know which test made it be corrupt if check() fails but can be costly in time. check() loads every item in the repository, every value, and iterates every ref in every ref collection. I think that running check() at the end of the test suite in 'release' would be a good addition.
Andi.. _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "chandler-dev" mailing list http://lists.osafoundation.org/mailman/listinfo/chandler-dev
