view doc/debugging.txt @ 5142:93832cec4c31

issue2550839: Xapian, DatabaseLockError: Unable to get write lock on db/text-index: already locked I put in a retry loop that will attempt to get the lock. 10 tries with a delaythatvaries from .02 seconds to .64 seconds. Total delay over 10 cycles approx. 4.5 seconds. I can't figure out how to make pytest run two parallel processes to test this code. I did try running: ./run_tests.py -k Xapian test/test_indexer.py & ./run_tests.py -k Xapian test/test_indexer.py and confirmed that one of the processes seemed to hang on a test and then threw a lock failure error. So at least the code path is being exercised. If anybody knows how to correctly test this I would love to do a real test.
author John Rouillard <rouilj@ieee.org>
date Wed, 13 Jul 2016 19:42:44 -0400
parents b6f1aaba4827
children a635a60ffb84
line wrap: on
line source

Debugging Aids
--------------

Try turning on logging of DEBUG level messages. This may be done a number
of ways, depending on what it is you're testing:

1. If you're testing the database unit tests, then set the environment
   variable ``LOGGING_LEVEL=DEBUG``. This may be done like so:

    LOGGING_LEVEL=DEBUG python run_tests.py

   This variable replaces the older HYPERDBDEBUG environment var.

2. If you're testing a particular tracker, then set the logging level in
   your tracker's ``config.ini``.

SENDMAILDEBUG
=============

Set to a filename and roundup will write each email message
that it sends to that file instead to the internet. 
This environment variable is independent of the python -O flag.


Roundup Issue Tracker: http://roundup-tracker.org/