Mercurial > p > roundup > code
view doc/debugging.txt @ 5277:b580f61929e2
Removing richard from notification list. Verified that
he doesn't want to be on it anymore.
Date: Sun, 24 Sep 2017 14:58:24 +1000
To: rouiljsomewhere
From: Richard Jones <r1chardj0n3s at gmail.com>
Subject: Re: Do you still want new issues to roundup tracker sent to
you?
--94eb2c0da3aac771bb0559e84afb
Content-Type: text/plain; charset="UTF-8"
Thanks John, yes please do remove me.
Richard
On 24 September 2017 at 14:13, John P. Rouillard <rouilj at cs.umb.edu>
wrote:
> Hi Richard:
>
> I am working on updating the roundup tracker to
> get it ready for the current development code.
>
> As I was testing I noticed you are still in the
> list of email addresses getting new issue emails.
>
> Do you want to continue to receive these since
> you aren't actively developing roundup?
| author | John Rouillard <rouilj@ieee.org> |
|---|---|
| date | Sun, 24 Sep 2017 18:44:48 -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.
