Mercurial > p > roundup > code
view doc/debugging.txt @ 5971:e5acd1843517
- issue2550926 - Original author adding a second message shouldn't set
status to 'chatting'.
Updates to jinja and classic tracker's statusauditor.py and new
config.ini for the detectors. Also updated upgrading.txt.
Tested classic tracker using demo.py. Test cases:
value set to false: second update sets to chatting
value set to true: update by new user sets to chatting, update by
creator of issues leaves it at unread.
missing config value in config.ini: error about missing value
value set to non-boolean: error message reports bad value with valid
values.
| author | John Rouillard <rouilj@ieee.org> |
|---|---|
| date | Thu, 07 Nov 2019 18:35:33 -0500 |
| 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.
